Unicorn doesn't play nice with Capistrano deployment?
rob at roberocity.com
Wed May 9 19:47:47 UTC 2012
I'm going to a bit off your topic but for good reason. I was finally
annoyed by capistrano for other reasons and went with a simple git
I setup my remote repo to post to a url in the app when a commit
happens. The action of that URL is summed up in this gist:
I also use this because I can make changes on github directly or on
the server and commit the changes to cause the same code refresh and
worker restart. It's also nice that the app on the server is an actual
I don't have experience with the capistrano-unicorn gem; that gem may
be more of what you're looking for.
On Wed, May 9, 2012 at 2: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:
> 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:
> I haven't been able to fully understand how unicorn sets the
> working_directory from here:
> 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
> Do not quote signatures (like this one) or top post when replying
More information about the mongrel-unicorn