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
Assuming you set up your volume correctly, it's very easy. If you're brave, you could even have your image URI use the tag
latest, then all you need to do is restart the container each time an update comes out. I'm a little less brave. I like to use explicit version numbers. I just update my Dockerfile or yml file and restart it each time.Kinda unrelated, but if I restart my computer for whatever reason, will the containers and volumes be wiped out?
The volumes will be fine. The way volumes work is the data is stored on the host in a directory, and then that directory gets mounted on the container. So as long as you don't delete the volume's folder on the host, you are totally fine.
The containers won't get wiped, but even if they did, it wouldn't matter. They aren't anything special. You could wipe them at will and pull them again and restart them. As long as your volumes didn't get deleted, it will be like nothing even happened.