From ae4af254cc5a37da98e65046ef6da70fb51c450b Mon Sep 17 00:00:00 2001
From: Amr Mohammed El-Sheraey <141947355+AmrMsCLL@users.noreply.github.com>
Date: Sun, 11 Oct 2026 07:58:17 +0300
Subject: [PATCH] chore: production values live in platform; drop the
 production compose

---
 .graphite.yml           |  4 +---
 README.md               | 16 +++++++++-------
 compose.production.yaml | 22 ----------------------
 3 files changed, 10 insertions(+), 32 deletions(-)
 delete mode 100644 compose.production.yaml

diff --git a/.graphite.yml b/.graphite.yml
index 6ca140e..77fb7ee 100644
--- a/.graphite.yml
+++ b/.graphite.yml
@@ -28,9 +28,7 @@ projects:
 
       # kind: compose
       # host: my-project.project-graphite.com # <label>.project-graphite.com
-      # source: { file: compose.production.yaml, service: web, port: 80 }
-      # secrets: [SECRET_KEY] # UPPER_SNAKE_CASE[]
 
       # kind: pages
       # host: my-project.project-graphite.com # <label>.project-graphite.com
-      # source: { directory: web, output: dist }
+      # source: { directory: web, output: dist, command: npm run build }
diff --git a/README.md b/README.md
index b2e92ac..1d3e621 100644
--- a/README.md
+++ b/README.md
@@ -34,22 +34,24 @@ Delete this section once the checklist is done.
    `lint`, `test`, and `build` scripts. A folder with a `Makefile` must provide `install`, `lint`, and
    `test` targets.
 4. Update `compose.yaml` for local development, with its bind mounts, hot reload, and development
-   ports. Update `compose.production.yaml` to pull the prebuilt GHCR images,
-   define health checks and persistent volumes, avoid published host ports, and cap CPU and memory.
-5. Add a screenshot or short GIF, the eventual live link, the stack, and clear local instructions
+   ports.
+5. For a `compose` deploy, open a pull request in `platform` adding `deploy/<slug>/values.yaml`:
+   the production services, health checks, volumes, resource limits and the names of its secrets.
+   Ask an organisation owner to add the secret values. Merging the values deploys it.
+6. Add a screenshot or short GIF, the eventual live link, the stack, and clear local instructions
    to this README.
 
 Use named service folders even for a single-service project. Images are published as
-`ghcr.io/project-graphite/<repo>/<service>`, and each image name must match its service in the
-production Compose file.
+`ghcr.io/project-graphite/<repo>/<service>`, and each one is a service of the same name in the
+project's platform values.
 
 `.github/workflows/pipeline.yml` runs the shared `reusable-pipeline.yml`. Turn a stage off with its
 switch, e.g. `with: { changelog: false }`, or replace the file with calls to the individual shared
 workflows.
 
 Until the platform entry is merged, the `Deploy` job on `main` fails with a clear message. Builds
-and checks continue. Once the repository has the `COOLIFY_WEBHOOK` and `COOLIFY_TOKEN` secrets, the
-same job deploys to Coolify.
+and checks continue. After that, each `main` push records its image tag in `platform`, which
+deploys it.
 
 ## Conventions
 
diff --git a/compose.production.yaml b/compose.production.yaml
deleted file mode 100644
index d3bd7ea..0000000
--- a/compose.production.yaml
+++ /dev/null
@@ -1,22 +0,0 @@
-name: project-template
-
-services:
-  web:
-    image: ghcr.io/project-graphite/project-template/web:${IMAGE_TAG:-latest}
-    expose:
-      - "80"
-    healthcheck:
-      test: [CMD, wget, --quiet, --tries=1, --spider, http://localhost/]
-      interval: 30s
-      timeout: 5s
-      start_period: 10s
-      retries: 3
-    init: true
-    restart: unless-stopped
-    security_opt:
-      - no-new-privileges:true
-    deploy:
-      resources:
-        limits:
-          cpus: "0.25"
-          memory: 128M