Proxy Options
If you have several machines on the same version and architecture, using a local cache can not only save your mirror bandwidth, but also keep your usage down. One machine downloads and keeps copies of all the updated and newly-installed packages, and the other computers look to the first one.
- approx: You need to give an alias to each repository used on your network in /etc/approx.conf, like so:
debian http://ftp.debian.org/debianThen you need to divert apt to use the approx proxy, which uses port 9999 by default. Edit the /etc/apt/sources.list file, like so:
security http://security.debian.org
deb http://apt:9999/debian testing mainwhere "apt" is the hostname of your machine which runs approx. Make sure the hostname is in the /etc/hosts file of each machine. There are two good pages about approx.
deb http://apt:9999/security testing/updates main
deb-src http://apt:9999/debian unstable main
- apt-cacher: There's a howto over on Ubuntu tutorials.
- apt-cacher-ng: The howto is on Ubuntu Forums.
- apt-proxy: Linux.com has a howto on the setup.
P2P Options
If you're not worried about your own bandwidth or have only one computer with a given version and architecture, you can use peer to peer protocols like Bittorrent to ease the burden on your mirror. Your bandwidth will probably go up using these methods.
- apt-p2p: See Ubuntu Geek for the howto.
- debtorrent
: See the install documentation for details.
Zeroconf
If you have several computers but don't want the bother of setting up a cache, you can try using the Zeroconf/Avahi method, automatically finding the required package on other computers in your network. Think of this as a hybrid cache/P2P solution. It is, of course, zeroconf, so there's no configuration necessary.
apt-zeroconf
Hybrid
The possible combinations are numerous. There is a cool HowTo on setting up Approx and using the cache server to fetch via DebTorrent. It's in Spanish, but Google is your friend.
No comments:
Post a Comment