From b62d814ececebd97b8a93bc56dbbba1173cc960d Mon Sep 17 00:00:00 2001 From: Hermes Coding Manager Date: Mon, 10 Aug 2026 05:52:00 -0400 Subject: [PATCH] docs(deploy): update deploy host to 10.0.0.52 --- DEPLOY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DEPLOY.md b/DEPLOY.md index d91bc29..69452be 100644 --- a/DEPLOY.md +++ b/DEPLOY.md @@ -1,6 +1,6 @@ # Project E — Deploy Guide -Production runs as a docker-compose stack on the deploy host (`10.0.0.204`). The stack has four services: PostgreSQL, the Hono API, the Vite SPA served by Caddy, and the Bun worker. Deploys are normally driven by Gitea Actions, but every step below can be run by hand. +Production runs as a docker-compose stack on the deploy host (`10.0.0.52`). The stack has four services: PostgreSQL, the Hono API, the Vite SPA served by Caddy, and the Bun worker. Deploys are normally driven by Gitea Actions, but every step below can be run by hand. ## Architecture @@ -50,7 +50,7 @@ Idempotent, safe to re-run. It: The workflow runs on the self-hosted runner `projecte-runner`, which must be registered on the Gitea instance before any job can start (otherwise jobs stay -stuck at "Waiting to run"). Do this once on the deploy host (10.0.0.204), which +stuck at "Waiting to run"). Do this once on the deploy host (10.0.0.52), which is where the `deploy` and `smoke` jobs act on the local docker-compose stack: 1. **Install `act_runner`** — download the `act_runner` binary from the Gitea