afaik it's not possible to have an untrusted git server, at a minimum ram contents will be plaintext.
before i undertook this, i had never heard of git-bundle:
The only thing that's going to remain resident after a push/pull is os level file system cache. There's no daemon when operating git over ssh.
Are container escapes on major hosting services common enough to even worry about? I don't hear much about them.
Or are you concerned about AWS/Vultr/Digital Ocean stealing your code? That seems like paranoia. They have world class developers, best in the industry. They don't want your code. This isn't the movie Antitrust.
which addresses exactly none of what this project is intended to, since there’s no end-to-end encryption. (yes, if you don’t need end-to-end encryption on your git repo, this is too complicated for your use case.)
https://stackoverflow.com/a/377293
git daemon --reuseaddr --base-path=. --export-all --verbose
Others can just pull from the IP address. Works well for hacking in the field, a PR is just one shout away :)
For years, across two different jobs we just had bare repos on Linux servers - we used git's built in ssh support and we liked it. Worked great. We wanted a Pull Request workflow and moved to GitHub, but self hosted is fine.
All you really need is a server your developers can SSH into with a shared directory. $2 a month Vultr server and you're golden.
You want to get real spicy, you can just do this without a central server at all, The way God and Linus intended. git was designed to be decentralized. You don't even need to share the server, you can just pull from each other's repos if you give each other your SSH access to each other's repos.