You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
update my database.json file with my heroku postgres db connection info
run db-migrate against a remote postgres heroku instance
Heroku only allows remote connections to come over SSL. My understanding is that this requires('pg').native. So I'd love for some way to specify whether I want 'pg' or 'pg' native. Then I can try to run my remote migrations (and I'll let you know if it works or if I run into another issue...).
Thanks!
The text was updated successfully, but these errors were encountered:
What do you think about having db-migrate fall back to loading a database.js file if no database.json file is found? You'd be responsible for exporting the environment configurations similarly to what's found in database.json but it would give you a chance to select the appropriate driver using code rather than a string-based loading convention.
That works for me. It would allow people to connect to other databases as well (admittedly it might not work... but they could try). If you add it, please document an example in the README (I'm happy to help you write it).
In fact, if I can get it working, I'll contribute instructions on how to run against a Postgres instance on Heroku.
Here is what I really want to do:
Heroku only allows remote connections to come over SSL. My understanding is that this requires('pg').native. So I'd love for some way to specify whether I want 'pg' or 'pg' native. Then I can try to run my remote migrations (and I'll let you know if it works or if I run into another issue...).
Thanks!
The text was updated successfully, but these errors were encountered: