Synchronised Rieter instances #14

Open
opened 2024-07-09 21:44:37 +02:00 by Jef Roosens · 0 comments

Distros often have multiple mirrors to serve their repositories, as a single server isn't capable of handling the bandwidth.

A swarm of Rieter instances could automate this process by synchronising their state. If one of the instances receives a new package, it sends it to the other servers. Once they're all ready to commit the package, they commit it at the same time, ensuring their repositories are synchronised.

This technique could also apply to mirroring, allowing a hosting provider to automatically provide multiple mirrors that are managed automatically using Rieter.

Distros often have multiple mirrors to serve their repositories, as a single server isn't capable of handling the bandwidth. A swarm of Rieter instances could automate this process by synchronising their state. If one of the instances receives a new package, it sends it to the other servers. Once they're all ready to commit the package, they commit it at the same time, ensuring their repositories are synchronised. This technique could also apply to mirroring, allowing a hosting provider to automatically provide multiple mirrors that are managed automatically using Rieter.
Jef Roosens added the
idea
label 2024-07-09 21:44:37 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
1 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: Chewing_Bever/rieter#14
There is no content yet.