-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
What environment variables should we use for database configuration? #2400
Comments
@ri8ika , I think the error occurred because the IP is not correct. I haven't tried it on Heroku but I think you need to modify the |
I'm transferring your issue to |
You might also wanna see: Hope it helps. |
Hmm, I'm still getting the error even after using Procfile to run index.js when I try to migrate:
I also tried setting up |
Sorry, i misunderstood your issue and it's actually complaining about cannot connect to the Postgresql. Looking at the code snippet in the original comment, should
|
Good catch. But I'm still having same issue. |
@ri8ika, one last thing I can think of. In this tutorial https://loopback.io/doc/en/lb4/Deploying-to-IBM-Cloud.html#updating-application, it binds the new value in
I'm not sure what's the difference between setting it here vs in application.ts, perhaps @hacksparrow might be able to answer. |
Still no luck. |
@ri8ika, I wasn't able to reproduce this issue. Since this issue was opened more than a year ago, I'd like to close this issue as non-reproducible. If you still encounter this issue, please feel free to ping here or open a new issue. Thanks. |
After following medium blog, I set the following variables:
But this is not working.
After some research I found this issue:
strongloop/loopback-boot#4
But I am still not sure what database environment variables are available to use in loopback 4.
For further information, I have used the followings inside application.ts inside the constructor:
I think this is not getting bound, because when try to run migrate on heroku, I get the following error:
The text was updated successfully, but these errors were encountered: