Submitted 1 year ago by rglullis@communick.news to selfhosted@lemmy.world
https://major.io/p/quadlets-replace-docker-compose/
Dependencies within unrelated projects (ie, sharing a single database container for a few unrelated apps) is something that would be pretty handy, and is missing from compose.
Auto-updates are cool - but also dangerous... I think there's something in running watchtower manually like I have been - when something breaks straight after, I know the cause.
Couldn’t you just create a compose file for a database separately?
I don't really understand what you're suggesting. Having a seperate compose file for your database would "work", but you'd lack any of the dependency handling.
Honestly, this is kinda making me wanna redeploy a couple app stacks I have on a VPS. Hmm.
Oh, well that’s simple…
thevoiceofra@mander.xyz 1 year ago
Interesting. But what If I’m not using CoreOS? Also RedHat fucked up by using YAML for configuration.
kylian0087@lemmy.world 1 year ago
What is wrong with YAML for configuration? It is much more easy to read then say json.
anyhow2503@lemmy.world 1 year ago
YAML is way too bloated of a standard and has a ton of inconsistencies between implementations, despite the widespread reputation of simplicity. It is easy to read as long as you limit yourself to a fraction of its capabilities and err on the side of caution when it comes to escaping characters (especially when number literals are involved, or booleans for that matter). As far as alternatives go, I prefer TOML for simple key=value configs, but it has its own issued and is nowhere near as featureful, for better or worse.
brian@programming.dev 1 year ago
There is some surprising behavior with some of the features of yaml, mostly arising from the fact that it looks nice to read. Here’s a list of things that you can avoid to avoid a lot of the pitfalls: hitchdev.com/strictyaml/why/ . I haven’t actually used strictyaml, but the arguments it presents are pretty solid and some are things I’ve run into in real environments
thevoiceofra@mander.xyz 1 year ago
If you’re just reading configs then yeah, it’s superior. If you’re maintaining big complex configurations you need something to reduce boilerplate. Jsonnet, nickel or nix are excellent here. So you’re forced to use one of those, generate yaml, and deploy. One more moving thing in your pipeline which can break.
sasoiliev@lemmy.world 1 year ago
JSON was never meant for configuration.
YAML has a ton of footguns.
losttourist@kbin.social 1 year ago
Podman runs on any distro (or more strictly: any distro that uses systemd).
lemmyvore@feddit.nl 1 year ago
…except I can run Docker anywhere. It’s not tied to systemd. These quadlets seem like a very systemd-specific thing. Which is great if you’re building everything around systemd but it’s a niche.
poVoq@slrpnk.net 1 year ago
It’s built into Podman 4.x, so you can easily install it on any distro (with Systemd).