1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
6 <title>Update the Webserver</title>
7 <meta name="GENERATOR" content=
8 "Modular DocBook HTML Stylesheet Version 1.79">
9 <link rel="HOME" title="Privoxy Developer Manual" href="index.html">
10 <link rel="PREVIOUS" title="Releasing a New Version" href=
12 <link rel="NEXT" title=
13 "Contacting the developers, Bug Reporting and Feature Requests" href=
15 <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
16 <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
19 <body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
20 "#840084" alink="#0000FF">
21 <div class="NAVHEADER">
22 <table summary="Header navigation table" width="100%" border="0"
23 cellpadding="0" cellspacing="0">
25 <th colspan="3" align="center">Privoxy Developer Manual</th>
29 <td width="10%" align="left" valign="bottom"><a href=
30 "newrelease.html" accesskey="P">Prev</a></td>
32 <td width="80%" align="center" valign="bottom"></td>
34 <td width="10%" align="right" valign="bottom"><a href="contact.html"
35 accesskey="N">Next</a></td>
38 <hr align="left" width="100%">
42 <h1 class="SECT1"><a name="WEBSERVER-UPDATE" id="WEBSERVER-UPDATE">7.
43 Update the Webserver</a></h1>
45 <p>The webserver should be updated at least with each stable release.
46 When updating, please follow these steps to make sure that no broken
47 links, inconsistent contents or permission problems will occur (as it has
48 many times in the past!):</p>
50 <p>If you have changed anything in the stable-branch documentation source
53 <table border="0" bgcolor="#E0E0E0" width="100%">
56 <pre class="PROGRAMLISTING">
57 make dok dok-pdf # (or 'make redhat-dok dok-pdf' if 'make dok' doesn't work for you)
63 <p>That will generate <tt class=
64 "FILENAME">doc/webserver/user-manual</tt>, <tt class=
65 "FILENAME">doc/webserver/developer-manual</tt>, <tt class=
66 "FILENAME">doc/webserver/faq</tt>, <tt class=
67 "FILENAME">doc/pdf/*.pdf</tt> and <tt class=
68 "FILENAME">doc/webserver/index.html</tt> automatically.</p>
70 <p>If you changed the manual page sources, generate <tt class=
71 "FILENAME">doc/webserver/man-page/privoxy-man-page.html</tt> by running
72 <span class="QUOTE">"<b class="COMMAND">make man</b>"</span>. (This is a
73 separate target due to dependencies on some obscure perl scripts [now in
74 CVS, but not well tested]. See comments in <tt class=
75 "FILENAME">GNUmakefile</tt>.)</p>
77 <p>If you want to add new files to the webserver, create them locally in
78 the <tt class="FILENAME">doc/webserver/*</tt> directory (or create new
79 directories under <tt class="FILENAME">doc/webserver</tt>).</p>
81 <p>Next, commit any changes from the above steps to CVS. All set? If
82 these are docs in the stable branch, then do:</p>
84 <table border="0" bgcolor="#E0E0E0" width="100%">
87 <pre class="PROGRAMLISTING">
94 <p>This will do the upload to <a href="http://www.privoxy.org/" target=
95 "_top">the webserver</a> (www.privoxy.org) and ensure all files and
96 directories there are group writable.</p>
98 <p>Please do <span class="emphasis"><i class="EMPHASIS">NOT</i></span>
99 use any other means of transferring files to the webserver to avoid
100 permission problems. Also, please do not upload docs from development
101 branches or versions. The publicly posted docs should be in sync with the
102 last official release.</p>
105 <div class="NAVFOOTER">
106 <hr align="left" width="100%">
108 <table summary="Footer navigation table" width="100%" border="0"
109 cellpadding="0" cellspacing="0">
111 <td width="33%" align="left" valign="top"><a href="newrelease.html"
112 accesskey="P">Prev</a></td>
114 <td width="34%" align="center" valign="top"><a href="index.html"
115 accesskey="H">Home</a></td>
117 <td width="33%" align="right" valign="top"><a href="contact.html"
118 accesskey="N">Next</a></td>
122 <td width="33%" align="left" valign="top">Releasing a New
125 <td width="34%" align="center" valign="top"> </td>
127 <td width="33%" align="right" valign="top">Contacting the developers,
128 Bug Reporting and Feature Requests</td>