Hot answers tagged

3

This won't solve all your tasks, but maybe this is still helpful. Despite the name, apt-cacher-ng doesn't only work with Debian and derivatives, and is a caching proxy. Specialized for package files from Linux distributors, primarily for Debian (and Debian based) distributions but not limited to those. I'm using this in production in a similar (...


2

We use Squid for this; the nice thing about squid is that you can set individual expiry of objects based on a pattern match, fairly easily, which allows the metadata from the yum repo to be purged fairly quickly. The config we have which implements this: refresh_pattern (Release|Packages(.gz)*)$ 0 20% 2880 refresh_pattern (\.xml|xml\.gz)$ ...


1

we had a similar challenge and have solved it using local repos and a snapshot based storage system. We basically update the development repository, clone it for testing, clone that for staging and finally for production. The amount of disk used is limited that way, plus it's all slow sata storage and that's ok. The clients get the repository info from our ...


1

It looks like you might be using server-first SSL bumping, which according to the docs cannot handle SNI on the server and will use the server's IP as the certificate (since the server will no longer have a single hostname). Starting with Squid 3.5 there are new mechanisms called peek and stare that allow squid to observe the SNI negotiation to figure out ...



Only top voted, non community-wiki answers of a minimum length are eligible