thevoiceofra@mander.xyztoSelfhosted@lemmy.world•Working on an emulated-OS docker containerEnglish
1·
1 year agodeleted by creator
deleted by creator
If you’re just reading configs then yeah, it’s superior. If you’re maintaining big complex configurations, possibly for multiple machines, you need something to reduce boilerplate. Jsonnet, nickel or nix are excellent here. So the best way is to use one of those, generate yaml, and deploy. Saves you a lot of headaches but it’s one more moving thing in your pipeline which can break.
Interesting. But what If I’m not using CoreOS? Also RedHat fucked up by using YAML for configuration.
anything similar for amd?
>put messages into someone else’s system
>don’t read privacy policy
>someone else uses your messages
surprisedpikatchu.jpg