aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/app_rails_loader.rb
Commit message (Collapse)AuthorAgeFilesLines
* application loader refactor and test suite complete rewriteXavier Noria2013-04-111-28/+27
|
* code review of 22e5ab3Xavier Noria2013-04-101-8/+7
|
* Searching for rails executable correctlyPrathamesh Sonpatki2013-04-101-16/+11
| | | | | | | | | | * Current logic of finding Rails executable in parent directory is not returning full path of executable if it is found in one of the parent directories * To compensate for this, we have to call exec_app_rails recursively until the executable is found or we cant do 'chdir' anymore * This solution finds the correct executable path from parent directory(s) recursively
* Explain how to upgrade bin/ for Rails 4Jeremy Kemper2013-04-091-8/+29
|
* fix binstub typoAndre Arko2013-03-301-1/+1
|
* need to delete bin, not binstub, update wordingAndre Arko2013-03-271-4/+4
|
* script/rails could never be from bundlerAndre Arko2013-03-271-1/+1
|
* rails commands even if bin/rails is a gem stubAndre Arko2013-03-201-10/+20
|
* Fix backwards compatibility with Rails 3 apps.Steve Klabnik2013-02-221-8/+16
| | | | | | | | | | | | | | | When we removed script/rails and introduced bin/rails, we accidentally introduced a regression. If you install Rails 4 as a gem, then try to do something in a Rails 3 application: $ rails g This will throw the 'please type rails new foo' message rather than the proper generator documentation message. This is because older apps don't have bin/rails. Therefore, we now *prefer* bin/rails, but still search for script/rails, and exec the one we find.
* Introduce ./bin for your app's executables: bin/bundle, bin/rails, bin/rake. ↵Jeremy Kemper2013-01-061-0/+29
Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'