This file is indexed.

/usr/share/doc/apt-cacher-ng/html/config-servquick.html is in apt-cacher-ng 0.7.2-1ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=US-ASCII">
<title>Basic Configuration</title>
<link rel="previous" href="usage.html">
<link rel="ToC" href="index.html">
<link rel="up" href="index.html">
<link rel="next" href="config-serv.html">
</head>
<body>
<p><a href="usage.html">Previous</a> | <a href="index.html">Contents</a> | <a href="config-serv.html">Next</a></p>

<ul>
<li><a href="#config-servquick">Chapter 3: Basic Configuration</a>
<ul>
<li><a href="#server-config">3.1 Server Configuration</a></li>
<li><a href="#config-client">3.2 Client Configuration</a></li>
</ul></li>
</ul>
<h1><a name="config-servquick"></a>Chapter 3: Basic Configuration</h1>
<h2><a name="server-config"></a>3.1 Server Configuration</h2>
<p>
Unlike some rumors on the internet claim, there should be no need for exhausting configuration work to just test apt-cacher-ng and run it with default parameters. It's actually designed to bootstrap most of its working environment without additional help.
</p>
<p>
The package setup scripts used by distributions should already prepare working initial settings for apt-cacher-ng. Check the file <code>/etc/apt-cacher-ng/acng.conf</code> file where most settings are explained. For the beginning they should not be changed, the only interesting setting present there is the TCP port. See Advanced Server Configuration for details.
</p>
<p>
There is also a daily cron job which executes some maintenance work. Additional automated control commands can be added by administrator.
</p>
<h2><a name="config-client"></a>3.2 Client Configuration</h2>
<p>
From the client side, apt-cacher-ng can be used as a drop-in replacement for apt-cacher. The same rules apply, e.g. Debian/Ubuntu users should EITHER:
</p>
<ul><li>
Specify the caching machine as HTTP Proxy for APT, e.g. putting a line like the following into a file like /etc/apt/apt.conf.d/02proxy:
<pre><code>Acquire::http { Proxy "http://CacheServerIp:3142"; };
</code></pre>

</li>
</ul>
<p>
OR:
</p>
<ul><li>
Replace all mirror hostnames with cachinghost/hostname in sources.list, so
<pre><code>deb http://ftp.uni-kl.de/debian etch main
</code></pre>
<p>
should now become:
</p>
<pre><code>deb http://192.168.0.17:3142/ftp.uni-kl.de/debian etch main
</code></pre>

</li>
</ul>
<p>
<em>(assuming that CacheServerIp is 192.168.0.17 and the service port is 3142)</em>.
</p>
<p>
Mixing both configuration methods is not recommended and will lead to obscure APT failures in most cases.
</p>
<p>
Additionally, leading path component containing "apt-cacher/" or "apt-cacher?/" might be ignored by the server during the URL processing. This is intended behavior and exists to maintain backwards compatibility to sources.list entries configured for early versions of Apt-Cacher (based on CGI technology).
</p>

<hr><address>Comments to <a href='mailto:blade@debian.org'>blade@debian.org</a>
<br>
[Eduard Bloch, Sat, 08 Oct 2011 23:18:17 +0200]</address></body>
</html>