blueprint

Indeed! I'm showing my age, but I do remember using this with Puppet and it was one of my inspirations :D (no commits in nearly 13 years, ouch) https://github.com/devstructure/blueprint

The tool is quite old, and haven't seen updates in some time. https://github.com/devstructure/blueprint

I don't have a ton of experience with any of them, but fig.yaml looks dramatically simpler and easier to learn than Chef or Puppet. (It also solves a much narrower problem, but I think the point remains.) What this needs is the ability to be pointed at a working VM - lets say, Ubuntu 13.10 server - and then just figure out whats different about it, compared to the distro release. It sounds like you want Blueprint (https://github.com/devstructure/blueprint). But careful what you ask for... I found this to not actually be a very useful approach in practice.

Look at blueprint: https://github.com/devstructure/blueprint/ Right now it has frontends for bcfg2, cfengine, chef, puppet and shell scripts. It's not perfect, but it does a pretty good job of giving you a base set of provisioning rules you can then refine by hand.

https://github.com/devstructure/blueprint [generates] configuration sets for "Puppet or Chef or CFEngine 3." https://en.wikipedia.org/wiki/Comparison_of_open-source_conf... https://ops-school.readthedocs.org/en/latest/config_manageme...

Blueprint author here. Our goal is dead simple configuration management, so it might be just what you need. Check it out and feel free to email me with any questions matt@devstructure.com Blueprint (https://github.com/devstructure/blueprint) Blueprint I/O (https://github.com/devstructure.com/blueprint-io)

Puppet and Chef are pretty agnostic. You can use them to manage only your infrastructure (packages, user accounts, databases) and leave app deployment up to something like capistrano or fabric if you like (although at a certain level of app complexity it makes sense to integrate.) cfengine has been around longer, but seems to have negative adoption since puppet became well-known. I know a few people who swear by it, though. FWIW, at my current startup I use Chef to manage a mid-sized collection of servers (app, load balancers, DBs/replicas, task processors) where the app is written mostly in Python, and it took a ton of pain out of scaling up to deal with a very large paying customer two nights ago. Puppet has better documentation, but learning either is a bit of a trial and error process I think. You might find Blueprint (https://github.

> Has this been done already? A more general approach which also covers python/php modules as well as system packages, configuration files, installed software on /usr/local , .. is blueprint https://github.com/devstructure/blueprint / http://devstructure.com/ What it basically does is to analyse your system, create a list of packages and files, save it in a git repository and allows you to export it to various different formats like shell script or puppet or chef. Btw. this is IMHO a really big deal. Not only can you clone your environment easily, but it helps you to create a managed environment as you have at least a starting point to create your puppet manifests/chef recipes or at least shell scripts. And as it uses git you can easily use it to create distributed configuration backups of your systems. Oh and as the default output for

DevStructure co-founder here, sorry to hear about your experience. Not sure when you installed blueprint, but we've recently open-sourced it and it's been ported to python. Should require minimal "stuff" to use it. Let us know if you have any questions or problems and again my apologies. https://github.com/devstructure/blueprint