Merge pull request #292 from meith-dev/claude/coolify-compose-deploy

Author: jouwdan

apps/web/public/create-board.sh

@@ -489,6 +489,10 @@ services:
   # always applied before the first request rather than racing it.
   migrate:
     image: ${MEITH_IMAGE:?set this to the image the build workflow's Summary just printed, e.g. ghcr.io/<you>/__MEITH_BOARD_NAME__:latest}
+    # Pull the tag on every deploy. Compose keeps an image it already has, so
+    # a rebuilt `:latest` is otherwise never fetched and a redeploy quietly
+    # runs the old code.
+    pull_policy: always
     environment:
       COMMUNITY_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
@@ -501,9 +505,21 @@ services:
 
   web:
     image: ${MEITH_IMAGE:?set this to the image the build workflow's Summary just printed, e.g. ghcr.io/<you>/__MEITH_BOARD_NAME__:latest}
+    pull_policy: always
     restart: unless-stopped
     mem_limit: ${WEB_MEM_LIMIT:-1g}
     cpus: ${WEB_CPUS:-2}
+    # A readiness probe Coolify gates a rolling deploy on: with "Rolling
+    # update" enabled on the resource, the new container must answer
+    # /api/ready before the old one is retired, so a redeploy swaps in with no
+    # gap. Without it Coolify recreates the stack — old removed, then new
+    # started — and the board is down while the new web boots.
+    healthcheck:
+      test: ["CMD", "node", "-e", "fetch('http://127.0.0.1:3000/api/ready').then(r=>process.exit(r.ok?0:1)).catch(()=>process.exit(1))"]
+      interval: 30s
+      timeout: 5s
+      start_period: 20s
+      retries: 3
     environment:
       # Ask Coolify for a domain on port 3000, then hand the board the same
       # thing with a scheme in front.

docs/getting-started/deployment/coolify.md

@@ -228,6 +228,18 @@ ceilings, which default to a small VPS: `WEB_MEM_LIMIT`, `WEB_CPUS`,
 `MEITH_IMAGE` does, so a larger server is a variable on the resource,
 never an edit to the file.
 
+> [!NOTE]
+> **Redeploys, and deploying without a gap.** The `web` and `migrate`
+> services set `pull_policy: always`, so every **Redeploy** fetches the
+> current image for the tag rather than reusing a `:latest` the host already
+> has — a rebuild on `main` is picked up without pinning a new digest.
+> Coolify recreates a compose stack by default, though: it stops the old
+> containers before starting the new ones, so the board is briefly down while
+> `web` boots. To close that gap, turn on **Rolling update** for the resource
+> (its **General** settings). `web` declares a `/api/ready` healthcheck for
+> exactly this — with rolling enabled Coolify waits for the new container to
+> pass it before retiring the old one, so the swap carries no downtime.
+
 ## 4. Run the installer
 
 Open `https://your-domain/install`.

packages/create-meith/src/scaffold.test.ts

@@ -583,7 +583,7 @@ const SELF_HOST_TREE_DIGESTS: Readonly<Record<string, string>> = {
   '.dockerignore': '620ca0bdf50f76e3817c135ee43afe56669b7b3caaad86b4926021cc52dd3c4b',
   '.github/dependabot.yml': '6cae93a9aa7b08a6f62e94db7c940d74b3657ff81454e6dc6b6e485b1afa3ac8',
   '.github/workflows/build.yml': 'd61b4b1fe933e5fd4d584e63ec45a999e47145529c0c89f9bb9eef0580fb4915',
-  'docker-compose.yaml': 'bb57c62317b1db6572a553f578bc2f603fa63cc69bc45d4ffdf938e044f19960',
+  'docker-compose.yaml': '42bc81028ffce83ae55ac407ece0607b144f73674822610064da3eabe77fc6d1',
   'README.md': 'c2af780df2ca761943117adbe44c4ce464bb6781654dcb9928b78d21066221d4',
 }
 

packages/create-meith/src/scaffold.ts

@@ -823,6 +823,10 @@ services:
   # always applied before the first request rather than racing it.
   migrate:
     image: \${MEITH_IMAGE:?set this to the image the build workflow's Summary just printed, e.g. ghcr.io/<you>/${name}:latest}
+    # Pull the tag on every deploy. Compose keeps an image it already has, so
+    # a rebuilt \`:latest\` is otherwise never fetched and a redeploy quietly
+    # runs the old code.
+    pull_policy: always
     environment:
       COMMUNITY_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
@@ -835,9 +839,21 @@ services:
 
   web:
     image: \${MEITH_IMAGE:?set this to the image the build workflow's Summary just printed, e.g. ghcr.io/<you>/${name}:latest}
+    pull_policy: always
     restart: unless-stopped
     mem_limit: \${WEB_MEM_LIMIT:-1g}
     cpus: \${WEB_CPUS:-2}
+    # A readiness probe Coolify gates a rolling deploy on: with "Rolling
+    # update" enabled on the resource, the new container must answer
+    # /api/ready before the old one is retired, so a redeploy swaps in with no
+    # gap. Without it Coolify recreates the stack — old removed, then new
+    # started — and the board is down while the new web boots.
+    healthcheck:
+      test: ["CMD", "node", "-e", "fetch('http://127.0.0.1:3000/api/ready').then(r=>process.exit(r.ok?0:1)).catch(()=>process.exit(1))"]
+      interval: 30s
+      timeout: 5s
+      start_period: 20s
+      retries: 3
     environment:
       # Ask Coolify for a domain on port 3000, then hand the board the same
       # thing with a scheme in front.

templates/self-host/docker-compose.yaml

@@ -32,6 +32,10 @@ services:
   # always applied before the first request rather than racing it.
   migrate:
     image: ${MEITH_IMAGE:?set this to the image the build workflow's Summary just printed, e.g. ghcr.io/<you>/meith-board:latest}
+    # Pull the tag on every deploy. Compose keeps an image it already has, so
+    # a rebuilt `:latest` is otherwise never fetched and a redeploy quietly
+    # runs the old code.
+    pull_policy: always
     environment:
       COMMUNITY_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
@@ -44,9 +48,21 @@ services:
 
   web:
     image: ${MEITH_IMAGE:?set this to the image the build workflow's Summary just printed, e.g. ghcr.io/<you>/meith-board:latest}
+    pull_policy: always
     restart: unless-stopped
     mem_limit: ${WEB_MEM_LIMIT:-1g}
     cpus: ${WEB_CPUS:-2}
+    # A readiness probe Coolify gates a rolling deploy on: with "Rolling
+    # update" enabled on the resource, the new container must answer
+    # /api/ready before the old one is retired, so a redeploy swaps in with no
+    # gap. Without it Coolify recreates the stack — old removed, then new
+    # started — and the board is down while the new web boots.
+    healthcheck:
+      test: ["CMD", "node", "-e", "fetch('http://127.0.0.1:3000/api/ready').then(r=>process.exit(r.ok?0:1)).catch(()=>process.exit(1))"]
+      interval: 30s
+      timeout: 5s
+      start_period: 20s
+      retries: 3
     environment:
       # Ask Coolify for a domain on port 3000, then hand the board the same
       # thing with a scheme in front.