I built this transactional python deployment system a while back. I didn’t ever mention it because I was waiting to add a few things. But now that I’m looking at it again, I’m remembering that it’s actually pretty cool and some people might like it. Or maybe want to use it as inspiration to create the next best deployment system.

Elsware is a generic deployment system that’s meant to be “hooked” into, and has hooks for transactions.

The initial reason I built this, was for Django. If any of you have used Django you know it uses a “settings” file to describe things about the application. I wanted to be able to keep some information in that settings file so I could type “djangoadmin.py deploy ’somewhere’”. And it would do it for me.

I didn’t ever get all the way there; as I was writing it it ended up being a lot better than I had expected. So I was writing support for a bunch of stuff - essentially built in “actions”.

I’m not going to explain too much technical details, I’ve got some documentation written, and the source code is on gitweb; the docs are ok, but the code is badass. Here’s a good example of how you write deployment config files

If you’re interested in deployment scripting, or frustrated with anything you’re using now, definitely give this a read.

docs
src