cc: build-based deploy — cal.diy publishes no prebuilt release images

Verified: Docker Hub calcom/cal.diy has 0 tags; scarf/ghcr mirrors serve none.
The upstream Dockerfile + compose build args are the deploy path.
This commit is contained in:
hausgeist committed 2026-09-28 00:23:53 -07:00
1 parent b1173fc8c3
commit 3dbad3113d
2 files changed
+13 -4

No files matched your search

+8 -2
View File
@@ -49,7 +49,7 @@ git add -A && git commit -m "cc: bump to v6.2.1 (issue #11)"
git push cc cc
```
Then re-run `playbooks/caldiy-deploy.yml` to pull the new image and migrate.
Then re-run `playbooks/caldiy-deploy.yml` to rebuild the image and migrate.
## Manual deploy (if not using ansible)
@@ -57,5 +57,11 @@ Then re-run `playbooks/caldiy-deploy.yml` to pull the new image and migrate.
git clone --branch cc https://git.commonscomputer.com/commonscomputer/cal.diy.git /opt/caldiy
cd /opt/caldiy
cp cc.env.example .env # then fill RELEASE secrets (see generation notes in cc.env.example)
# cal.diy publishes no prebuilt images for releases — build from source:
docker compose -f docker-compose.yml -f docker-compose.cc.yml build calcom
docker compose -f docker-compose.yml -f docker-compose.cc.yml up -d database redis calcom
```
```
The cal.com build is heavy (~20-40 min on first run: yarn install + Next.js
production build); give the host 6+ cores / 8 GB RAM (the caldiy CT is sized for
this). Subsequent builds are fast thanks to the layer cache.