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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
In the docker folder with the docker-compose.yml of whatever docker container you want to upgrade:
docker compose pull && docker compose up -dAs others have said, for large groups of containers it's helpful to use Watchtower.
Immich in particular warns to backup your database before an upgrade. Also be on the lookout for breaking changes which require you to alter your docker-compose.yml file before an upgrade.
Oh and after upgrades to remove any dangling images which sometimes take up a lot of space:
docker image pruneAlso if you want services to be interoperable, learn about docker networking now not later and remember for static IPs you must create a user defined bridge.
I think compose files are usually pinned to a version, or use a .env file that needs to be changed to update to a new version.
I personally don't update very often; usually not until I'm forced to for some reason. I find that just checking the documentation for any upgrade/migration guides, and doing it manually is sufficient. I don't expose this kind of stuff publicly; if I did, I'd probably update regularly.
Immich is a more touchy beast because it includes a mobile app and the mobile app and the docker container need to generally be either the same version, or within a few versions of one another. There was a while where I forgot to update the server for a while and the mobile app kept being updated on my phone and stopped backing up photos because it could no longer communicate with the server.
I don't expose services to the outside world either, but I still enjoy keeping things up to date. Gives me something to do.