From c43abb1adecc9f05af47eecf234e6ebc57961bfa Mon Sep 17 00:00:00 2001 From: John Riviello Date: Wed, 11 Jun 2014 17:47:13 -0400 Subject: There are 3 caveats to Local Precompilation including 1 config change not 2 caveats with one of them being 2 config changes [ci skip] --- guides/source/asset_pipeline.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'guides') diff --git a/guides/source/asset_pipeline.md b/guides/source/asset_pipeline.md index 526126e93d..423b915873 100644 --- a/guides/source/asset_pipeline.md +++ b/guides/source/asset_pipeline.md @@ -856,10 +856,12 @@ duplication of work. Local compilation allows you to commit the compiled files into source control, and deploy as normal. -There are two caveats: +There are three caveats: * You must not run the Capistrano deployment task that precompiles assets. -* You must change the following two application configuration settings. +* You must ensure any necessary compressors or minifiers are +available on your development system. +* You must change the following application configuration setting: In `config/environments/development.rb`, place the following line: @@ -873,9 +875,6 @@ development mode, and pass all requests to Sprockets. The prefix is still set to would serve the precompiled assets from `/assets` in development, and you would not see any local changes until you compile assets again. -You will also need to ensure any necessary compressors or minifiers are -available on your development system. - In practice, this will allow you to precompile locally, have those files in your working tree, and commit those files to source control when needed. Development mode will work as expected. -- cgit v1.2.3