Restrict use of Spring binstubs to development

Partial revert of 7d7e47def

Fixes #1692

doc/CHANGELOG

@@ -15,8 +15,6 @@
 == Version 2.3devel
 
 New and changed features
-* Added new binstubs. The commands `bin/rails` and `bin/rake` take the place of
-  the old `bundle exec rails` and `bundle exec rake`, respectively.
 * You can select to group todos on the home page by context or by 
   project (using the view menu). This also works for tag page, the project page, 
   the tickler and the context page

doc/installation.textile

@@ -60,7 +60,7 @@ h2. Configure variables
 
 # In the @config@ folder, copy the files @database.yml.tmpl@ and @site.yml.tmpl@ to @database.yml@ and @site.yml@, respectively.
 # Open the file @config/database.yml@ and edit the @production:@ section with the details of your database. If you are using MySQL the @adapter:@ line should read @adapter: mysql2@, @host: localhost@ (in the majority of cases), and your username and password should match those you assigned when you created the database. If you are using SQLite3, you should have only two lines under the production section: @adapter: sqlite3@ and @database: db/tracks.db@.
-# Open the file @config/site.yml@, and read through the settings to make sure that they suit your setup. In most cases, all you need to change are the @salt: "change-me"@ line (change the string "change-me" to some other string of your choice), the administrator email address (@admin_email@), and the time zone setting. For the time zone setting you can use the command @bin/rake time:zones:local@ to see all available timezones on your machine
+# Open the file @config/site.yml@, and read through the settings to make sure that they suit your setup. In most cases, all you need to change are the @salt: "change-me"@ line (change the string "change-me" to some other string of your choice), the administrator email address (@admin_email@), and the time zone setting. For the time zone setting you can use the command @bundle exec rake time:zones:local@ to see all available timezones on your machine
 # If you are using Windows, you may need to check the 'shebang' lines (@#!/usr/bin/env ruby@) of the @/public/dispatch.*@ files and all the files in the @/script@ directory. They are set to @#!/usr/bin/env ruby@ by default. This should work for all Unix based setups (Linux or Mac OS X), but Windows users will probably have to change it to something like @#c:/ruby/bin/ruby@ to point to the Ruby binary on your system.
 # If you intend to deploy Tracks with the built in webserver called WEBrick, you'll need to change @config.serve_static_assets@ to @true@ in @config/environments/production.rb@ in order for the images, stylesheets, and javascript files to be served correctly.
 
@@ -69,7 +69,7 @@ h2. Populate your database with the Tracks schema
 
 Open a terminal and change into the root of your Tracks directory. Enter the following command:
 
-bc. bin/rake db:migrate RAILS_ENV=production
+bc. bundle exec rake db:migrate RAILS_ENV=production
 
 This will set up your database with the required structure to hold Tracks' data.
 
@@ -78,14 +78,14 @@ h2. Precompile assets
 
 Static assets (images, stylesheets, and javascript) need to be compiled in order for them to work correctly with the new asset pipeline feature in Rails. Precompiling your assets is as simple as running the following command while inside the Tracks root directory:
 
-bc. bin/rake assets:precompile
+bc. bundle exec rake assets:precompile
 
 
 h2.  Start the server
 
 While still in the Terminal inside the Tracks root directory, issue the following command:
 
-bc. bin/rails server -e production
+bc. bundle exec rails server -e production
 
 If all goes well, you should see some text informing you that the WEBrick server is running: @=> Rails application starting in production on http://0.0.0.0:3000@. If you are already running other services on port 3000, you need to select a different port when running the server, using the @-p@ option.
 

doc/upgrading.textile

@@ -9,9 +9,9 @@ That said. To upgrade:
 # Install Tracks 2.3devel in a new directory. Or you can create a separate installation of 2.3 for testing purposes.
 # Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.3devel directory.
 # Check that you have all dependencies installed: @bundle install --without development test@ Or leave out the @--without development test@ part if you intent to test or develop on this tree.
-# Run @bin/rake db:migrate RAILS_ENV=production@ to update your old database to the new schema. This is the point of no return. Make sure you have backups!
-# Precompile your static assets (css, javascript, etc.) by running @bin/rake assets:precompile@.
-# Run @bin/rails server -e production@ inside your Tracks 2.3devel directory to start up Tracks. Or use @-e development@ if you intent to try your changes and get more log info.
+# Run @bundle exec rake db:migrate RAILS_ENV=production@ to update your old database to the new schema. This is the point of no return. Make sure you have backups!
+# Precompile your static assets (css, javascript, etc.) by running @bundle exec rake assets:precompile@.
+# Run @bundle exec rails server -e production@ inside your Tracks 2.3devel directory to start up Tracks. Or use @-e development@ if you intent to try your changes and get more log info.
 
 Please note that if you intend to use Tracks with the built in webserver called WEBrick for production, you'll need to change @config.serve_static_assets@ to @true@ in @config/environments/production.rb@ in order for the images, stylesheets, and javascript files to be served correctly.