-
Notifications
You must be signed in to change notification settings - Fork 59
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
Rails assets:precompile tries to connect to DB #11
Comments
@sabudaye You have to add a package to your Heroku setup such as https://postgres.heroku.com or similar for other DB types. |
lol it is because you do not have any database yet set up. In local you have to create the db, run these commands
with that your local database will be recreated, but in your heroku instance if you have a database addon installed you won't have to run those commands manually. Also make sure you run maily_herald migrations! |
@Phitherek, @ssoulless thank you, but i'm already added DB on Heroku and also have db setup on local machine. This issue is not about my db configuration, is about https://devcenter.heroku.com/articles/rails-asset-pipeline#troubleshooting
rails asset:precompile task should not require connection to database, and without maily_herald gem it works fine. |
I found same issues in other gems: |
You also could use the activerecord-nulldb-adapter gem -> https://github.com/nulldb/nulldb http://blog.zeit.io/use-a-fake-db-adapter-to-play-nice-with-rails-assets-precompilation/ |
I'm trying to deploy my application with maily_herald gem to Heroku, and it fails with this reason:
I reproduced this on local machine
RAILS_ENV=production rake assets:precompile
and got this error:
The text was updated successfully, but these errors were encountered: