| > Periodically merge upstream libgit2 in your custom fork, maintain your custom git server code and audit it for vulnerabilities, make sure everything still compiles with emscripten, deploy it. There's only a difference here because there exist off-the-shelf git packages for traditional VPS environments but there do not yet exist off-the-shelf git packages for serverless stacks. The OP is a pioneer here. The work they are doing is what will eventually make this an off-the-shelf thing for everyone else. > Rotate API keys to make sure your database service can talk to your storage service and your worker service. Huh? With Durable Objects the storage is local to each object. There is no API key involved in accessing it. > Then I don't even know how you'd backup all this Durable Object storage (under the new beta storage engine) automatically gives you point-in-time recovery to any point in time in the last 30 days. https://developers.cloudflare.com/durable-objects/api/storag... > And all that only to end up with worse latency than a VPS Why would it be worse? It should be better, because Cloudflare can locate each DO (git repo) close to whoever is accessing it, whereas your VPS is going to sit in one single central location that's probably further away. > and more size constraints on the repo and objects. While each individual repo may be more constrained, this solution can scale to far more total repos than a single-server VPS could. (I'm the tech lead for Cloudflare Workers.) |