News for hackers. Stuff that matters.
Re:Why Puppet, Chef, Ansible aren't good enough by kaivi on Tuesday March 11, 2014 @09:15AM (#7378992)
Talking about automating apt-get, yum and the like, is there a way to cache frequently downloaded packages on developer machine in the same local network?

For instance, I have a bunch of disposable VMs, and I don't want them to download the same gigabytes every time I run init-deploy-test.

Re:Why Puppet, Chef, Ansible aren't good enough by unethical_ban on Tuesday March 11, 2014 @09:20AM (#7379013)
apt-mirror creates a full repository, and there's a tool called deb-squid-proxy or some combo of those words that lazily caches packages.
Re:Why Puppet, Chef, Ansible aren't good enough by kaivi on Tuesday March 11, 2014 @09:27AM (#7379043)
Oh thank you, not even sure how I missed it.
Re:Why Puppet, Chef, Ansible aren't good enough by jcastro on Tuesday March 11, 2014 @09:33AM (#7379073)
The server piece is "squid-deb-proxy" and for the clients it's "squid-deb-proxy-client".
Re:Why Puppet, Chef, Ansible aren't good enough by ema_rocca on Tuesday March 11, 2014 @09:22AM (#7379023)
You might want to give a try to apt-cacher-ng.

apt-get install apt-cacher-ng

Re:Why Puppet, Chef, Ansible aren't good enough by cdjk on Tuesday March 11, 2014 @11:16AM (#7379692)
I use this - and it's great with my slow internet connection. It's totally transparent, and I only notice it if my vm running it is down.

And despite the name, newer versions work with yum too (although I found I had to disable the fastest mirror yum plugin to get reliable caching).