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
Auto updates can cause problems. Some recommend it, some tell you to not do it. My standpoint is, when a container can't work with auto updates, they suck. Sure there are containers who require some additional attention after an update, like gitea with some config changes but I use it in an environment where it can be offline of some time.
If a container uses Postgresql, you can't auto update. So far I didn't found a well maintained container, that can do this. You also should keep an eye on your containers. As I mentioned, Gitea had some config changes, breaking the default theme (nothing major). They even screwed up their tags and I had 3 times an RC in a tag where no RC should get published. With Jellyfin I was on a tag that didn't got any updates anymore and I needed to use a different one.
That's interesting. I certainly will keep that in mind.
To be more specific: Postgresql requires manual steps with major versions. Tutorials I found require you to dump the database in the old version first, then update and then import. You could use a tagged version of postgresql and just auto update there but the main container might require a newer version. I saw containers who try this but none looked production ready.