| Privoxy Developer Manual | ||||
|---|---|---|---|---|
| Prev | - +Prev | - - | Next | +|
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:
- +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) -+ make dok |
That will generate doc/webserver/user-manual, doc/webserver/developer-manual, doc/webserver/faq, doc/pdf/*.pdf and That will generate doc/webserver/user-manual, doc/webserver/developer-manual, doc/webserver/faq, 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:
- + "FILENAME">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 + Git, 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 Git. All set? If these are docs in the stable branch, then + do:
- - make webserver -+ 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.
+This will do the upload to the SourceForge webserver (which is manually syncronized with 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.