Stand up the Forgejo server stack and its switch-day checklist #490

New issue

admin-amaurycoudr · 2026-10-21T10:06:28Z

root commented

2026-10-21 10:06:28 +00:00

(Migrated from gitlab.core-project.space)

Parent

What to build

Everything the owner needs to stand Forgejo up on the CI VPS on switch day, merged ahead of time and inert on GitLab: Forgejo on its LTS line and one Forgejo runner, each pinned by tag and digest, served at git.core-project.space behind Traefik with HTTPS, with the registry beside it. The runner takes one job at a time through the host's Docker daemon, mounts the shared Turbo cache volume, and keeps today's job memory cap and /dev/shm. Forgejo's SSH server is off. A nightly forgejo dump replaces the GitLab backup, with the same destination and retention. A provisioning wizard modelled on the GitLab one brings it up, and a switch-day checklist lists every step of the switch, each ending in a command that checks it.

Seam: the switch-day checklist (spec ## Seams).

Acceptance criteria

Forgejo and its runner come up beside GitLab on one host, from the repo, with no GitLab file changed.
Forgejo answers over HTTPS at its host; its SSH server is off.
The runner registers with capacity 1, the Turbo cache volume and the job memory cap.
The nightly dump writes to the backup destination with the current retention.
The checklist covers install, bot account, import, converter run, origin, GitHub push mirror, branch protection, the gitlab. redirect, first main deploy, GitLab backup and stop, and GitLab deletion a week later, each with its check command.
ADR 0048 is followed.

## Parent #489 ## What to build Everything the owner needs to stand Forgejo up on the CI VPS on switch day, merged ahead of time and inert on GitLab: Forgejo on its LTS line and one Forgejo runner, each pinned by tag and digest, served at `git.core-project.space` behind Traefik with HTTPS, with the registry beside it. The runner takes one job at a time through the host's Docker daemon, mounts the shared Turbo cache volume, and keeps today's job memory cap and `/dev/shm`. Forgejo's SSH server is off. A nightly `forgejo dump` replaces the GitLab backup, with the same destination and retention. A provisioning wizard modelled on the GitLab one brings it up, and a switch-day checklist lists every step of the switch, each ending in a command that checks it. Seam: the switch-day checklist (spec `## Seams`). ## Acceptance criteria - [ ] Forgejo and its runner come up beside GitLab on one host, from the repo, with no GitLab file changed. - [ ] Forgejo answers over HTTPS at its host; its SSH server is off. - [ ] The runner registers with capacity 1, the Turbo cache volume and the job memory cap. - [ ] The nightly dump writes to the backup destination with the current retention. - [ ] The checklist covers install, bot account, import, converter run, `origin`, GitHub push mirror, branch protection, the `gitlab.` redirect, first `main` deploy, GitLab backup and stop, and GitLab deletion a week later, each with its check command. - [ ] ADR 0048 is followed.

root commented

2026-10-21 10:07:19 +00:00

(Migrated from gitlab.core-project.space)

mentioned in issue #498