Deprecate repos.saiden.dev hostname — replaced by git.saiden.dev #10

Open
opened 2026-06-12 10:06:34 +00:00 by madcat · 1 comment
Owner

The hostname repos.saiden.dev is deprecated. The Gitea instance is now accessed via git.saiden.dev. All references (SSH remotes, web links, documentation, agent configs) should be updated accordingly.

The hostname repos.saiden.dev is deprecated. The Gitea instance is now accessed via git.saiden.dev. All references (SSH remotes, web links, documentation, agent configs) should be updated accordingly.
Author
Owner

Investigation: repos.saiden.dev references across all hosts

Searched: All 3 hosts (junkpile, fuji, sin) — /home/madcat, system configs, git remotes, tea config, package manager configs, cloudflared, Coolify/Docker, systemd.

Already migrated (clean)

  • tea CLI (junkpile) — both logins use git.saiden.dev
  • .npmrc (junkpile, sin) — registry points to git.saiden.dev
  • .gitconfig — no refs
  • .ssh/config — no refs
  • Git remotes — all repos on all hosts use git.saiden.dev
  • Gitea app.iniDOMAIN, SSH_DOMAIN, ROOT_URL all set to git.saiden.dev
  • systemd units — no refs
  • fuji — fully clean, no actionable refs

Needs fixing — Config files (active)

# Host File Details
1 junkpile ~/.gemrc RubyGems source: https://repos.saiden.dev/api/packages/madcat-os/rubygems
2 junkpile ~/.config/uv/uv.toml Python uv extra-index-url: https://repos.saiden.dev/api/packages/madcat-os/pypi/simple/
3 junkpile ~/.pypirc PyPI upload repository: https://repos.saiden.dev/api/packages/madcat-os/pypi
4 sin ~/.config/tea/config.yml Tea login URL: https://repos.saiden.dev (junkpile is fine, sin is stale)

Needs fixing — Source code

# Host File Line(s) Details
5 all opencode-plugin/src/tools/whoami.ts 194, 196 Hardcoded guidance strings: tea CLI description and npm_registry URL both reference repos.saiden.dev

Needs fixing — Infrastructure

# Host File/Service Details
6 junkpile ~/.cloudflared/config.yml Ingress rule routes repos.saiden.dev → localhost:80. File header says "remotely managed via CF API" — may be informational only, but should be verified against the live CF tunnel config.
7 junkpile Coolify Gitea container env SERVICE_FQDN_GITEA=repos.saiden.dev, COOLIFY_FQDN=repos.saiden.dev, COOLIFY_URL=http://repos.saiden.dev, plus traefik routing rule Host(repos.saiden.dev). This is the Coolify project FQDN — needs updating in Coolify dashboard.

Not actionable (logs/cache/history)

  • .npm/_logs/ — old npm debug logs referencing the registry (will age out)
  • .bun/install/cache/ — cached build of opencode-plugin (will refresh on next install)
  • .bash_history on sin — historical commands

Summary

7 actionable items across 3 categories: 4 dotfile configs, 1 source code file (opencode-plugin), 2 infra items (cloudflared + Coolify). The Coolify FQDN (#7) is the most impactful — it controls how the reverse proxy routes to Gitea.

## Investigation: `repos.saiden.dev` references across all hosts **Searched:** All 3 hosts (junkpile, fuji, sin) — `/home/madcat`, system configs, git remotes, tea config, package manager configs, cloudflared, Coolify/Docker, systemd. ### Already migrated (clean) - **tea CLI (junkpile)** — both logins use `git.saiden.dev` ✅ - **`.npmrc` (junkpile, sin)** — registry points to `git.saiden.dev` ✅ - **`.gitconfig`** — no refs ✅ - **`.ssh/config`** — no refs ✅ - **Git remotes** — all repos on all hosts use `git.saiden.dev` ✅ - **Gitea `app.ini`** — `DOMAIN`, `SSH_DOMAIN`, `ROOT_URL` all set to `git.saiden.dev` ✅ - **systemd units** — no refs ✅ - **fuji** — fully clean, no actionable refs ✅ ### Needs fixing — Config files (active) | # | Host | File | Details | |---|------|------|---------| | 1 | junkpile | `~/.gemrc` | RubyGems source: `https://repos.saiden.dev/api/packages/madcat-os/rubygems` | | 2 | junkpile | `~/.config/uv/uv.toml` | Python uv extra-index-url: `https://repos.saiden.dev/api/packages/madcat-os/pypi/simple/` | | 3 | junkpile | `~/.pypirc` | PyPI upload repository: `https://repos.saiden.dev/api/packages/madcat-os/pypi` | | 4 | sin | `~/.config/tea/config.yml` | Tea login URL: `https://repos.saiden.dev` (junkpile is fine, sin is stale) | ### Needs fixing — Source code | # | Host | File | Line(s) | Details | |---|------|------|---------|---------| | 5 | all | `opencode-plugin/src/tools/whoami.ts` | 194, 196 | Hardcoded guidance strings: tea CLI description and npm_registry URL both reference `repos.saiden.dev` | ### Needs fixing — Infrastructure | # | Host | File/Service | Details | |---|------|-------------|---------| | 6 | junkpile | `~/.cloudflared/config.yml` | Ingress rule routes `repos.saiden.dev` → localhost:80. File header says *"remotely managed via CF API"* — may be informational only, but should be verified against the live CF tunnel config. | | 7 | junkpile | Coolify Gitea container env | `SERVICE_FQDN_GITEA=repos.saiden.dev`, `COOLIFY_FQDN=repos.saiden.dev`, `COOLIFY_URL=http://repos.saiden.dev`, plus traefik routing rule `Host(repos.saiden.dev)`. This is the Coolify project FQDN — needs updating in Coolify dashboard. | ### Not actionable (logs/cache/history) - `.npm/_logs/` — old npm debug logs referencing the registry (will age out) - `.bun/install/cache/` — cached build of opencode-plugin (will refresh on next install) - `.bash_history` on sin — historical commands ### Summary **7 actionable items** across 3 categories: 4 dotfile configs, 1 source code file (opencode-plugin), 2 infra items (cloudflared + Coolify). The Coolify FQDN (#7) is the most impactful — it controls how the reverse proxy routes to Gitea.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: infra/issues#10