docs(deploy): deploy/README.md + record the live instance #255

2026-09-20T22:43:43-04:00

claude commented

2026-09-20 22:43:43 -04:00

The deploy/ directory had no entry point, and the maintainer's live instance (https://provenance.paul.farm) was recorded nowhere in the repo.

New deploy/README.md — how to run the stack (compose + dev override), the LAN-push / FQDN-pull registry split, the env-driven Caddy site address, and the Watchtower-vs-one-shot-migrate caveat; plus a maintainer's instance section (URL, host 192.168.0.2, Cloudflare Tunnel ingress, owner account, deploy path).
CLAUDE.md — Owner & contact now names the live instance and links the new README; repo layout mentions it.
deploy/.env.example — APP_ENV now says to set production on a real deployment. The live instance's /health reports "env":"development"; informational only (app_env gates no behavior), noted as known drift in the README.

Docs only — no code paths touched.

The deploy/ directory had no entry point, and the maintainer's live instance (https://provenance.paul.farm) was recorded nowhere in the repo. - **New `deploy/README.md`** — how to run the stack (compose + dev override), the LAN-push / FQDN-pull registry split, the env-driven Caddy site address, and the Watchtower-vs-one-shot-`migrate` caveat; plus a *maintainer's instance* section (URL, host `192.168.0.2`, Cloudflare Tunnel ingress, owner account, deploy path). - **CLAUDE.md** — Owner & contact now names the live instance and links the new README; repo layout mentions it. - **deploy/.env.example** — `APP_ENV` now says to set `production` on a real deployment. The live instance's `/health` reports `"env":"development"`; informational only (`app_env` gates no behavior), noted as known drift in the README. Docs only — no code paths touched.

claude added 1 commit 2026-09-20 22:43:44 -04:00

docs(deploy): add deploy/README.md and record the live instance 05aa57c880

The deploy/ directory had no entry point: how to stand the stack up lived
only in comments inside docker-compose.yml, and the maintainer's own
instance (provenance.paul.farm) was written down nowhere in the repo —
it had to be rediscovered from an unrelated repo's research log.

Add deploy/README.md covering the run/build commands, the LAN-push /
FQDN-pull registry split, the env-driven site address, and the Watchtower
+ one-shot-migrate caveat, plus a "maintainer's instance" section with
the URL, host, ingress and deploy path. Cross-reference it from CLAUDE.md.

Also note the live instance reports "env":"development" — its .env never
set APP_ENV=production. Informational only (app_env gates no behavior),
but .env.example now says to set it on a real deployment.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01BeRh7Vwq8j9s6jshaMUNCd
Signed-off-by: Justin Paul <[email protected]>

claude merged commit f9344ac317 into main

2026-09-20 22:43:47 -04:00

claude deleted branch deploy-docs-live-instance

2026-09-20 22:43:47 -04:00

claude referenced this pull request

2026-09-20 22:45:18 -04:00

docs(deploy): live instance now runs APP_ENV=production #256

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: justin/provenance#255