How does this work?

[harmon]

Hi!

This looks awesome! I'm really glad to see a Ruby deployment project written using NORMAL ruby classes! Rake sucks.

Thor is an especially nice touch. I've been wanting to do something like this for a while.

I had a question though. I'm not quite sure how this gem works. Based on the recipes, it seems that the gem runs on the actual machine you are deploying to? Maybe you could update the README to explain a bit about the mechanics. Do you run it from your dev machine, and it sets up the gem on production? And where does this post-push hook get installed? Is it on your dev box, or github, or the production server?

Thanks, and keep up the good work!

• Adam

[effkay]

Hi @harmon

good questions! And yes, I was trying to get rid of rake and do a more OO syle DSL ;-)

I will try to update the README to clarify what's going on... I had a lighning talk prepped for last Euruko answering all those questions, but didn't get a chance to do it, so It's just a matter of moving those things to the Readme. Meanwhile:

• the recipes are run on the machine you are deploying to, in blazing terminology, the target.
• you run it from your dev machine to handle everything. The triggering of recipes etc. happens trough a git post-receive hook that is triggered on a successfull git push to the remote repository on the server.
• Creation of the remote repository on the server, including the git hook that triggers the deployment recipes is also handled by blazing

I hope that answers your questions for now?

cheers, felipe