Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using current_path vs release_path #33

Closed
eLod opened this issue Feb 4, 2014 · 1 comment
Closed

Using current_path vs release_path #33

eLod opened this issue Feb 4, 2014 · 1 comment

Comments

@eLod
Copy link

eLod commented Feb 4, 2014

related: #31, tablexi/capistrano3-unicorn#10

i'm not sure if this is a problem, but i noticed, that when using capistrano/rbenv, capistrano/bundler and capistrano3-unicorn and trying to do zero downtime restarts, that unicorn's BUNDLE_GEMFILE path points to the old release (please see the related capistrano3-unicorn issue for my setup) when unicorn was actually started, and does not get refreshed upon deploys (when unicorn is gracefully restarted).

edit: same when using capistrano/rbenv master

@eLod
Copy link
Author

eLod commented Feb 6, 2014

not sure if BUNDLE_GEMFILE is set by bundle exec or unicorn, and whether it's a bug that it does get resolved through symlinks (e.g. bundle exec unicorn is run from capistrano's current release path which is a symlink to one of the releases, the environment variable shows the release path, and thus leads to problems when trying to gracefully reload unicorn), but it's definitely not a bug in capistrano/bundler so i'm closing this issue.

@eLod eLod closed this as completed Feb 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant