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
Yields the connection URI: postgres://someuser:somepassword@/tmp:5555/somedatabase
This blows up with: error: no pg_hba.conf entry for host "127.0.0.1", user "someuser", database "tmp:5555/somedatabase", SSL off.
Since the format of the config object matches what node-postgres expects, couldn't that just be passed straight on to its new Client() function instead? Patching it to just set DATABASE_URL = json; seems to work in my, albeit very limited testing.
The text was updated successfully, but these errors were encountered:
The way that the DB connection URI is put together in the
readJson
functionin https://github.com/salsita/node-pg-migrate/blob/master/bin/node-pg-migrate#L185, causes connections to fail when specifying a socket rather than TCP connection via a configuration file.
For example, a config of:
Yields the connection URI:
postgres://someuser:somepassword@/tmp:5555/somedatabase
This blows up with:
error: no pg_hba.conf entry for host "127.0.0.1", user "someuser", database "tmp:5555/somedatabase", SSL off
.Since the format of the config object matches what node-postgres expects, couldn't that just be passed straight on to its
new Client()
function instead? Patching it to just setDATABASE_URL = json;
seems to work in my, albeit very limited testing.The text was updated successfully, but these errors were encountered: