The Self-Hosted Git Setup
Your own git server on your own machine — Forgejo, Gitea or GitLab CE — with every repository you move across proved intact by matching commit IDs on the old host and the new one.
Moving your source history onto a server you own is a one-way door. Get it wrong and you find out months later, when the branch somebody needs turns out never to have arrived.
We build the server on a machine you supply, put it behind HTTPS on the certificate you already hold, and bring your repositories over. Then we prove it: the head commit of every branch, read from the old host and from the new one, printed side by side.
A nightly backup goes in before we leave, and we clone a repository back out of that archive rather than telling you it works. The handover is as blunt about what comes next: nobody here watches your backups, and nobody here upgrades your server.
What's included
A git server of your own — Forgejo, Gitea or GitLab CE — answering on your hostname over HTTPS with the certificate you already hold, and over SSH for the everyday clone and push
Up to twenty repositories moved across with their full history, with the head commit of every branch read from both hosts and printed side by side
A plain list, per repository, of what did not come across, so nobody discovers in March that the wiki stayed behind
Up to twenty-five people and three organisations set up and ready to work, with sign-ups closed so strangers cannot open accounts on your server
Sign-in through the identity provider you already run, where you want it, proved with one real login rather than a screenshot of a settings page
A nightly backup running before we leave, with a repository cloned back out of the archive to prove it reads, and failed runs raised on a channel you name and test with us
A handover that keeps you independent: adding the twenty-sixth account, restoring from the archive, upgrading without breaking it, and what nobody here is doing for you afterwards
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A Linux machine of yours for the server, with root or sudo access over SSH and your go-ahead to open the ports it needs
Your platform (Forgejo, Gitea or GitLab CE) and the hostname people will use to reach it
A TLS certificate and its private key for that hostname
Your administrator and the people to set up (up to 25). For single sign-on, your provider's details, with our redirect address already registered there
The repositories to bring across (up to 20), and a read-only token for the old host if any of them are private
Where backup failure alerts should go: an email address with your relay details, a webhook, or a Gotify server
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The CI Runner & Pipeline Setup
Build machines wired into the git platform you already run, with up to three pipelines handed over running green on your own code.
The Proxmox Backup Server Setup
Proxmox Backup Server standing behind every guest on your node or cluster, with one of your machines restored from its backup, booted in front of you and timed before we hand anything over.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.