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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )
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 quadlets can also auto-update and auto rollback, if needed.
@K3can @silver How do you handle running as other users? I like to run services as their own user, so currently I create a new user and (as them) run podman compose.
Quadlets work like any other systemd service.
You create the user/group you want to run as on the underlying system, then just specify that user/group in the quadlet file.
If you look at my *arr examples, you can see the user and groups they're running as.
@K3can So you're running the systemd services as root, and letting systemd change them to their relevant users? Or are you running the systemd services as a non-privileged user, and using container subuid/subgids?
The first one. The service is owned by root, but the application is running as an unprivileged system user.