You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: