134
systemd has been a complete, utter, unmitigated success
(blog.tjll.net)
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of [email protected] and The GIMP
One thing the author probably hasn't done yet or just doesn't mention is that you can configure
.container
services with systemd-podman units (often called quadlets), e.g. a simple MariaDB container would look like this:Short intro Full reference
This is superb, because it means your containers finally feel well-integrated with the rest of the OS and you can use systemctl, journalctl, etc. just like you would with other services.
Personally, I use this as an alternative to Podman/Docker compose and have been very happy with it running rootless containers from Nextcloud, Pufferpanel, Forgejo, Authentik, etc. (ask me for .container files if you need any help, I'm currently working on a small repo with a collection)
Excuse me, peasant crontab enjoyer here, but what?! I could write a (mostly) declarative system without having to learn Nix?! I should probably be learning systemd anyway, it's looking more and more like the present, let alone the future.
I run a bunch of remote reverse proxies that are functionally identical, but for having a different Cloudflare key and calling for a different static IP
Could I write the entire config to a self hosted Git > pull that repo > change those two variables and have a running machine?
Remote updates have been kicking my ass, I either can't wrap my head around Screen or it isn't fit for my need. Being able to pull the new config from Git over Tailscale and then run it would be game changing for me.
If you need a half step on your journey, convert your crontab to systemd timers first.
In fact, I do need a half step. Legend, thank you.