hi guys, sorry if this is a newbie question but I'...
# orm-help
r
hi guys, sorry if this is a newbie question but I've already spent a lot of time trying to figure out a solution and not even close. I was hoping someone could give me a direction. I created a project using the node-basic boilerplate and I want it to use a local postgres database. So, I created a temp folder, ran
prisma init
, copied the docker-compose file to the database folder, removed the endpoint key, ran prisma init and then got a new endpoint key in the prisma.yml file. I ran
docker-compose up -d
and it was fine, then when I ran prisma deploy I get this:
Error: Could not connect to server at <http://localhost:4466>. Please check if your server is running.
. Am I missing anything? For what I understand I need 2 servers, the one created by docker-compose which is where Prisma sits, and then the web server to consume it.
r
The error says that prisma server, your application server is trying to connect to, is not running. It starts when you do
docker-compose up -d
. Can you please run
docker ps
and confirm if prisma container is up?
r
Yes, it's running. When I add the
export DEBUG="*"
I get a bunch of errors with
FetchError: request to <http://localhost:4466/management> failed, reason: socket hang up
and
FetchError: request to <http://localhost:4466/management> failed, reason: connect ECONNREFUSED 127.0.0.1:4466
. There's an open issue on the repo, apparently no solution yet
r
Hmm, that's weird. If prisma container is running you should not get above error. I found following issues logged which might help: https://github.com/prismagraphql/prisma/issues/2548 https://github.com/prismagraphql/prisma/issues/2479
r
Thank you @Raeesaa, I checked the docker logs and I'm getting "connection not available", which already has a issue reported
👍 1
n
I can think of multiple causes for "connection not available" please create a new issue if you feel that the existing ones don't cover your cause.