This repository was archived by the owner on Oct 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 29, 2025. It is now read-only.
docker compose up -d calcom is misleading, it still runs database #334
Description
I run my own postgresql for several other things, so I connected calcom to that as well. It works fine there.
docker compose up -d calcom says it just runs calcom however it runs database too
I have deleted the database config out of the docker file and it seems to work just fine. So this leads me to believe it should be doing that already?
I see the prisma thing is also marked there to be deleted.
I believe the docker compose up -d calcom should ONLY run calcom and nothing else. As it claims to do.
Activity
voska commentedon Feb 29, 2024
General consensus is separate db containers for each service: https://www.reddit.com/r/docker/comments/dwlvt6/one_database_per_container_or_one_for_everything/
G2G2G2G commentedon Feb 29, 2024
Your docker gives the option to use a separate database, so the poor performance community isn't relevant.
If you're already using a remote db, there's no reason to run another database that isn't even being used.
asdf4w3t5 commentedon Feb 29, 2024
As said that isn't part of the discussion here.
But reading your thread, no it isn't, did you read that thread? Top comment discusses differences and benefits of single. Some other comments straight up say single is better. The thread is very split up with majority of upvotes swaying toward 1 large database.
You're giving the option to not use your database, therefore it shouldn't be running.
Why run more things that don't get used? That's what this issue thread is about.
Regardless postgresql has streaming replication and async / sync redundancies for offsite.