Self-hosted Git provider

[heyainsleymae]

I'd be happy to help implement a self-hosted Git provider for the Standard Ebooks repositories over the next few months, as listed in the "Help wanted" section of the README.

Based on @acabal's blog post about the site's tech from a few years ago, I'd imagine you want something that isn't too resource-intensive. I've spun up a couple instances of Forgejo, a fork of Gitea that powers Codeberg, but would be willing offer a shortlist of options if you think it's worth the deliberation.

I have other relevant questions, but I'll hold off on adding them here until I've got confirmation that this is worth pursuing right now; I see there's a lot going into prep for Public Domain Day and other site improvements.

Thank you all for your work on Standard Ebooks. I've relied on much of your open-source code while taking over and modernising a literary magazine, and I'm hoping to contribute a book to the collection in the near future.

[acabal]

Great, Forgejo sounds like what we want, as the Readme entry was written before whatever Gitea drama had occurred.

The main benefit of GitHub for our project is that I don't have to think about maintaining it. Therefore we should have the same goal for whatever we replace it with. That probably means using Docker or something like that, and setting it up so that it updates itself for security and minor releases. Is that possible with Forgejo?

You're right that I'm extremely busy right now with PD day stuff and other improvements. So if this happens the actual release will have to occur at least a month from now.

The next step would be to confirm a what the replacement will be. It must have hands-off updates, must be able to migrate from Github, and install/config/migrate/update must be scriptable.

Our server currently runs stock Ubuntu 22.04 and we stick with each LTS until it is EOL'd, so very long term.