To increase adoption and be a sustainable option to the non-free alternatives (like github.com), Codeberg.org should be transparent about the infrastructure setup and availability/uptime guarantees.
I see that codeberg.org currently runs on a (single?) Hetzner server, is there any high-availability setup and backup in place?
Other (crazy?) ideas: integrate IPFS to have at least distributed read-only git clones (reduces server load and can bridge temporary downtimes), see also https://docs.ipfs.io/guides/examples/git/
Right on point! All improvements in this area definitely high-priority for Codeberg.org (and we will probably never be finished).
We have not yet put the infrastructure deploy scripts public (but would like to as soon time permits). If you like to do anything in this domain, please don’t hesitate to call us directly via firstname.lastname@example.org!
@hw yes, I would gladly like to help out where I can --- will send an email!
Indeed, I agree with OP. A document where an uptime and a mention of the backup system and all that is mentioned would be great. I couldn’t find one, but perhaps there is? If so, please link.
We wrote a bit about this in monthly letter reports, but did not create a formal document: offline backup machines are currently provided by founding members, creating hourly incremental backups.
Longer-term we’d like to set-up continuous database and filesystem snapshotting (for example via mariadb and cephfs asynchronous master-slave replication). If you would like to work on this, please send an email to email@example.com.
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?