Codeberg/Community
54
325
Fork
You've already forked Community
12

Availabiliy/uptime guarantee / HA? #36

Closed
opened 2019年03月23日 11:49:01 +01:00 by hjacobs · 7 comments

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/

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](https://ipfs.io/) 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/
Member
Copy link

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 contact@codeberg.org!

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 contact@codeberg.org!
Author
Copy link

@hw yes, I would gladly like to help out where I can --- will send an email!

@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.

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.
Member
Copy 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 codeberg@codeberg.org.

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 codeberg@codeberg.org.

I am not seeing what is still tracked here, can this get closed?

I am not seeing what is still tracked here, can this get closed?

ref: https://github.com/go-gitea/gitea/issues/13791 - pleace only comment if you have valid idears & suggestons :)

ref: https://github.com/go-gitea/gitea/issues/13791 - pleace only comment if you have valid idears & suggestons :)
Owner
Copy link

There are many more specific infrastructure related issues open, and this topic of course still on the roadmap. Closing as nothing really relevant seems to be tracked here 😉

There are many more specific infrastructure related issues open, and this topic of course still on the roadmap. Closing as nothing really relevant seems to be tracked here 😉
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#36
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?