Closed andrewhavens closed 11 years ago
I think that this gem does something naughty with the database upon initialize (like accessing a model,etc) that prevents the config.assets.initialize_on_precompile = true
case working.
Sorry for terseness, but here's a quick fix: https://devcenter.heroku.com/articles/labs-user-env-compile
Yeah; I understand why you're doing it. :-)
Please see refinery/refinerycms#1751
@robyurkowski that was a quick fix: https://devcenter.heroku.com/articles/labs-user-env-compile @parndt I think you are answering a comment I quickly deleted because I realized that I misread your original comment. =]
was this ever resolved? I'm still seeing this issue on
gem "refinerycms-page-images", :git => "git://github.com/resolve/refinerycms-page-images.git", :branch => "2-0-stable"
Did you enable user-env-compile
?
I just did, and it worked.
However, it's not clear to me what the actual root of the problem is however.
The only config/vars I added for this gem was my s3 configuration (keys/bucket/etc) -- and I don't know why it'd be needed during asset pre-compilation.
If "that's just the way it is" I think this would be important to put in the readme to save everyone a few minutes of their life.
Sure, could you please send a pull request? It's just the way it is with Heroku and this extension, unfortunately.
Fixed by #85
@parndt How is this issue fixed now that Heroku has deprecated user-env-compile?
@LoganDSPrice have you encountered the issue?
So now that I've added the refinerycms-page-images gem and deploy to heroku, when it goes to pre-compile the assets to add to the slug, it fails with the message:
I am running Rails 3.2.6 and refinerycms/refinerycms-page-images '~> 2.0.0'
I found some articles online which say they solved the issue by adding this line to their config/application.rb file:
But that resulted in a different error for me:
Now I dont know what to do to fix this. What should I do?