For those you’d need to scan your dick in UK.
For those you’d need to scan your dick in UK.
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.
That’s the video in this post
Sounds like a land of burgers
dude where do you live
deleted by creator