Follow-up: 3 years of automation with Puppet

Want to help support this blog? Try out Oh Dear, the best all-in-one monitoring tool for your entire website, co-founded by me (the guy that wrote this blogpost). Start with a 10-day trial, no strings attached.

We offer uptime monitoring, SSL checks, broken links checking, performance & cronjob monitoring, branded status pages & so much more. Try us out today!

Profile image of Mattias Geniar

Mattias Geniar, November 18, 2014

Follow me on Twitter as @mattiasgeniar

Yesterday I blogged about my lessons learned after 3 years of using Puppet. In reply, @roidelapluie also posted his list of lessons learned. Accidentally, also after 3 years. Go figure.

And he touches on topics I didn’t think of, but I can only agree on what he said.

Using Puppet does not mean your infrastructure is managed correctly. You need to ask yourself the right questions, because automation is not a goal. Automation brings you a lot of different tools, an overview of your infra, but it will not erase your technical debt. It can even be the opposite.@roidelapluie

Read the full article at his blog, 3 years of automation with Puppet.



Want to subscribe to the cron.weekly newsletter?

I write a weekly-ish newsletter on Linux, open source & webdevelopment called cron.weekly.

It features the latest news, guides & tutorials and new open source projects. You can sign up via email below.

No spam. Just some good, practical Linux & open source content.