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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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 don't do upgrades (well, not in the sense most people think of them).
My approach is that upgrades are too risky, things always break. It's also why I don't permit auto updates on anything. I'd rather do manual updates than dedicated time. Keeping things working is more important, and I have backups.
I run everything virtualized (as much as I can), so I can test upgrades by cloning a system and upgrading the clone. If that fails, I simply build a new system based on some templates I keep. Run in parallel, copy config and data as best I can, then migrate. Just migrated my Jellyfin setup this way.
This is a common methodology in enterprise, which virtualization makes a lot easier for us self hosters.
I haven't had a disruption from updates/upgrades in 5 years.
It’s not common in enterprise to not auto-update.
It's extremely common...most production lines I've ever been to only do manual updates on equipment, if any at all.
Depends on the company and the system. Some of them need to be done off-hours while people aren't using them. Some are HA and/or insignificant enough that you can do them any time without interruption.
I have not had any auto update in my entire career but i have always been on the infra side so it was never just my app. Though I do wish the update/outage process would be updated to reflect kubernetes and not just think of everything as monolithic servers.
It's also not uncommon in enterprises that things break needlessly.