[drewwwwww]

not that this isn't awesome, but it's pretty unfair to heroku to describe this as even close to equivalent to what they do. badger-rails replicates parts of the deploy experience, but heroku does so much more.

i think the title of the post should be changed to avoid making reference to heroku, as badger-rails can and should stand on its own as a useful tool.

[mattvv]

That's true drewwwww. The reason for comparison to heroku though was to draw on the simplicity of deploying a ruby on rails application, which is otherwise very difficult. It's easier to explain this to people using heroku then it is to draw comparisons to peoples experiences with puppet or chef.

To be clear though, badger doesn't just replicate the deploy experience but also the best practices of setting up a rails server, including scaling an infrastructure to the same if not better levels then heroku can currently scale if you have the server power behind it.

We currently use it on one of our own applications that has multiple application servers and webservers, and use badger-rails to scale whenever we need to.