view the rest of the comments
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!
If you decide to use docker-compose.yml files, which I do recommend, then I'd also highly recommend this script for updating the docker containers.
It checks each container for updates and then let's you select the containers you would like to update. I just keep it in the main directory with all the other docker container directories.
https://github.com/mag37/dockcheck/blob/main/dockcheck.sh
The preferred filename is now
compose.yaml
, see https://docs.docker.com/compose/compose-file/03-compose-file/I doubt they’re going to remove support for the previous filename anytime soon. It would break way too many things.
Why not just run a watchtower container? Combined with a diun one to send gotify messages to my phone if you're into that. (I am!)
Sometimes automated updates are not desirable. I also prefer the simplicity of a bash script over a full container.