X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fwebserver-update.html;h=50985b83ad87c7a0e62356ad2f57ac886ec28ef0;hp=b54d64626944fc16f1f0bd8aa578adb0a8516ae2;hb=6d810395712f0337682205c4ea304009c86c128f;hpb=89109daf604e0df9355fc49ae82e26baf1a47da0 diff --git a/doc/webserver/developer-manual/webserver-update.html b/doc/webserver/developer-manual/webserver-update.html index b54d6462..50985b83 100644 --- a/doc/webserver/developer-manual/webserver-update.html +++ b/doc/webserver/developer-manual/webserver-update.html @@ -1,260 +1,158 @@ - -
The webserver should be updated at least with each stable release. When - updating, please follow these steps to make sure that no broken links, - inconsistent contents or permission problems will occur (as it has many - times in the past!): -
If you have changed anything in the stable-branch documentation source - SGML files, do: -
make dok dok-pdf # (or 'make redhat-dok dok-pdf' if 'make dok' doesn't work for you) |
That will generate doc/webserver/user-manual, - doc/webserver/developer-manual, - doc/webserver/faq, - doc/pdf/*.pdf and - doc/webserver/index.html automatically. -
If you changed the manual page sources, generate - doc/webserver/man-page/privoxy-man-page.html - by running "make man". (This is - a separate target due to dependencies on some obscure perl scripts - [now in CVS, but not well tested]. See comments in GNUmakefile.) -
If you want to add new files to the webserver, create them locally in - the doc/webserver/* directory (or - create new directories under doc/webserver). -
Next, commit any changes from the above steps to CVS. All set? - If these are docs in the stable branch, then do: -
make webserver |
This will do the upload to the - webserver (www.privoxy.org) and ensure all files and directories - there are group writable. -
Please do NOT use any other means of transferring - files to the webserver to avoid permission problems. Also, please do not - upload docs from development branches or versions. The publicly posted - docs should be in sync with the last official release. -
+ The webserver should be updated at least with each stable release. + When updating, please follow these steps to make sure that no broken + links, inconsistent contents or permission problems will occur (as it + has many times in the past!): +
++ If you have changed anything in the stable-branch documentation + source SGML files, do: +
++
+
++ make dok dok-pdf # (or 'make redhat-dok dok-pdf' if 'make dok' doesn't work for you) ++ |
+
+ That will generate doc/webserver/user-manual, doc/webserver/developer-manual, doc/webserver/faq, doc/pdf/*.pdf and doc/webserver/index.html automatically. +
++ If you changed the manual page sources, generate doc/webserver/man-page/privoxy-man-page.html by + running "make man". + (This is a separate target due to dependencies on some obscure perl + scripts [now in CVS, but not well tested]. See comments in GNUmakefile.) +
++ If you want to add new files to the webserver, create them locally in + the doc/webserver/* directory (or create + new directories under doc/webserver). +
++ Next, commit any changes from the above steps to CVS. All set? If + these are docs in the stable branch, then do: +
++
+
++ make webserver ++ |
+
+ This will do the upload to the webserver (www.privoxy.org) and ensure all files and + directories there are group writable. +
++ Please do NOT + use any other means of transferring files to the webserver to avoid + permission problems. Also, please do not upload docs from development + branches or versions. The publicly posted docs should be in sync with + the last official release. +
+