The usual work, done for you
| Usually you'd set up | With SORN GIT |
|---|---|
| A database server | Built in, nothing to install |
| A reverse proxy and certificates | HTTPS built in, certificates renewed automatically |
| A second SSH port for Git | Git over SSH on the normal port 22 |
| Backup scripts, and hoping they work | Nightly backups, restored and checked every week |
| Watching for updates | Signed updates installed nightly, rolled back if they fail |
| Hardening the service | Locked-down systemd service, SELinux kept on |
What to run it on
SORN GIT uses about 50 MB of memory, so almost anything that runs Linux works:
- A small cloud VM with a domain name, to reach your code from anywhere.
- A mini PC at home or in the office, on your local network.
- An old laptop or desktop you no longer use.
It is tested on Rocky Linux 9, on amd64 and arm64. See what you need.
What's included
- Git over HTTPS and SSH, Git LFS for big files, protected branches and storage quotas.
- A web interface to browse code, manage people, keys and tokens, and see your server's health.
- Two-factor sign-in and passkeys, an admin area locked to your network, and secret scanning on push.
- Import and mirrors from GitHub or any HTTPS server, and push mirrors to keep a copy elsewhere.
- Email alerts when a backup fails, the disk fills up or someone unlocks the admin area.