Prisma

<@U82V6UE1H>, yes that's expected. what problems are you running into?

you can configure the number of connections using the env vars `SQL_CLIENT_CONNECTION_LIMIT` and `SQL_INTERNAL_CONNECTION_LIMIT`

Oh, good to know :smile: It’s been 2 times already that the server along with prisma that I deployed and keep in one docker-file is failing after some time (Not sure how much, but let’s say 12 hours). Now I moved DB to AWS to see if it was the DB fault

I can’t provide any logs currently, but I will definitely keep logs if this happends again

In addition there is not much traffic, as it’s test environment, mostly close to 0

ah you can't :smile: ok, you can do `docker logs -f &lt;prisma container id&gt;` when it happens again

As I said, I don’t have error logs now. Failing, means that I can’t use the server, and when I went inside with `docker logs prisma` I’ve seen that prisma failed because it couldn’t connect to the db

on the other hand `docker logs db` said the db is running and listening on port

you should probably set up a separate DB with AWS RDS for example

Yeah, I did that right now. Let’s see how it goes. I will write if it happens again :slightly_smiling_face: