Mirroring repos/proxy server #67
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vieter-v/vieter#67
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The option to mirror a repo, optionally while specifying a regex expression that matches package names or architectures, might be useful to implement. A periodic re-sync might allow us to install a vieter server in our local netwokr & use it as a proxy or something.
I've brainstormed this a bit just now.
The mirroring server could simply poll the main Vieter server every n minutes, just like the agents. The Vieter server could expose an endpoint that lists what packages in specific repositories/arch-repositories have changed since a given timestamp. The mirroring server would then only have to pull down these packages.
The mirror server implementation itself could simply use the existing repo implementation. The only complexity would be implementing streaming downloads, as vlib does not currently support this.