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
this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying "edit the file"? why symlink systemd stuff to your own home directory?
the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.
I'm still learning how to write good posts. I'll this into consideration for the next one.
your writing overall is good! it's just a matter of information priority.
here's a tip, dunno how applicable it is but i use it when writing technical documentation:
for each step, explain to yourself why you're doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.
That's a good tip. Thanks. I think I might tweak the existing posts for readability.