-
Notifications
You must be signed in to change notification settings - Fork 143
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
rake assets:precompile not processing .hamlc #11
Comments
Can you try setting
in your |
You are the best ! I thought I did it, but I did not. It works perfectly. Congrats for the great job, this gem is changing my life :) |
Glad to hear you like it! The hint came from @thibaudgg and I thought it only applies to Heroku. I'll update the README. |
It always happens when you compile your assets in |
This is an awesome gem, thanks. I did have one question specifically about this before I dig into it too much. I was wondering why it needed the full environment to precompile the assets (specifically the |
I haven't played with the |
Yeah, it's definitely a little confusing, and the docs don't help much. The main side effect of that flag (for me) is that it loads the entire rails environment, and initializers and other code that looks for a database connection will be allowed to run. That presents a bit of an issue when you're deploying to Heroku and want to compile resources at slug compilation (they have a writeup on the issue). In any case other types of assets don't require the full environment and I suspect that we could probably get these hamlc templates compiled without it, so I'll dig around a bit and see if I can come up with something. |
The only dependencies are the |
I think I got it (just sent a pull request). Turns out it was a relatively straightforward option to the Railtie initialization. |
When I run "bundle exec rake RAILS_ENV=production assets:precompile", hamlc templates are not compiled. They are just put as is in the /assets directory.
On-the-fly compilation (like in development mode) works perfectly though.
Did I miss something ?
The text was updated successfully, but these errors were encountered: