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
When changing .env file to point to a remote Postgres instance example not working #465
Comments
Might just be running it from the wrong directory. Can you provide a more complete set of reproduction steps? |
So my regular test my env file looks exactly the same as the example: SERVER_ADDR=127.0.0.1:80 I do a post to 127.0.0.1:80/users with { and everything works fine. The record gets inserted into my local Postgres database. Then I installed a remote instance of Postgres onto the Microsoft Azure Cloud environment and changed Upon changing the PG.HOST, When I run my code it seems like it doesnt even use the PG.HOST setting. It always goes locally regardless of what PG.HOST is set to. I can prove this because when I have the PG.HOST point to the remote Postgres instance and I shut down my local postgres instance I get : An error occured while creating a new object: error connecting to server: No connection could be made because the target machine actively refused it. (os error 10061) |
When running this example locally everything works fine, but as soon as I change the
PG.HOST=XXX.XXX.XXX.XXX to a remote postgres instance the example still trys to connect to the local instance.
The text was updated successfully, but these errors were encountered: