Don’t generate binstubs by default

[kirs]

Two reasons:

1. bin/ is often checked out into repo
2. Don't generate binstubs by default when using Rails 4? #45 (comment)

[kirs]

/cc @indirect

[Kriechi]

👍
I'm using that a long time now for all my deployments.

[kirs]

1.1.4 released.

[rmetzler]

Oh damn, I was bitten by this one. I think it is a breaking change and it should have used minor version bump and not a patch version number bump according to semver.

I use the whenever gem which creates cron jobs and uses the release path to find the binstubs. I also had working binstubs until updating. Now my binstubs didn't get updated and when capistrano removed the old releases all my binstubs (e.g. bin/rails runner) ran into "path not found" errors.

[Kriechi]

Are your binstubs not checked into your version control system?
They should... because then they are just part of every new deploy.

[rmetzler]

Thanks for hint. I usually just use bundle exec and don't use binstubs on my dev machine. I also wasn't aware that whenever uses binstubs.

[Kriechi]

Well that was the idea of binstubs - to get rid of bundle exec confusion.
Therefore it makes sense for whenever to use them.

Just generate them properly, add them to git, and never touch them again.