chore(org): retarget org paths to RunicGateway #66

wtclaude · 2026-07-18T04:47:03Z

wtclaude commented

2026-07-18 04:47:03 +00:00

Follow-up to the UOM → RunicGateway Gitea org transfer (repo reorg Phase 1).

What changed

docker-compose.yml — app + bot images now pull from gitea.whitlocktech.com/runicgateway/* instead of /uom/*.
README.md — the three UOM/link references (intro bullet, shard-integration section, ASCII diagram) now point at RunicGateway/link.

Why the compose change matters

build-images.yml already derives its registry owner from ${{ github.repository_owner }} (lowercased), so post-transfer it publishes to …/runicgateway/website-app|bot. But compose still pulled from …/uom/…, so the next deploy would have pulled stale/missing images. This realigns the pull path with what CI actually pushes.

Not in scope

No branding text touched (UOMysticmoon display strings are handled separately).
Deploy-box compose at /home/perry/website/docker-compose.yml, if it's a standalone copy rather than a checkout, needs the same uom → runicgateway edit applied manually on the host.

Opening this exercises the pre-merge PR Checks; merging it fires build-images + uom_deploy against the new image paths.

🤖 Generated with Claude Code

Follow-up to the `UOM` → `RunicGateway` Gitea org transfer (repo reorg Phase 1). ## What changed - **`docker-compose.yml`** — app + bot images now pull from `gitea.whitlocktech.com/runicgateway/*` instead of `/uom/*`. - **`README.md`** — the three `UOM/link` references (intro bullet, shard-integration section, ASCII diagram) now point at `RunicGateway/link`. ## Why the compose change matters `build-images.yml` already derives its registry owner from `${{ github.repository_owner }}` (lowercased), so post-transfer it **publishes to `…/runicgateway/website-app|bot`**. But compose still pulled from `…/uom/…`, so the next deploy would have pulled stale/missing images. This realigns the pull path with what CI actually pushes. ## Not in scope - No branding text touched (`UOMysticmoon` display strings are handled separately). - **Deploy-box compose** at `/home/perry/website/docker-compose.yml`, if it's a standalone copy rather than a checkout, needs the same `uom` → `runicgateway` edit applied manually on the host. Opening this exercises the pre-merge `PR Checks`; merging it fires `build-images` + `uom_deploy` against the new image paths. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

wtclaude added 1 commit 2026-07-18 04:47:04 +00:00

chore(org): retarget org paths to RunicGateway

PR Checks / client-build (pull_request) Successful in 9m30s

Details

PR Checks / server-tests (pull_request) Successful in 10m34s

Details

PR Checks / bot-install (pull_request) Successful in 9m21s

Details

6c967d9a6c

Repo was transferred UOM -> RunicGateway. build-images.yml already
derives its registry owner from github.repository_owner, so it now
publishes to gitea.whitlocktech.com/runicgateway/*, but docker-compose
still pulled from /uom/*. Point the app+bot images at the new owner so
deploys pull the images CI actually publishes. Also update the two
README links to the uo-link repo (UOM/link -> RunicGateway/link).

No branding text touched (that is handled separately).

whitlocktech approved these changes 2026-07-18 04:47:29 +00:00

whitlocktech scheduled this pull request to auto merge when all checks succeed 2026-07-18 04:47:34 +00:00

wtclaude referenced this pull request

2026-07-18 05:06:08 +00:00

docs: move design docs to RunicGateway/docs #67

whitlocktech merged commit e0fadbdcc2 into main

2026-07-18 05:06:46 +00:00

whitlocktech deleted branch chore/org-rename-runicgateway

2026-07-18 05:06:47 +00:00

whitlocktech referenced this issue from a commit

2026-07-18 05:06:47 +00:00

Merge pull request 'chore(org): retarget org paths to RunicGateway' (#66) from chore/org-rename-runicgateway into main