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
Podman ftw!
Concur, podman doesn't (have to) have root, and has autoupdate and podman-compose to use docker files. Containers are cool, Docker less so.
My biggest issue with podman is that podman-compose isn't officially recommended or supported, and the alternatives (kubernetes YAML and Quadlet) kind of suck compared to using a compose file. It makes me way to pour a bunch lf work into switching to using podman-compose. I have no clue why they didn't just use the compose spec for their official orchestration method.
once the containers are running after podman-compose you can use podman-generate-systemd to create a systemd services. Helped me move a rather large compose file to a bunch of services. My notes weren't the best, sorry, but that's the gist.It got me moved. I've now moved on to .container files for new stuff, which generates them on the fly. Need to move my old services over, but they work and who's got the time...
How do you like the .container files? I hate the idea of having different files for each container, and each volume. They also don't even support pods and the syntax is just terrible compared to YAML.
Not sure yet, agree it's not as nice to look at as YAML, but at least it's prettier than the alternative systemd.service implementation, and it's been rock solid so far. Time will tell, I'm sure pods will come and it seems to be what redhat sees as their direction. A method for automatically generating them from docker YAML (and hopefully vice-versa) would go a looong way towards speeding adoption.
How do you feel about having to specify a different file for all of your containers and volumes? Has that annoyed you at all? I agree that pods are really nice, and they should give you a way to generate them from compose YAML.
I have made my peace, it's the price of not giving docker root. I just open a Kate session and it's all there, nicely broken into sections.