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
What is the reason for the systemd service? Looks to me like it only supplements the standard docker restart function. Can it be run without it? Then maybe mark it as optional while pointing out the benefits
In my world the standard way of starting and stopping services on Linux is systemd, that is why I added it. I never used the docker way and am not really familiar with it.
But I will try to update it a bit, it's a good point overall.
Docker run commands or docker-compose.yml files offer a restart-policy flag that offer various levels of restart behavior which trigger when the container crashes, is stopped or when the Docker service starts (eg after a reboot)