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
I hate, hate, hate when I fix something and I don't know why the fix worked (or what the fix even was...). I want my suffering to result in something learned so it doesn't happen again.
Soooo much this. I'm down to learn about technology any day of the week. But when I 'fix' something and I don't know what the 'fix' really was, it is a rush of mixed emotions. I am ecstatic relieved the problem is fixed, but left empty not having learned the 'why it broke' in the first place. And then I'm always fearful that the problem will gestate in my lab and rear it's ugly head again at some other inopportune time.
This. If I pay the cost in frustration and anguish and soul-searching and demanding justice from an uncaring god, I want some thing for it. I want documentation. I want my lessons learned from the post incident review. I want something I can hack into mgmtConfig to make sure nothing else will do that too.
Struggling for no payoff is the absolute worst thing.