> On 9 Mar 2020, at 09:09, Anton Marchukov <[email protected]> wrote: > > Hello Scott. > >> On 6 Mar 2020, at 22:23, Scott Dickerson <[email protected]> wrote: >> >> Advice ranges from increasing yarn timeouts to decreasing the size of >> packages uploaded to their registry so caching stuff on the proxy and not >> relying on upstream seems like the way to go. >> >> >> Caching on the proxy won't work since everything is https, unless squid is >> setup to intercept https traffic... > > Just to remind that in the past we have set up a Nexus server in oVirt PHX DC > that is capable of caching nodejs artefacts. AFAIK it is not actively used, > but does it makes sense to reconsider this decisions now? I think using Nexus > is more clear that doing SSL MITM on existing squid (although this is also > something doable).
But we can’t easily just change the urls in upstream code unless that server is accessible externally > > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat > > > > > > _______________________________________________ Infra mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/PJXUMWJYET3RKTR2O4V6GU75DVOHBNOL/
