Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
If documentation is written in a readable and confluent way, RTFM isn't such a big deal. The issue comes with overly draconian and non-confluent documentation.
I thought you wrote confluence and wanted to grab my pitchfork.
rivers
Petrichor
Looking at you, Nix documentation
Day 564: I have become lost in the forums amidst flake debate threads. Do not search for me, it is already too late.
You got a nice guttural laugh outta me for that one.
Confluent?
Flowing/coming together.
I think what they are referring to are docs where pieces are explained individually, but not in a consistent or cohesive way, obfuscating use.
In my experience, all the Linux documentation I have read has been written for peers of Linux developers, who are familiar with technical terminology and several concepts and steps are left out and implied rather than explained.
It’s a way for developers to ensure that Linux never receives adoption past other developers. Literary equivalent of pulling the ladder up.
Said it before and I'll say it again: had to manually install some software to make Steam tinker launch work, and the instructions for installing it were to download and prepare the GitHub folder, then "do the usual and move the completed file to ..."
Ive used git in the past and it still took me multiple minutes to figure out they meant the "make && build" command. Why was that so hard to fucking write??
Highly specialized people live in bubbles and assume that everyone else lives in their same bubble and so if someone else doesn’t understand, they aren’t worth communicating with.
XKCD 2501, basically.
Thank you for this. It’s beautiful.
I mean, it's technical documentation. There's a limit to how exciting it can be. lol.
There is a way with chmod in bash to change files and folders with files getting no execute bit and folder do (rwX instead of rwx). It's in the man pages but good luck finding it via Google. Stackoverflow just suggests using find over and over again.
That did it for me.
You're absolutely right