Installed bins are not refreshed.

[coffeeaddict]

The bins that are places in shared/bin are not refreshed per-deploy.

As we, at our site, only keep 5 previous releases this means that after the fifth consecutive release the specified Gemfile is gone, when using the supplied defaults.

This is what my unicorn_rails file looks like:

#!/usr/bin/env ruby
#
# This file was generated by Bundler.
#
# The application 'unicorn_rails' is installed as part of a gem, and
# this file is here to facilitate running it.
#

require 'pathname'
ENV['BUNDLE_GEMFILE'] ||= File.expand_path("../../../releases/20131211121115/Gemfile",
  Pathname.new(__FILE__).realpath)

require 'rubygems'
require 'bundler/setup'

load Gem.bin_path('unicorn', 'unicorn_rails')

The 20131211121115 directory has been (long) reaped by Capistrano in order to keep things clean.

I see 3 solutions:

• Rewrite files in shared/bin to point to ../../../current/Gemfile (rewriting files is a bad idea)
• Remove the (appropriate) files in shared/bin before each bundle:install (removing all files might have unwanted side effects, so you need some sort of manifest)
• Pack the files in release_path.join('bin') by default

Is there any speaking against the last option?

[Kriechi]

What do you mean by "The bins that are places in shared/bin are not refreshed per-deploy."?
I just checked in one of my projects, and the bins are updated. So each file in bin/ is touched at the last deploy date+time (as listed in revisions.log). And the content in each bin-file mentions the correct Gemfile-path.

[tsechingho]

@coffeeaddict The gemfile path of each bins in shared/bin will change it's value while the bundle --gemfile --binstubs is executed each time.

[coffeeaddict]

I am not sure what has been happening there, but it seems resolved now... May have something to do with dying-off deployments due to reconfiguration. I'm closing (and forgetting) this.

Thnx anyway!