iamcoolvivek007/morpheus-brain
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
morpheus-brain/research/tech-study/2026-06-11-forgejo-url-change-and-repo-access.md
Vivek a661cf04ae docs: add Forgejo URL migration study
2026-06-10 21:26:45 +00:00

2.5 KiB
Raw Blame History

Forgejo URL Change and Repo Access (2026-06-11)

What it is

The self-hosted Forgeio instance used for personal and project repositories has migrated from http://forgejo-vil3xyowqk0qsh4hiqy77e3h.187.127.178.110.sslip.io to https://git.errorlog.space/. All repository URLs, API endpoints, and SSH remotes have been updated accordingly.

How it works

  • API Access: The Forgejo REST API is available at https://git.errorlog.space/api/v1/. Authentication is via a personal access token (PAT) stored in Hermes memory (a33b1586cb5b33b42823758d237202ceeaff12e1).
  • Repository Listing: GET /api/v1/user/repos returns JSON metadata for all owned repos (see sample output below).
  • Clone URLs: HTTPS clone URLs now follow the pattern https://git.errorlog.space/<username>/<repo>.git. Some SSH URLs still reflect the old host in metadata but the actual Git service is reachable via the new domain.
  • Mirrors: Several repositories (bharath, data) are marked as mirrors with original_url pointing to the previous Forgejo instance; they sync every 8 hours.

Key Patterns

  • Use HTTPS for simplicity unless SSH keys are explicitly configured.
  • The API token provides full access (admin, push, pull) to all repositories.
  • Repository metadata includes mirror_interval and mirror_updated fields useful for tracking sync status.
  • The instance hosts a mix of public and private repositories (e.g., morpheus-brain is private).

Why it matters

  • Ensures continued access to personal knowledge base (morpheus-brain) and project repos (freightdesk, internal-freight-app, data, etc.).
  • Enables automation scripts, CI/CD, and agent collaboration to point to the correct endpoint.
  • Awareness of mirror status helps avoid confusion when viewing stale data.

Action Items

  • Update any local git remotes that still point to the old sslip.io host.
  • Verify CI/CD pipelines (if any) use the new API endpoint and token.
  • Consider adding a webhook to notify Hermes of new pushes to key repos.
  • Document the new URL in Hermes memory for future reference (already done).

Sources

  • Forgejo API response from https://git.errorlog.space/api/v1/user/repos (retrieved 2026-06-11).
  • Repository metadata fields: html_url, clone_url, ssh_url, original_url, mirror, mirror_interval.

Relevance to our stack

5/5 – Directly impacts all Forgejo-hosted projects, including the freight‑desk SaaS, data layer, and personal knowledge base used by Hermes and other agents.