Restrict use of Spring binstubs to development

Partial revert of 7d7e47def

Fixes #1692
This commit is contained in:
Dan Rice 2014-06-27 16:14:25 -04:00
parent 949149c4a6
commit c017b38a3a
3 changed files with 7 additions and 9 deletions

View file

@ -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.