X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fwebserver-update.html;h=1abeaef54c25946db2846cf0ae1f891678efa55b;hb=52460473669cd31edd8cb8ae66c6b94c489e7e1d;hp=b0b0919f6786883c2e7f80f527655614fe335cfd;hpb=3c890b0540031fa87cc28514b3e4d0e23124fbcd;p=privoxy.git diff --git a/doc/webserver/developer-manual/webserver-update.html b/doc/webserver/developer-manual/webserver-update.html index b0b0919f..1abeaef5 100644 --- a/doc/webserver/developer-manual/webserver-update.html +++ b/doc/webserver/developer-manual/webserver-update.html @@ -1,239 +1,81 @@ - -
Privoxy Developer Manual | ||
---|---|---|
Prev |
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 |
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: -
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. -
Privoxy Developer Manual | +||
---|---|---|
Prev | ++ | + |
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+ |
+
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 + 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+ |
+
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.
+