On Wed, 4 Sep 2019 09:51:58 -0500 Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > On Mon, Sep 2, 2019 at 3:26 PM Samuel Sieb <samuel@xxxxxxxx> wrote: > > > On 9/2/19 8:51 AM, Richard Shaw wrote: > > > \/fedora\/linux\/releases\/([0-9]+)\/Everything/x86_64\/(.*)$ > > > http://repo.mirrors.squid.internal/fedora/releases/$1/$2 > > > \/fedora\/linux\/updates\/([0-9]+)\/x86_64\/(.*)$ > > > http://repo.mirrors.squid.internal/fedora/updates/$1/$2 > > > > > > There's got to be a proper and generic way of doing this. Keeping > > > up with a list of mirrors isn't sustainable. > > > > The bigger problem is that most mirrors default to using https > > which you can't cache with a proxy. > > > > Looks like it's possible but not simple... > > https://elatov.github.io/2019/01/using-squid-to-proxy-ssl-sites/ A hack you might consider if the computers can exchange files. On one machine, the machine that will get the packages, turn off the switch that deletes packages after install in /etc/dnf/dnf.conf. Then, use rsync to put those packages in the appropriate directory on each of the dependent computers (something like var/cache/dnf/updates-[unique key]/) Then you can update the dependent computers as normal, and they will get their own metadata, but when the update occurs, they will skip the download because they will see that the packages are already downloaded. You could put the rsync commands in a script, and run the script after updating the master computer. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
