Sprinkle and passenger-stack v Deprec

Anton Jenkins | March 05, 2009

I decided to give passenger-stack a quick spin and I’ve got so say I’m impressed. I love the whole idea of being able to write recipes to build a server. It’s definitely the way forward as it’s so much easier having a DSL to spec a server.

However I don’t think I’ll be moving away from deprec just yet. The aim of sprinkle and passenger-stack is to be technology agnostic and it’s a great idea. Deprec is purely aimed at getting your rails app up and running as quickly as possible and it scratches this itch perfectly. And once you are running it’s the little touches which you start to appreciate. I’ve fallen in love with the way you can do something along the lines of :

1
2
3
4
5
6
7
8
cap deprec:passenger:config_gen

# Edit the newly created config files

cap deprec:passenger:config

# The config files are now pushed on to the server 
# and the relevant service is bounced!

This way of generating and pushing configuration changes to the components that deprec has installed is a fantastic time saver and I’m not sure how I could live without it now that I’ve been so spoilt.

In summary

So I guess what I’m getting at is passenger-stack and sprinkle is a really elegant solution, but if you are purely using this for rails then I’d personally be inclined to stick with deprec if it still works for you. However….. if there was a way of abstracting out the configuration goodness from deprec and mixing it with the actual building steps which passenger-stack and sprinkle performs then I think we’d have a perfect solution! Taking the best parts from both and mixing them together. Sounds great!

comments powered by Disqus