Thought canarying would be difficult to shoehorn in, *but* it's just a matter of having a serivce listen to a non-main branch.
also lot of fun to poke a serivce's git repo with another tool and see it changing
gitopper status checking, rolling back and then rolling forward again.
it appeared (via email), but by now it's stale :/
Need a better name to create another repo to start some coding
@miek I like your thoughts. I think you’re right about something missing in this space: canaries and rollbacks. Having tried my hands at Puppet and Chef, I really loathe client-side processing where what is doing the processing needs bootstrapping with Ruby gems and similar. A simple statically-linked client-controller binary with limited/zero plugin capability would be :chef kiss:.
Never liked the current crop of provisioning tools (for bare metal). Tried to write down a design of what I think I actually need: https://miek.nl/2022/november/15/provisioning-services/
To be clear:
No. Nobody should have an opinion on things like MAX_THREADS or CONCURRENCY_POOL or WEB_COUNT in your application.
Its not an "education" problem with administrators not understanding your stack. Its application problem, and in this case a programming language problem.
Your app should dynamically allocate itself as needed like nginx, redis, postgres and all the other services.
We shouldn't be asking operators to get "good" at doing "bad" things.
Decided to look at network stats again. There are 1M more people using #Mastodon today than there were on October 27.
Everyone is welcome as long as you follow our code of conduct! Thank you. Mastodon.cloud is maintained by Sujitech, LLC.