1.1 --- a/docs/CGI/NOTES.txt Fri Jun 09 22:58:34 2006 +0000
1.2 +++ b/docs/CGI/NOTES.txt Fri Jun 09 22:58:48 2006 +0000
1.3 @@ -1,10 +1,11 @@
1.4 Configuring Apache
1.5 ==================
1.6
1.7 -To configure applications without authenticators, use the config.py script
1.8 -in tools/Apache to set up CGI applications. For example:
1.9 +To configure applications without authenticators, use the
1.10 +webstack_apache_config.py script (installed with setup.py but also found in
1.11 +tools/Apache) to set up CGI applications. For example:
1.12
1.13 -python tools/Apache/config.py \
1.14 +python webstack_apache_config.py \
1.15 CGI \
1.16 /home/paulb/Software/Python/WebStack/examples/CGI/CookiesApp.py \
1.17 /etc/apache2/sites-available \
2.1 --- a/docs/JavaServlet/NOTES.txt Fri Jun 09 22:58:34 2006 +0000
2.2 +++ b/docs/JavaServlet/NOTES.txt Fri Jun 09 22:58:48 2006 +0000
2.3 @@ -1,11 +1,11 @@
2.4 Preparing the Application
2.5 =========================
2.6
2.7 -Use the build.py script in the tools/JavaServlet directory to create a Web
2.8 -application directory. Then, deploy the directory in the servlet container. For
2.9 -example:
2.10 +Use the webstack_java_build.py script (installed by setup.py but also found in the
2.11 +tools/JavaServlet directory) to create a Web application directory. Then,
2.12 +deploy the directory in the servlet container. For example:
2.13
2.14 -jython tools/JavaServlet/build.py examples/JavaServlet/SimpleApp.py \
2.15 +jython webstack_java_build.py examples/JavaServlet/SimpleApp.py \
2.16 examples/Common/Simple/ \
2.17 . \
2.18 web.xml \
2.19 @@ -35,13 +35,13 @@
2.20 WebStack resource without additional configuration being performed first:
2.21
2.22 * The web.xml template should be replaced with the protected-web.xml
2.23 - template in the build.py command. This alternative template produces a
2.24 - special deployment descriptor which introduces role-based authentication for
2.25 - the application. Consequently, upon seeing that the application requires a
2.26 - user with a given role, Tomcat will prompt for the username/password details
2.27 - of a user with that role, and once such a user has been authenticated, the
2.28 - resulting user identity is then made available via the API to the
2.29 - application.
2.30 + template in the webstack_java_build.py command. This alternative template
2.31 + produces a special deployment descriptor which introduces role-based
2.32 + authentication for the application. Consequently, upon seeing that the
2.33 + application requires a user with a given role, Tomcat will prompt for the
2.34 + username/password details of a user with that role, and once such a user
2.35 + has been authenticated, the resulting user identity is then made available
2.36 + via the API to the application.
2.37
2.38 * The server.xml configuration file in Tomcat should declare the protected
2.39 application as a privileged context; for example:
3.1 --- a/docs/ModPython/NOTES.txt Fri Jun 09 22:58:34 2006 +0000
3.2 +++ b/docs/ModPython/NOTES.txt Fri Jun 09 22:58:48 2006 +0000
3.3 @@ -1,10 +1,11 @@
3.4 Configuring Apache
3.5 ==================
3.6
3.7 -To configure applications without authenticators, use the config.py script
3.8 -in tools/Apache to set up mod_python applications. For example:
3.9 +To configure applications without authenticators, use the
3.10 +webstack_apache_config.py script (installed with setup.py but also found in
3.11 +tools/Apache) to set up mod_python applications. For example:
3.12
3.13 -python tools/Apache/config.py \
3.14 +python webstack_apache_config.py \
3.15 mod_python \
3.16 /home/paulb/Software/Python/WebStack/examples/ModPython/CookiesApp/CookiesHandler.py \
3.17 /etc/apache2/sites-available \