Sign in through GitHub

Please read for an updated status on RailsCasts:

Learn more or hide this

Luis Urrea's Profile

GitHub User: lfurrea

Comments by Luis Urrea

Avatar

I had to add /current to the working_directory and others on unicorn.rb

working_directory "/home/deployer/apps/sample_app/current"
pid "/home/deployer/apps/sample_app/current/tmp/pids/unicorn.pid"
stderr_path "/home/deployer/apps/sample_app/current/log/unicorn.log"
stdout_path "/home/deployer/apps/sample_app/current/log/unicorn.log"

Thanks for the great work!

Avatar

Very helpful!! Thanks

I wanted to check with the community is this is still working for everybody.

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.