It came out of a similar approach, but my Capistrano scripts quickly grew unmaintainable. So instead I check my Necktie script into Git, and use a Capistrano task (cap necktie) to pull it and run it on the remote server. A single script that runs locally (on the remote machine) is easier to work with.

http://blog.labnotes.org/2009/11/04/necktie-dress-to-impress/

Nice post. I’m very tempted to enhance this by calling a Puppet manifest (or if you really twisted my arm, Chef recipe) to manage all the dependencies, including crontabs, etc. Not a fan of sudo in Capistrano tasks generally but I’d probably make an exception in this case.

Best

Julian