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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Every time I set up anything, I do one of two things:
If it's container based, it gets a commented docker compose file in my custom orchestration
If it's on a host system, the changes are scripted and commented in a setup script, which are run on new machines. If the acrit is specific to one machine, it is configured as such
I find in-setup docs to be best for a home lab, plus if I have to replace hardware, it's fast.
Fun fact, I do it for laptops and desktops, too.
I started to put it all in my selfhosted bookstack and that works well for me. I also automated a good part of my setup with Ansible, so I can just check how the Playbook did things if I forgot.
Obsidian synced via git.
Here: https://wiki.gardiol.org/
Based on Dokuwiki and my own experience. Mostly started to track what and why I do stuff, and published because I truly believe in a free internet.
I tried since the very beginning to build everything in ansible and terraform, so everything is in the code or in its associated README files.
But apart from that I have a hodge podge of dozens of note documents in Obsidian.
Not much, really. I do comment changes to config files and such.
The whole deployment is done via ansible, so the ansible source is my documentation.
NixOS's declarative configurations basically document themsleves: add some comments and you're good to go and can back then up to wherever whenever
In gitlab.
In the terraform project that builds it. Or in the cinc.sh config that makes it go.
MD lets me add diagrams.
If it need documentation means things are over the line when comes to complexity and I should scale down / simplify. :)
Complexity and over-engineering are a serious problem, I really try to keep it as simple as possible so I don't have to waste time managing it, dealing with updates and potential security issues. Simple code/infrastructure breaks less and has less potential insecure points.