Closed brianjmurrell closed 1 year ago
So, I was able to work this out. Simply after unpacking the tarball, but before running install.sh
one has to do:
sed -i -e '/^base_domain=/s/".*"/"$local_url"/' files/internals/internals.conf
Where one replaces $local_url
with one's local mirror of the upstream files:
maldet.sigs.ver maldet-sigpack.tgz maldet-sigpack.tgz.md5 maldet-cleanv2.tgz maldet-cleanv2.tgz.md5 maldet-clean.tgz.md5
which one has to of course set up a local mirror of.
It would be nice not to have to do this quite so hackily though. An argument to install.sh
to specify a local URL would be nicer.
This is a growing timing / capacity issue and has been resolved by moving the CDN into Cloudflare.
We seem to somewhat frequently hit issues downloading from the CDN. For example, just last night:
We need to be able to insulate ourselves from these kinds of external outages even if it means using a slightly (likely not even) outdated
maldet.sigs.ver
et al.) . While #363 is quite relevant once maldet is installed, how can theinstall.sh
be told to fetch the artefacts it needs to download (i.e.maldet.sigs.ver
, and whatever else might be downloaded) from a local server/service which we keep updated from the upstream https://cdn.rfxn.com/downloads?This would also actually ease load on the upstream CDN as we would/could update our mirror much less frequently than we run
maldet
in our CI (which is probably hundreds of times per day).