avoiding duplicate unicorns starting with Upstart / Init

[danman01]

Hey all,

I was getting two errors that bugged me for a while: my environment variable was being overwritten and I couldn't figure out how to set it within my deploy scripts (e.g. staging and production), and my unicorn process, after unicorn:duplicate, was running into an error and not being able to listen on the appropriate ports. I had to manually send a kill -QUIT to pidfile.oldbin after each deploy to start my new unicorn.

I finally figured out that my init scripts were starting unicorn during the unicorn:duplicate process, and my init scripts had a different environment specified than my deploy.rb.

Here's my setup (in a gist) to handle capistrano-unicorn with monit / upstart / init scripts: https://gist.github.com/danman01/8640750

I was thinking of adding this as a wiki entry as a warning to those who use these scripts (which I would imagine is nearly everyone), but want to verify this is a good enough solution for the wiki (there's nothing over there now - should it be a place for tips & best practices?)

Does anyone have experience running Monit with init / upstart and capistrano-unicorn all in perfect unison? Could you perhaps share your solution with me and we could create a wiki entry for others?

Thanks