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
Docker compose pull; docker compose down;docker compose up -d
Pulls an update for the container, stops the container and then restarts it in the background. I've been told that you don't need to bring it down, but I do it so that even if there isn't an update, it still restarts the container.
You need to do it in each container's folder, but it's pretty easy to set an alias and just walk your running containers, or just script that process for each directory. If you're smarter than I am, you could get the list from running containers (docker ps), but I didn't name my service folders the same as the service name.
What commands do you have to run after you update
docker-compose.ymlor.envfiles? I updated one of those files once bad things happened... I haven't had to update the configs in a long time.I usually just do
As I would with any service restart. The up -d command is supposed to reload it as well, but I prefer knowing for certain that the service restarted.
Out of curiosity, what did you update and what broke? I had that happen a lot when I was first getting started with docker, and is part of how I learned. Once you have a basic template (or have dec supplies example files), it makes spinning up new services less of a hassle.
Though I still get yelled at about the version entry in my fines because I haven't touched mine in forever
My breakage happened a while ago, so I don't quite remember all of the details...
but what I think happened was I updated
/etc/immich/.env. I updated the path forDB_DATA_LOCATIONand/orUPLOAD_LOCATIONand then I randocker compose up -dI think. But nothing changed....