From 64db209baba293a79d8ef4f86bb234ea16d57d79 Mon Sep 17 00:00:00 2001 From: saravanakumardb1 Date: Mon, 23 Mar 2026 19:26:31 -0700 Subject: [PATCH] fix(docs): refresh local Gitea rehearsal status --- docs/devops/SINGLE_VM_DEPLOYMENT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/devops/SINGLE_VM_DEPLOYMENT.md b/docs/devops/SINGLE_VM_DEPLOYMENT.md index 496435be..ae7b53ca 100644 --- a/docs/devops/SINGLE_VM_DEPLOYMENT.md +++ b/docs/devops/SINGLE_VM_DEPLOYMENT.md @@ -1196,7 +1196,7 @@ This is fragile, slow, and must be repeated for every image rebuild. Gitea has a built-in npm registry at `http://gitea:3300/api/packages//npm/`. Publishing `@bytelyst/*` packages there means **all product repos install from the registry like any normal npm dependency** — no tarballs, no rewriting, no `docker-prep.sh`. -> **Current local rehearsal status on this Mac:** host-side package publishing and host-side consumer installs are validated. Full Docker-side validation against the local Homebrew Gitea instance is still blocked by host/Docker registry URL reachability and tarball URL generation behavior. Treat the Docker portion of this section as the target architecture, not yet a fully cleared local result. +> **Current local rehearsal status on this Mac:** host-side package publishing and host-side consumer installs are validated. FlowMonk backend/web Docker builds are also locally green with the documented `host.docker.internal` + `--add-host localhost:host-gateway` workaround, but the Homebrew Gitea tarball URL shape is still not clean enough to treat that as the final VM-ready/default result. #### Setup (one-time)