X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fwebserver-update.html;fp=doc%2Fwebserver%2Fdeveloper-manual%2Fwebserver-update.html;h=0777b74c289dfcc11b1b1ba29ea53b0c18c675a6;hp=6e1f21c4b5d07c3b20b71564315b3fc6237cf42d;hb=659cbbc13f413ed0c5dacd4d03060f48eb500011;hpb=ea95378cea9ef3e122952bb965618642e445aeb9 diff --git a/doc/webserver/developer-manual/webserver-update.html b/doc/webserver/developer-manual/webserver-update.html index 6e1f21c4..0777b74c 100644 --- a/doc/webserver/developer-manual/webserver-update.html +++ b/doc/webserver/developer-manual/webserver-update.html @@ -1,81 +1,239 @@ - - - - Update the Webserver - - - - - - - - -
-

7. Update the Webserver

-

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 && make dok-tidy
-
-

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.

-
- - - + +Update the Webserver
Privoxy Developer Manual
Prev 

7. Update the Webserver

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 && make dok-tidy

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. +


PrevHome 
Releasing a New Version  
\ No newline at end of file