This file is indexed.

/usr/share/doc/bup/bup-web.html is in bup-doc 0.29-3.

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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta http-equiv="Content-Style-Type" content="text/css" />
  <meta name="generator" content="pandoc" />
  <meta name="author" content="Joe Beda jbeda@gmail.com" />
  <meta name="date" content="2017-04-01" />
  <title>bup-ftp(1) Bup debian/0.29-3</title>
  <style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<div id="header">
<h1 class="title">bup-ftp(1) Bup debian/0.29-3</h1>
<h2 class="author">Joe Beda <a href="mailto:jbeda@gmail.com">jbeda@gmail.com</a></h2>
<h3 class="date">2017-04-01</h3>
</div>
<h1 id="name">NAME</h1>
<p>bup-web - Start web server to browse bup repositiory</p>
<h1 id="synopsis">SYNOPSIS</h1>
<p>bup web [[hostname]:port]</p>
<p>bup web unix://path</p>
<h1 id="description">DESCRIPTION</h1>
<p><code>bup web</code> starts a web server that can browse bup repositories. The file hierarchy is the same as that shown by <code>bup-fuse</code>(1), <code>bup-ls</code>(1) and <code>bup-ftp</code>(1).</p>
<p><code>hostname</code> and <code>port</code> default to 127.0.0.1 and 8080, respectively, and hence <code>bup web</code> will only offer up the web server to locally running clients. If you'd like to expose the web server to anyone on your network (dangerous!) you can omit the bind address to bind to all available interfaces: <code>:8080</code>.</p>
<p>When <code>unix://path</code> is specified, the server will listen on the filesystem socket at <code>path</code> rather than a network socket.</p>
<p>A <code>SIGTERM</code> signal may be sent to the server to request an orderly shutdown.</p>
<h1 id="options">OPTIONS</h1>
<dl>
<dt>--human-readable</dt>
<dd>display human readable file sizes (i.e. 3.9K, 4.7M)
</dd>
<dt>--browser</dt>
<dd>open the site in the default browser
</dd>
</dl>
<h1 id="examples">EXAMPLES</h1>
<pre><code>$ bup web
Serving HTTP on 127.0.0.1:8080...
^C
Interrupted.

$ bup web :8080
Serving HTTP on 0.0.0.0:8080...
^C
Interrupted.

$ bup web unix://socket &amp;
Serving HTTP on filesystem socket &#39;socket&#39;
$ curl --unix-socket ./socket http://localhost/
$ fg
bup web unix://socket
^C
Interrupted.

$ bup web &amp;
[1] 30980
Serving HTTP on 127.0.0.1:8080...
$ kill -s TERM 30980
Shutdown requested
$ wait 30980
$ echo $?
0</code></pre>
<h1 id="see-also">SEE ALSO</h1>
<p><code>bup-fuse</code>(1), <code>bup-ls</code>(1), <code>bup-ftp</code>(1), <code>bup-restore</code>(1), <code>kill</code>(1)</p>
<h1 id="bup">BUP</h1>
<p>Part of the <code>bup</code>(1) suite.</p>
</body>
</html>