diff --git a/doc/CHANGELOG b/doc/CHANGELOG
index 0381c08c..a6c7a995 100644
--- a/doc/CHANGELOG
+++ b/doc/CHANGELOG
@@ -22,6 +22,8 @@ New and changed features
 * Czech locale has been renamed from cz to cs to follow ISO standards
 * The toggle-notes and toggle-collapsed-containers have been moved into the view
   menu
+* Assets are no longer identical across environments, so the environment
+  must now be specified during asset precompilation.
 * Bugfixes
 * Tracks is tested on Ruby 1.9.3, 2.0.0, and 2.1
 
diff --git a/doc/installation.textile b/doc/installation.textile
index 5ac6628d..d535e2b3 100644
--- a/doc/installation.textile
+++ b/doc/installation.textile
@@ -78,7 +78,7 @@ 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. bundle exec rake assets:precompile
+bc. bundle exec rake assets:precompile RAILS_ENV=production
 
 
 h2.  Start the server
diff --git a/doc/upgrading.textile b/doc/upgrading.textile
index efb85ced..99a027d2 100644
--- a/doc/upgrading.textile
+++ b/doc/upgrading.textile
@@ -10,7 +10,7 @@ That said. To upgrade:
 # 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 intend to test or develop on this tree.
 # 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@.
+# Precompile your static assets (css, javascript, etc.) by running @bundle exec rake assets:precompile RAILS_ENV=production@.
 # Run @bundle exec rails server -e production@ inside your Tracks 2.3devel directory to start up Tracks. Or use @-e development@ if you intend 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.