-
Notifications
You must be signed in to change notification settings - Fork 120
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
Heroku pre-compiling assets fails after Heroku deprecated user-env-compile #146
Comments
I use Refinerycms-page-images on Heroku with no problems. I precompile my assets on my dev systems using
then incorporate changed assets into the git repo using
|
Thanks for the reply! I ran
Any idea how that would be fixed? |
More info: When I run I don't understand why PageImages is unable to find the models. I did follow this guide to be able to use image collections for my models. Is there a chance that is messing things up? I found elsewhere that putting |
If precompile in production isn't completing, then heroku is trying to do the precompile and getting the same error. Try changing your
|
Is your issue fixed @LoganDSPrice ? |
In the Deploying to Heroku section, the instructions state to run
heroku labs:enable user-env-compile -a myapp
in order to properly precompile assets. Heroku has since deprecated that.I've found reference to the Buildpack API, but I don't understand it and how it relates to the precompiling issues with refinerycms-page-images.
I'm getting:
... and so on.
It seems like there has to be a new method for deploying to Heroku while using refinerycms-page-images.
The text was updated successfully, but these errors were encountered: