Re:GitHub Incident
by freedomben on Tuesday March 22, 2022 @01:15PM
(#30768779)
Ah interesting! I read somewhere that it uses the database for that, but I think they were mistaken.
Thanks that's quite helpful. If we do it in prod we'll have to accept single-instance.
Re:GitHub Incident
by qbasic_forever on Tuesday March 22, 2022 @02:25PM
(#30769603)
Yeah I forgot to mention too a lot of complexity goes away if you host it on a good IaaS platform. On AWS for example you could just mount an EBS volume as the bare repo root and use RDS for a database. Then you just have to deploy and manage an EC2 instance to host gitea's main process. It's more expensive to use those managed platforms but might be well worth the cost vs. doing it all yourself with a bare metal deployment of everything.
So the big issue for any non-trivial or highly available setup is going to be how you get high availability for the local storage volume. There are tons of options with various tradeoffs and levels of complexity here--simple local disk RAID, distributed filesystems like gluster or ceph, etc. I think this is the real crux of getting a good gitea instance going.
No matter what figure out and test a good backup and recovery solution!