kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Remove Capistrano from asset pipeline guide

Browse source
This commit is contained in:
Gannon McGibbon 2019-09-14 21:01:33 -04:00
parent bf5530df68
commit 730046e667
1 changed files with 1 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
guides/source/asset_pipeline.md
View file

@ -677,17 +677,6 @@ The command is:
$ RAILS_ENV=production rails assets:precompile $ RAILS_ENV=production rails assets:precompile
``` ```
Capistrano (v2.15.1 and above) includes a recipe to handle this in deployment.
Add the following line to `Capfile`:
```ruby
# Capistrano version 2
load 'deploy/assets'
# Capistrano version 3
require "capistrano/rails/assets"
```
This links the folder specified in `config.assets.prefix` to `shared/assets`. This links the folder specified in `config.assets.prefix` to `shared/assets`.
If you already use this shared folder you'll need to write your own deployment If you already use this shared folder you'll need to write your own deployment
command. command.
@ -793,9 +782,8 @@ duplication of work.
Local compilation allows you to commit the compiled files into source control, Local compilation allows you to commit the compiled files into source control,
and deploy as normal. and deploy as normal.
There are three caveats: There are two caveats:
* You must not run the Capistrano deployment task that precompiles assets.
* You must ensure any necessary compressors or minifiers are * You must ensure any necessary compressors or minifiers are
available on your development system. available on your development system.
* You must change the following application configuration setting: * You must change the following application configuration setting: