thanks for the PR, I'll test it

@squatica sorry for the late reply. I would like to keep the entry point file, however, we can make the Postgres part optional depending on some ENV variable. We don't use docker compose in our prod setup. E.g. DATABASE_ADAPTER=postgres by default and you can set it to a different value.

@JannikStreek So you use the docker images, but not with health-checks? Or you don't use docker at all in prod? In general it's better to rely on health-checks, where a container defines its own healthy conditions, and other containers just wait for healthy status. Alternatively you could try to connect to the db normally in the .ts code, and when it fails just throw a fatal and rely on the service manager to restart the backend.

I could keep the entrypoint in repo but not use it in Dockerfile. But I'd recommend to avoid adding the postgresql-client dependency in Dockerfile, because that's essentially duplicated library (your @keyv/postgres already knows how to work with postgres), and it would be dead weight for anybody else who either uses redis or follows the best practices with health-checks.

@squatica we use the docker container, however, not together with docker compose but with Kubernetes. I will double check our configuration and get back to you.