search

mina-deploy / mina

Blazing fast deployer and server automation tool
https://rubygems.org/gems/mina
Other
4.35k stars 490 forks source link

The old "force_assets=1" option is mentioned on the "rails:assets_precompile" doc webpage rather than the new "force_asset_precompile=true" one #520

Closed mrj closed 7 years ago

mrj commented 7 years ago

The rails:assets_precompile doc webpage should be updated to mention the new force_asset_precompile=true option rather than the old force_assets=1 one, which no longer works.

lowjiayou commented 7 years ago

I keep getting -----> Skipping asset precompilation though it is a new deployment. I have checked that my project's "current/public/assets" is pointing to "shared/public/assets", and it is empty inside. By adding force_asset_precompile=true parameter do solve my problem. But shouldn't that precompilation run without problem?

Note: I've change the standard flow of "mina deploy" for my project that's why asset precompile had run to separately. I wish to use invoke :'rails:assets_precompile' without extra parameter so that deployment script is much simpler.

d4be4st commented 7 years ago

because to be fast, mina checks diffs of your assets between deploys. if you deploy the same code twice, the second time there wont be any difference between your assets and it will skip precompiling

d4be4st commented 7 years ago

Unfortunately i do not have access to http://nadarei.co/mina/tasks/rails_assets_precompile.html to change that documentation :(