Use bin directory in active way

[sheerun]

From Rails 4 error messages:

Looks like your app's ./bin/rails is a stub that was generated by Bundler.

In Rails 4, your app's bin/ directory contains executables that are versioned
like any other source code, rather than stubs that are generated on demand.

Here's how to upgrade:

  bundle config --delete bin    # Turn off Bundler's stub generator
  rake rails:update:bin         # Use the new Rails 4 executables
  git add bin                   # Add bin/ to source control

You may need to remove bin/ from your .gitignore as well.

When you install a gem whose executable you want to use in your app,
generate it and add it to source control:

  bundle binstubs some-gem-name
  git add bin/new-executable

[sheerun]

Also we should get used to calling bin/rails instead of rails, bin/rake instead of bundle exec rake etc.

[teamon]

Why?

[sheerun]

"When you install a gem whose executable you want to use in your app, generate it and add it to source control:"

[teamon]

Again, why?

[sheerun]

Why we should use bundle exec? I think Rails proposal is very good.

[teamon]

I still haven't head a single argument. Btw - https://github.com/mpapis/rubygems-bundler

[sheerun]

This gem is generating stubs, but outside the directory. Using bin/ commands is especially useful on server side. You don't need to care from which directory you call bundle exec. You're 100% sure the commands are called in context of your project. No need for manually setting ENV variables.

[sheerun]

Any trick using rbenv, rvm or alias is just hack and hiding the truth, that you're really calling stub or bundle exec.

[teamon]

ENV variables? oO

Server side != development. Adding bin to repository does not matter for server side and only makes development harder

[teamon]

rvm or rbenv have nothing to do with bundler

[sheerun]

Of course it matters on server. You can use stubs added to repo on server without any changes.

[teamon]

... or just add --binstubs to bundle install.

[sheerun]

When using --binstubs it isn't clear what commands are supposed to be actually used in application. Also the autosuggestion using tab is much worse.

[teamon]

... on server side ...

[sheerun]

And we will be using Rails 4 in future. The bin directory will be in repository, so bundle install --binstubs will be pain even on development.

[teamon]

I'd suggest more criticism for rails core team. echo /bin >> .gitignore

[sheerun]

I think it's wonderful decision. No need for criticism. Local binstubs should not be placed in repository.

[teamon]

Give me one argument, just one.

[sheerun]

I gave you more than one.

[jandudulski]

I agree that binstubs are better than bundle exec on server side, but as @teamon I don't get any reasons to keep them in repo and during local development. How rails core team arguments such decision?

[sheerun]

I didn't find any argumentation.