Skip to content
Browse files

Update config.assets.initialize_on_precompile warning to include engi…

…ne side affects
  • Loading branch information...
1 parent 5fdcda8 commit d3223b5b65c50e675da3f5d4726a5baa0d9f2010 adman65 committed Mar 22, 2012
Showing with 3 additions and 1 deletion.
  1. +3 −1 guides/source/asset_pipeline.textile
View
4 guides/source/asset_pipeline.textile
@@ -409,7 +409,9 @@ cannot see application objects or methods. *Heroku requires this to be false.*
WARNING: If you set +config.assets.initialize_on_precompile+ to false, be sure to
test +rake assets:precompile+ locally before deploying. It may expose bugs where
your assets reference application objects or methods, since those are still
-in scope in development mode regardless of the value of this flag.
+in scope in development mode regardless of the value of this flag. Changing this flag also effects
+engines. Engines can define assets for precompilation as well. Since the complete environment is not loaded,
+engines (or other gems) will not be loaded which can cause missing assets.
Capistrano (v2.8.0 and above) includes a recipe to handle this in deployment. Add the following line to +Capfile+:

0 comments on commit d3223b5

Please sign in to comment.
Something went wrong with that request. Please try again.