change image

docs/image-build.md

@@ -59,27 +59,20 @@ and update those pins when upgrading actions.
 
 ## Use the published image with Komodo
 
-The workflow only builds/publishes; it does **not** redeploy Komodo. The existing
-`compose.yaml` still builds locally and remains usable without a registry.
+The workflow only builds/publishes; it does **not** redeploy Komodo.
+[`compose.yaml`](../compose.yaml) directly uses
+`gitea.cptckp.com/nurinda/recruitment-hc:latest` for both `app` and `migrate`.
+It has no local `build` declarations and requires no override file.
 
-To deploy the CI image instead, add a small override file in your server-side
-Stack run directory, for example `compose.image.yaml`:
+For reproducible deployments, replace the shared `app-image` YAML anchor's
+`:latest` with the tested image digest (`@sha256:...`). Both services then use
+that same pinned image.
 
-```yaml
-services:
-  app:
-    image: gitea.cptckp.com/nurinda/recruitment-hc:latest
-  migrate:
-    image: gitea.cptckp.com/nurinda/recruitment-hc:latest
-```
+Use only `compose.yaml` in the Komodo Stack's Compose file paths. Then:
 
-Prefer replacing `:latest` with the tested image digest (`@sha256:...` instead
-of `:latest`).
-Include both `compose.yaml` and `compose.image.yaml` in the Komodo Stack's Compose
-file paths, in that order. Then:
-
-- Disable **Run build** so Komodo does not build/tag a local image over the CI image.
+- Disable **Run build**; Gitea Actions is responsible for building the image.
 - Enable **Auto pull** so the image is pulled before deployment.
+- Keep **Extra args** as `["--no-build"]` to explicitly enforce image-only deployment.
 - Configure Komodo's Registry provider/account for `gitea.cptckp.com`; for private
   packages, use a token with **Packages: Read** on an account allowed to pull them.
   Keep this separate from the CI write token.
@@ -88,10 +81,12 @@ file paths, in that order. Then:
   a trusted dump on the Docker host. Initialization/migrations run automatically;
   follow [the deployment guide](deployment.md).
 
-Compose retains both services' base `build` declarations in this simple override. Use
-`docker compose ... up -d --no-build` for manual deployments of the CI image
-(after registry login and `docker compose ... pull`); do **not** use `--build`.
-Komodo's Auto pull supplies the image before `up`, with Run build disabled.
+For manual deployments, run `docker compose ... pull` followed by
+`docker compose ... up -d --no-build` after registry login; do **not** use `--build`.
+Komodo's Auto pull supplies the image before `up`, with Run build disabled and
+`--no-build` set. The `recruitment-hc` entry in `komodo-sync/resources/stacks/web.toml`
+uses this single-file configuration. Push the application changes and wait for
+Gitea Actions to publish successfully before applying that Stack configuration.
 
 For example, after configuring registry authentication on the server: