You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To keep traffic to a minimum some mirrors would like to have a lastupdate file with timestamp of latest repo update. The mirror can then check this file before rsync'ing.
I'm not very fluent in golang, but seems to me like it should be possible to (optionally) generate or update a lastupdate file in repo root (or perhaps a configurable subfolder) every time repo is re-published. From shell we can run date +%s > /path/to/aptly/published/folder/lastupdate to generate a lastupdate file with timestamp.
Your Environment
The text was updated successfully, but these errors were encountered:
Hi @neolynx, I think for mirrors it would be useful with a lastupdate file, as that might be what they are used to. I can run a cronjob on the server and parse the Release file to generate a lastupdate file easily though, thanks for the idea!
Detailed Description
To keep traffic to a minimum some mirrors would like to have a
lastupdate
file with timestamp of latest repo update. The mirror can then check this file before rsync'ing.Context
See for example lastupdate check in archlinux's repo sync template (not an apt repo, but principle is the same).
Possible Implementation
I'm not very fluent in golang, but seems to me like it should be possible to (optionally) generate or update a lastupdate file in repo root (or perhaps a configurable subfolder) every time repo is re-published. From shell we can run
date +%s > /path/to/aptly/published/folder/lastupdate
to generate a lastupdate file with timestamp.Your Environment
The text was updated successfully, but these errors were encountered: