Repository navigation
feat(forge): Forgejo LTS in place of Gitea, "forge" where the name is generic - #116
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA
…the Gitea names still read Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA
stefanoghinelli
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The forge is Forgejo 15 LTS (urbforge/urbex ADR-0034, in urbforge/urbex#89):
platform/ansible/roles/gitea/templates/docker-compose.yml.j2:codeberg.org/forgejo/forgejo:15.0.11, pinned by its index digest (built 2026-10-26), in place ofgitea/gitea:1.24(out of support, not pinned); the settings asFORGEJO__*. The image keeps thegiteacommand (forgejolinks to it), uid 1000 and/data, so the role's tasks are unchanged."forge" where the name is generic, with the old names still read (a workspace written by 0.1.0 works unchanged):
internal/gitea→internal/forge.forgeAdminPassword,forgeToken(URBEX_FORGE_ADMIN_PASSWORD,URBEX_FORGE_TOKEN).giteaAdminPassword,giteaTokenandURBEX_GITEA_*are still read, from the file and the environment; the new names win; the next write ofcredentials.yamlmoves the values to the new keys.Get,SetandEnvanswer to both names.git.forgeUrl;git.giteaUrlstill read (forgeUrlwins).urbex discoverand the starter config writeforgeUrl.status's endpoints and logins (forgeAdminPassword),discover,apply --repo-dir's help.urbex-gitea, the volumegitea-data, the catalog's servicegitea(Grafana's labels), the webhook typegitea, the role's name, and Komodo's variablesURBEX_GITEA_URL/USER/TOKEN, which the installed Actions read (commented where they are set).forgeToken),git.forgeUrl, the progress and status checks.docs/layout.md.Why
#112: the platform ran Gitea 1.24, out of support, and the first testers (the Reddit call) should get a forge with years of support. Teg and Stefano agreed to switch if the spike passed; it did.
Tests I ran
demo: apply staging (webhook → Komodo build → registry → deploy, 342 s), release, apply prod, promote, status. The forge LXC: Gitea 1.24 124 MiB in its container / 316 MiB the LXC, Forgejo 150-160 / 293-313 MiB; disk 2.17 → 1.8 GB.go test ./...andmise run lintpass; the e2e PASSED (24 steps), after updating its two checks that read the old wording. New tests: legacy credential keys and env (read, the new wins, moved on write), legacygit.giteaUrl.giteaTokenincredentials.yaml,git.giteaUrlinurbex.platform.yaml), with this branch's operator image:urbex doctor: every workspace check ok, the platform config valid;urbex status: the endpoints withForgejo (web, git, registry), and the projects with no warning about updating the GitOps repo from the forge, so the legacy token is read;urbex status staging: running;credentials.yamlunchanged by these read-only commands.apply,release) against that workspace, which would move the file to the new keys. The unit test covers that move.Checklist before review
Depends on urbforge/urbex#89 (the ADR).
Fixes #112
🤖 Generated with Claude Code
https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA