@webjsdev/cli 0.10.2 → 0.10.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webjsdev/cli",
-  "version": "0.10.2",
+  "version": "0.10.3",
   "type": "module",
   "description": "webjs CLI - dev, start, create, db",
   "bin": {

package/templates/AGENTS.md

@@ -318,12 +318,17 @@ Fully warm means the deterministic analysis AND the first vendor attempt have
 both completed, so the importmap and its build id are settled. Point your
 platform's readiness check at `/__webjs/ready` so it holds traffic off a
 not-yet-warmed instance instead of routing the first user request into the cold
-analysis or the brief window where the importmap is still resolving. On
-Railway, set `"healthcheckPath": "/__webjs/ready"` under `deploy` in
-`railway.json`. For dependency-aware
-readiness (gate on a live DB ping), add an optional `readiness.{js,ts}` at the
-app root that default-exports an async check; `/__webjs/ready` runs it once warm
-and reports 503 if it returns `false` or throws.
+analysis or the brief window where the importmap is still resolving. The
+scaffolded `Dockerfile` and `compose.yaml` already wire this up with a
+`HEALTHCHECK` that probes `/__webjs/ready`, so any Docker-based deploy gets the
+gate with no extra config. On a platform that reads its own config instead,
+point its equivalent knob at the same path: Railway `"healthcheckPath":
+"/__webjs/ready"`, Render `healthCheckPath: /__webjs/ready`, Fly a
+`[[http_service.checks]]` on `/__webjs/ready`, or a Kubernetes `readinessProbe`
+with `httpGet.path: /__webjs/ready`. For dependency-aware readiness (gate on a
+live DB ping), add an optional `readiness.{js,ts}` at the app root that
+default-exports an async check; `/__webjs/ready` runs it once warm and reports
+503 if it returns `false` or throws.
 
 Scripts:
 

package/templates/Dockerfile

@@ -33,6 +33,17 @@ ENV NODE_ENV=production
 ENV PORT=8080
 EXPOSE 8080
 
+# Platform-neutral readiness gate. webjs answers /__webjs/ready with 503 until
+# the instance is fully warm (analysis + first vendor attempt), then 200. This
+# HEALTHCHECK is honoured by Docker, compose, and most Docker-based platforms,
+# so the gate works the same everywhere instead of needing a per-platform file.
+# The probe is dependency-free (Node 24's built-in fetch, no curl/wget). For
+# platforms that read their own config, point the equivalent knob at the same
+# path (Railway healthcheckPath, Render healthCheckPath, Fly [checks], k8s
+# readinessProbe); see AGENTS.md "Health and readiness probes".
+HEALTHCHECK --interval=15s --timeout=3s --start-period=40s --retries=5 \
+  CMD ["node", "-e", "fetch('http://127.0.0.1:'+(process.env.PORT||8080)+'/__webjs/ready').then(r=>process.exit(r.ok?0:1),()=>process.exit(1))"]
+
 # `npm start` runs `prestart: prisma migrate deploy` (idempotent, a no-op when
 # there are no migrations yet) and then `webjs start`, which serves on $PORT.
 CMD ["npm", "start"]

package/templates/compose.yaml

@@ -23,6 +23,14 @@ services:
       # REDIS_URL: redis://redis:6379
     volumes:
       - app-data:/data
+    # Readiness gate: hold the service "starting" until /__webjs/ready returns
+    # 200 (fully warm). Same probe as the Dockerfile HEALTHCHECK; dependency-free.
+    healthcheck:
+      test: ["CMD", "node", "-e", "fetch('http://127.0.0.1:'+(process.env.PORT||8080)+'/__webjs/ready').then(r=>process.exit(r.ok?0:1),()=>process.exit(1))"]
+      interval: 15s
+      timeout: 3s
+      start_period: 40s
+      retries: 5
 
 volumes:
   app-data: