Unicorn doesn't play nice with Capistrano deployment?

Konstantin Gredeskoul kig at wanelo.com
Wed May 9 19:33:15 UTC 2012

I highly recommend using the gem for this:

instead of rolling your own.  I typically start unicorn (and any other
task) by first doing a CD into the application directory (either
release_path or current_path depending on when during your deployment
the command runs).

When you set this up, please check your
config/unicorn/"#{Rails.env}".rb, perhaps that is what's pointing to
the wrong path?

Hope this helps

On Wed, May 9, 2012 at 12:29 PM, Luis Fernando Urrea
<lfurrea at simplecs.net> wrote:
> I am having issues when using unicorn with a Capistrano deployment.
> >From what I have been able to understand Capistrano uses a scheme in
> wich every release is deployed inside the releases directory under a
> unique name and if the transaction was successful, creates a symlink
> named current that will point to that release.
> So I end up with a deployment directory such as:
> /home/deployer/apps/sample_app/current
> Then when I try to start unicorn from the binstubs directory all the
> unicorn methods look for things in the following path, particularly in
> the configurator.rb module:
> /home/deployer/apps/sample_app
> I haven't been able to fully understand how unicorn sets the
> working_directory from here:
> https://github.com/defunkt/unicorn/raw/master/lib/unicorn/configurator.rb
> But I wanted to check with the community if I am missing something
> evident due to the noob nature in me.
> --
> O: 2248-2483
> C: 8723-2518
> _______________________________________________
> Unicorn mailing list - mongrel-unicorn at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-unicorn
> Do not quote signatures (like this one) or top post when replying


Konstantin Gredeskoul
CTO :: Wanelo Inc
cell: (415) 265 1054

More information about the mongrel-unicorn mailing list