Opened at 2025-01-16T11:06:39Z
Last modified at 2025-01-16T14:56:19Z
#4161 new task
Move off Trac - Execution - Forgejo
| Reported by: | btlogy | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | dev-infrastructure | Version: | n/a |
| Keywords: | movofftrac | Cc: | |
| Launchpad Bug: |
Description
Following #4095 (Move off Trac - Initiation), we can now start executing the plan.
In short, the goal is to follow the principle of Infrastructure as Code as much as possible in those main steps:
- deploy and manage a new VPS server hosted by Hetzner using OpenToFu
- deploy and configure Forgio using NixOS
- manage the DNS records to re-route web traffic to the new server using OpenToFu
- proxy/redirect out-of-scope content to the legacy server using NixOS
- migrate the data from Trac to Forgejo using trac2gitea
More details should be found in this dedicated MoveOffTrac repository.
Note: See
TracTickets for help on using
tickets.
Declarative definition of the DNS configurations via #4162 would be a very nice to have for the step 3 in the description.
We would be able to stream the IPs assigned to the VPS during their provisioning directly to the DNS records.
This would avoid a back-and-forth and/or synchronized interaction between the contributor(s) who's going to execute the migration and the one(s) have the permissions to change the DNS configurations.
This being said, the declarative definition of the VPS can be done regardless of what will happened to #4162. So we/I should try to keep those as separated as possible.