Closed cassioalmeidas closed 1 year ago
Just stopping by (not yet a user of this gem), but I think the problem here is that rails is trying to access to the database to generate assets - this happens with a lot of setups, not just this gem. So ensuring there's a db before deploying to heroku doesn't seem like a problem with this gem.
the critical lines in the output are:
remote: ! Precompiling assets failed.
remote: ! Attempted to access a nonexistent database:
remote: ! https://devcenter.heroku.com/articles/pre-provision-database
remote: ! Attempted to access a nonexistent database:
Seems to be a duplicate of https://github.com/jbox-web/ajax-datatables-rails/issues/388
this gem has an incompatibility with the i18n-js gem (according to the following setup: https://gist.github.com/bazzel/ecdff4718962e57c2d5569cf01d332fe) when first deploying to heroku, shows the following error during assets:precompile task:
The deploy only works successfully if I remove the ajax-datatables-rails gem from the Gemfile or ask heroku to provision the database before anything else: