APT proxy: Difference between revisions
(→How) |
(→How: Is a discussion page) |
||
| Line 10: | Line 10: | ||
Location will vary. | Location will vary. | ||
=How= | ==How== | ||
===Discussion=== | |||
We're spoiled for choice: | We're spoiled for choice: | ||
# apt-cacher -- The ng should have more features | # apt-cacher -- The ng should have more features | ||
# apt-cacher-ng -- This requires client configuration. | # apt-cacher-ng -- This requires client configuration. | ||
# | # [[squid]] as a transparent proxy | ||
# debtorrent (yeah, right) | ::[[User:AaronPeterson|AaronPeterson]] ([[User talk:AaronPeterson|talk]]) 13:38, 3 October 2014 (PDT) If this doesn't require reconfiguring the built machines I'd advocate for this solution. | ||
# [[squid-deb-proxy]] This also requires installing something on clients that may make them not work. when they are out in the field. | |||
# debtorrent (yeah, right) -- exactly | |||
Latest revision as of 16:46, 3 October 2014
What is it?[edit]
Proxy server for Debian / Ubuntu packages.
Why[edit]
Saves these packages locally and serves them to APT clients, as during upgrades and such, in order to conserve upstream bandwidth.
Where[edit]
FCS Location will vary.
How[edit]
Discussion[edit]
We're spoiled for choice:
- apt-cacher -- The ng should have more features
- apt-cacher-ng -- This requires client configuration.
- squid as a transparent proxy
- AaronPeterson (talk) 13:38, 3 October 2014 (PDT) If this doesn't require reconfiguring the built machines I'd advocate for this solution.
- squid-deb-proxy This also requires installing something on clients that may make them not work. when they are out in the field.
- debtorrent (yeah, right) -- exactly