bonna61/Bonna-Moon-Studio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CLAUDE.md: git.poweredbyotm.com and the NAS Gitea are separate instances; NAS is legacy, being retired

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bonna
2026-08-06 22:37:26 -05:00
parent c4ba1591c7
commit 4c2cf79250
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
CLAUDE.md
View File

@@ -40,15 +40,19 @@ user.name = Bonna
user.email = bonna@fullmoonbakehouse.com
```
### The other Gitea address
### The other Gitea address — ⚠️ TWO instances now, NAS is legacy
Same Gitea instance, three addresses depending on where you are:
**Corrected 2026-08-06 (the hard way):** `git.poweredbyotm.com` and the home NAS
are **separate Gitea instances**. They diverged at some point; an earlier version
of this file claimed they were one instance with three addresses. They are not.
| Address | When it works |
| Address | What it is |
|---|---|
| `https://git.poweredbyotm.com` | Anywhere. Keychain auth. Use this. |
| `http://192.168.0.5:3022` | Home LAN only (NAS). |
| `http://167.237.9.184:3022` | Home public IP — what `anvil` uses, and the fallback when the Mac is off the LAN. |
| `https://git.poweredbyotm.com` | **Production Gitea. Use this, always.** Keychain auth. Holds this repo, `tonym/platform` (the real one — admin 0.111.0-era), `bonna61/Moonbase`, etc. |
| `http://192.168.0.5:3022` / `http://167.237.9.184:3022` | **Legacy home-NAS Gitea (LAN / public IP of the same box). Being retired** — Tony confirmed 2026-08-06. Its `tonym/platform` is frozen at ~0.80.0; pushing there deploys nothing. A stray bms commit (`e2ea2b3`) landed there before the divergence was discovered. |
Do not push platform work to the NAS. If a doc, remote URL, or memory points at
`192.168.0.5:3022` / `167.237.9.184:3022`, treat it as stale until verified.
The sibling repos (`moonbase`, `moon-household-budget`, `otm-platform`) embed an
access token directly in their remote URL against `192.168.0.5:3022`. Those tokens