Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asset precompilation skip issue #60

Closed
sosedoff opened this issue Oct 4, 2012 · 9 comments
Closed

Asset precompilation skip issue #60

sosedoff opened this issue Oct 4, 2012 · 9 comments

Comments

@sosedoff
Copy link
Contributor

sosedoff commented Oct 4, 2012

I encountered the issue with asset precompilation.

Our app has config option config.assets.compile = false, which triggers exception when required asset (in our case admin.css) is not precompiled. Adding the asset into the precompilation list should solve it: config.assets.precompile += ['admin.css']

Here is the issue. Mina skips asset precompilation and thus causes application to fail after next successful deploy. I fixed it by removing the asset folder and ran the deploy again.

Any tips on this?

@rstacruz
Copy link
Member

rstacruz commented Oct 4, 2012

bundle exec mina deploy force_assets=1

Try that in the meantime.

On Oct 5, 2012, at 12:56 AM, Dan Sosedoff notifications@github.com wrote:

I encountered the issue with asset precompilation.

Our app has config option config.assets.compile = false, which triggers
exception when required asset (in our case admin.css) is not precompiled.
Adding the asset into the precompilation list should solve it:
config.assets.precompile
+= ['admin.css']

Here is the issue. Mina skips asset precompilation and thus causes
application to fail after next successful deploy. I fixed it by removing
the asset folder and ran the deploy again.

Any tips on this?


Reply to this email directly or view it on
GitHubhttps://github.com//issues/60.

@killthekitten
Copy link

It happened to us when we used similar script with Capistrano. Don't know how to solve this problem gracefully, but at least Mina can check application.rb for changes also.

@rstacruz
Copy link
Member

config/application.rb and config/environments/production.rb, considering that's where most store their precompile config. (Personally I'd argue application.rb is the best place to put it in, though)

@ghost
Copy link

ghost commented Mar 25, 2013

I'm having the same issue, any news on a fix?

@killthekitten
Copy link

It is just waiting someone to come and fix it. several month ago I tried to start the work on it, but something stopped me.

@tonytonyjan
Copy link

+1

@d4be4st
Copy link
Member

d4be4st commented Jul 5, 2015

mina only check diff of app/assets and vendor/asses for changes. Does not check any other as you can create your own intialize files which could change assets configs.

Please use mina deploy force_assets=1

@d4be4st d4be4st closed this as completed Jul 5, 2015
@ghost
Copy link

ghost commented Jan 26, 2017

@d4be4st But what about engine assets?

@kazimzaidi
Copy link

Any way to have that option (force_aseets=1) inside the config/deploy.rb ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants