Codeberg ──runs──▶ Forgejo ──forked from──▶ Gitea ──lives on──▶ GitHub
▲ │
└──────────────── hosts Forgejo ◀──────────────────────────────┘You can use SSH directly, but using something like gitolite makes managing the git repos easier.
My main gripe with this setup (gitolite + cgit) is the lack of repository labels/tags. You can define a namespaced/scoped category, but that's not as flexible as a hierarchical tag system.
The syntax for SSH access is user@hostname:/path/to/git/repo which you might recognise from github. You can use this syntax with any machine, not just GitHub. It invokes a real ssh subprocess to do the connection, so all of your .ssh config and private keys apply. It runs an internal git command on the server to do the data transfer (git receive-pack or git upload-pack).
Though obviously don't forget to make sure this location is included in your backups, or at very least clone the repo at another location and keep that location uptodate with regular pushes/pulls (depending on which you consider your origin), lest you become one of the “disk/filesystem corruption ate my repo, and it was the only full copy” horror stories.