Synchronised Rieter instances #14
Loading…
Add table
Add a link
Reference in a new issue
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?
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.