-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mirror] Another termux mirror in Germany #18398
Comments
Thanks!
Yeah, would be nice, it was suggested by some other mirror as well. Unfortunately I don't see a good way to implement it except for patching/hacking aptly (which we use to control repo) to generate the file when publishing repo. Shouldn't be too hard I guess, but my golang skills are negligible |
Opened a feature request: aptly-dev/aptly#1229 |
Added to wiki . |
@SunRed there is now a lastupdate file at https://packages.termux.dev/apt/termux-main/lastupdate, it is generated by a cronjob that checks the date field in the Release file, every 5 minutes. |
Thanks for coming back to me about this. I adjusted my configuration and thus it should now check every 5 minutes and only do a full sync if necessary. :) |
I have this mirror running for quite a while now and was recently reminded again to finally contribute my mirror to this project.
The server is running at Hetzner in Falkenstein/Vogtland, Germany with a 1Gb/s connection and support for both ipv4 and ipv6 and is available at https://mirror.sunred.org/termux/ with the following sources.list entries:
I check every two hours using
rsync
on the origin server.Additionally there are 8 sync slots open for syncing with
rsync
andrsync-ssl
usingrsync://sync.mirror.sunred.org/termux
. I may put the main domain behind a caching reverse proxy at some point, hence the use of a different domain for the sync endpoint.Additionally I would like to know if it would be possible to provide a
lastupdate
file in the root of the mirror repo or in /termux-main/ where thelastsync
file is located (or maybe move this one to the root as well) to indicate when one of the repos was actually last updated. This would make it possible to optionally sync a mirror more frequently but only when necessary. This is similar to how other linux distros like Arch Linux do it with a sync script like here. With this I could e.g. check every 5-10 minutes more efficiently over http and only sync over rsync when packages were actually updated on the origin mirror.The text was updated successfully, but these errors were encountered: