If you want to guard against temporary outages during application updates, you will need a lot of complexity in the software, feature switches, backwards-compatible data migrations, overall redundant structures and much more.
If you can live with Codeberg's 99.99% uptime, that's fine. If you want to raise that to 99.999%, this will require an exorbitant amount of additional funding to get there.
Codeberg Pages is a different story. Since it relies on Codeberg.org being available, the uptime can be at most the uptime of Codeberg, and less when there are further issues downstream. The service has no active development community and is only maintained by a few volunteers at the moment.
Codeberg.org
Als Antwort auf Mare Polaris • • •We accept donations for site reliability engineers. Check out docs.codeberg.org/improving-co…
We might accept applications later.
Donating to Codeberg | Codeberg Documentation
docs.codeberg.orgCodeberg.org
Unbekannter Ursprungsbeitrag • • •If you want to guard against temporary outages during application updates, you will need a lot of complexity in the software, feature switches, backwards-compatible data migrations, overall redundant structures and much more.
Some of it was touched here: blog.codeberg.org/the-hardest-…
If you can live with Codeberg's 99.99% uptime, that's fine. If you want to raise that to 99.999%, this will require an exorbitant amount of additional funding to get there.
The hardest scaling issue — Codeberg News
blog.codeberg.orgCodeberg.org
Als Antwort auf Codeberg.org • • •Codeberg Pages is a different story. Since it relies on Codeberg.org being available, the uptime can be at most the uptime of Codeberg, and less when there are further issues downstream. The service has no active development community and is only maintained by a few volunteers at the moment.
codeberg.org/Codeberg/pages-se…
pages-server
Codeberg.org