promote dev -> main: registry host migration to dev.jinemi.com #162

Merged

emi merged 2 commits from dev into main 2026-08-01 23:25:07 +00:00

Conversation 0 Commits 2 Files changed 39 +343 -157

emi commented 2026-08-01 23:20:19 +00:00

Owner

Copy link

Promotion of dev to main (beta). Two commits:

• 53e2eb7 registry: move the registry host to dev.jinemi.com, MCP to mcp.jinemi.com (#161)
• 4dcd677 make: add root install/up/down for the local stack

Pre-promotion verification

The registry change alters the REGISTRY_HOST default that deploy.sh and
deploy-stack.sh pull from, and deploy.yml never passes REGISTRY_HOST —
hosts fall back to that default. Checked the host-side prerequisites directly
rather than assuming:

• Proven on dev. vps1 is running
  dev.jinemi.com/jinemi/thermograph/{backend,frontend}:sha-53e2eb7c842f —
  the exact merge commit — with backend, frontend and lake all healthy. The
  new host worked end-to-end through a real build and deploy.
• /etc/hosts pins present on both boxes — vps1 and vps2 each pin
  dev.jinemi.com and git.thermograph.org to 10.10.0.2.
• vps2 reaches the new host over the mesh: dev.jinemi.com/v2/ returns
  401 (auth required) via 10.10.0.2, not 403 (off-mesh reject).
• The missing docker login self-heals. vps2's stored credential is still
  only for git.thermograph.org, but REGISTRY_TOKEN is present in both
  /etc/thermograph.env and /etc/thermograph-beta.env, and deploy.sh
  sources the env file (L133) before the login (L285), so it re-logs in
  against the new host on the way through.
• No unpinned node can pull: every service in both stacks is constrained
  to node.role == manager, i.e. vps2.

Both names address the same Forgejo and the same packages, so images already
pushed under the old prefix stay pullable and a rollback still resolves.

Promotion of `dev` to `main` (beta). Two commits: - `53e2eb7` registry: move the registry host to dev.jinemi.com, MCP to mcp.jinemi.com (#161) - `4dcd677` make: add root install/up/down for the local stack ## Pre-promotion verification The registry change alters the `REGISTRY_HOST` default that `deploy.sh` and `deploy-stack.sh` pull from, and `deploy.yml` never passes `REGISTRY_HOST` — hosts fall back to that default. Checked the host-side prerequisites directly rather than assuming: - **Proven on dev.** vps1 is running `dev.jinemi.com/jinemi/thermograph/{backend,frontend}:sha-53e2eb7c842f` — the exact merge commit — with backend, frontend and lake all healthy. The new host worked end-to-end through a real build and deploy. - **`/etc/hosts` pins present on both boxes** — vps1 and vps2 each pin `dev.jinemi.com` and `git.thermograph.org` to `10.10.0.2`. - **vps2 reaches the new host over the mesh**: `dev.jinemi.com/v2/` returns **401** (auth required) via `10.10.0.2`, not 403 (off-mesh reject). - **The missing `docker login` self-heals.** vps2's stored credential is still only for `git.thermograph.org`, but `REGISTRY_TOKEN` is present in *both* `/etc/thermograph.env` and `/etc/thermograph-beta.env`, and `deploy.sh` sources the env file (L133) before the login (L285), so it re-logs in against the new host on the way through. - **No unpinned node can pull**: every service in both stacks is constrained to `node.role == manager`, i.e. vps2. Both names address the same Forgejo and the same packages, so images already pushed under the old prefix stay pullable and a rollback still resolves.

emi added 2 commits 2026-08-01 23:20:23 +00:00

make: add root install/up/down for the local stack ... 4dcd6775c4

A fresh checkout had no working path to the stack locally. Neither compose
file carries a `build:` for backend or frontend -- each ships as its own
registry image -- so with no image present `make dev-up` fell through to
pulling the `:local` tag, which nothing publishes, and failed with 403
against a registry a laptop has no login for.

`install` builds both images from backend/Dockerfile and frontend/Dockerfile
under exactly the tag the compose files default to; `up` verifies they exist
and says what to run instead of retrying the pull. Image names are read back
from `docker compose config --images` rather than restated here, so an org
rename cannot leave this file building a tag nothing runs.

infra's dev-up/dev-down now set COMPOSE_PROJECT_NAME=thermograph-dev, which
matches deploy/deploy-dev.sh and what the root CLAUDE.md already described;
a local run previously landed in the prod-shaped `thermograph` project. Drop
dev-up's `--build`, a no-op since the Dockerfiles moved out of infra, and
correct the comment claiming a 0.0.0.0 default -- the overlay has published
on loopback since dev moved to a public VPS.

registry: move the registry host to dev.jinemi.com, MCP to mcp.jinemi.com ... 53e2eb7c84

Completes the Forgejo domain migration. ROOT_URL moved to dev.jinemi.com
earlier; the registry half was deliberately deferred. Every image name,
REGISTRY_HOST default, runner label and --add-host pin now names
dev.jinemi.com, so the registry host and the bearer-token realm agree again.

Both names address the same Forgejo, so no image needs re-pushing and a
rollback to a tag pushed under the old prefix still resolves.
git.thermograph.org therefore stays served off the same Caddy site block --
one block, so the /v2/* mesh-only matcher keeps covering both names -- for
pre-migration tags and for runners holding it as their registered instance
URL.

Mesh clients now pin both names in /etc/hosts: the new one as registry host
and token realm, the old one for pre-migration tags. runner-vps2/config.yaml
carries both --add-host entries for the same reason.

Also renames Centralis' endpoint to mcp.jinemi.com in the two places this
repo names it; Centralis itself is provisioned outside this repo.

Host-side steps this cannot do (documented in deploy/forgejo/README.md,
"Host-side steps"): the Forgejo Actions variable REGISTRY_HOST, docker login
against the new host, and the /etc/hosts pins.

emi merged commit 0eb4f63895 into main 2026-08-01 23:25:07 +00:00

emi referenced this pull request from a commit 2026-08-01 23:25:09 +00:00

Merge pull request 'promote dev -> main: registry host migration to dev.jinemi.com' (#162) from dev into main

emi referenced this pull request 2026-08-01 23:27:57 +00:00

promote main -> release: registry host migration to dev.jinemi.com #163

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

  

Compat/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Abandoned

Somebody has started to work on this but abandoned work

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

No labels

Compat/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Security

Kind/Testing

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Abandoned

Status

Blocked

Status

Need More Info

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Jinemi/thermograph#162

No description provided.