[Zope-Checkins] CVS: Zope/doc - CHANGES.txt:1.528.2.6 INSTALL.txt:1.32.10.2
Chris McDonough
chrism@zope.com
Tue, 8 Oct 2002 14:41:34 -0400
Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv20268/doc
Modified Files:
Tag: chrism-install-branch
CHANGES.txt INSTALL.txt
Log Message:
Merging HEAD into chrism-install-branch.
=== Zope/doc/CHANGES.txt 1.528.2.5 => 1.528.2.6 ===
--- Zope/doc/CHANGES.txt:1.528.2.5 Sat Sep 28 21:40:30 2002
+++ Zope/doc/CHANGES.txt Tue Oct 8 14:41:03 2002
@@ -22,76 +22,6 @@
We now check to make sure a content-type header is not
already set before allowing a page template to set its own.
- - Fixed bug in manage_editProperties which used an incorrect default
- for several types of property when they were not found in the
- REQUEST.
-
- - Fixed broken management form for TopicIndexes.
-
- - Fixed bug in z2.py where it would eat certain socket error exceptions
- at startup.
-
- - Collector #550: Exceptions in XML-RPC requests no longer envoke
- standard_error_message. Plain text error messages are instead added to
- the fault string. In debug mode, a full traceback is also included
- since access to the error log is not a given for XML-RPC developers.
-
- - Collector #512,541: Fixed broken WebDAV compatiblity
- with Cadaver 0.20.X due to a missing Lock-Token header.
-
- - Zope Page Templates set a 'content-type' header even if
- the result of their execution was not rendered to the browser.
- We now check to make sure a content-type header is not
- already set before allowing a page template to set its own.
-
- - Collector #586: Generated 'start' scripts had a nonsensical
- export of an "INST_HOME" environment variable.
-
- - Collector #538: Hybrid path expressions no longer attempt to call
- a value returned by the final, non-path alternate.
-
- - Collector #573: ZTUtils Iterator didn't catch AttributeError.
-
- - Deprecated hasRole alias in User.py failed to return result.
-
- - Collector #580: TALES evaluateBoolean() was squishing 'default'.
-
- - Collector #581: TALES Path traversal should not special-case a blank
- string in the second element position. It now skips directly
- to item access when a path element is blank or has a leading '_'.
-
- - Fixed inconsistent attribute access in TALES Paths.
-
- - Collector #587: fixed wrong migration to string methods in
- DTMLMethod.py
-
- - Collector #583: Searching for '/' with PathIndexes failed.
-
- - Fixed bug in manage_editProperties which used an incorrect default
- for several types of property when they were not found in the
- REQUEST.
-
- - Collector #574: Fixed write on HEAD requests caused by overzealous
- ETag support.
-
- - Fixed broken management form for TopicIndexes.
-
- - Fixed bug in z2.py where it would eat certain socket error exceptions
- at startup.
-
- - Collector #550: Exceptions in XML-RPC requests no longer envoke
- standard_error_message. Plain text error messages are instead added to
- the fault string. In debug mode, a full traceback is also included
- since access to the error log is not a given for XML-RPC developers.
-
- - Collector #512,541: Fixed broken WebDAV compatiblity
- with Cadaver 0.20.X due to a missing Lock-Token header.
-
- - Zope Page Templates set a 'content-type' header even if
- the result of their execution was not rendered to the browser.
- We now check to make sure a content-type header is not
- already set before allowing a page template to set its own.
-
- The title_or_id attribute of browser id managers and
session data managers is now accessible publically.
=== Zope/doc/INSTALL.txt 1.32.10.1 => 1.32.10.2 ===
--- Zope/doc/INSTALL.txt:1.32.10.1 Mon Sep 16 02:09:06 2002
+++ Zope/doc/INSTALL.txt Tue Oct 8 14:41:03 2002
@@ -2,9 +2,8 @@
----------------------------------------
This document describes building and installing Zope on Unix.
- We also provide binary releases for some platforms. See
- "Zope.org's download section":http://www.zope.org/Downloads
- for more information.
+ We will provide Windows instructions in later releases. We
+ will also provide binary releases for some platforms.
Important notes
@@ -14,17 +13,25 @@
See CHANGES.txt for important notes on Zope 2.5.
+
Quick Start
If you are impatient, the following commands should get you up and
- running with Zope 2 on Unix::
+ running with Zope 2 using ZServer and ZODB 3 on Unix::
+
+ python w_pcgi.py # Note, this must be Python 2.1
+ ./start
- ./configure; make; make install
- [cd to install directory]
- ./makeinstance
- [follow prompts]
- [cd to instance directory]
- ./zctl start
+ The first command builds and adjusts Zope. Take note of the user
+ name and password output at the end of this command. You will need
+ these to manage Zope.
+
+ If you get errors indicating that addresses are in use, then you
+ will have to supply arguments to z2.py to change the ports used for
+ HTTP or FTP. The default HTTP and FTP ports used by ZServer are 8080
+ and 8021 respectively. (See the help for the z2.py script by running
+ z2.py with the -h option for more information on how to specify
+ different ports)
You can then connect to Zope 2 by directing your browser to::
@@ -42,14 +49,30 @@
between Zope object and on the right you can edit them by selecting
different management functions with the tabs at the top of the frame.
- If you haven't used Zope before, you should head to the Zope web
- site and read some documentation. The Zope Book is a good place to
- start. It also contains more information on how to install Zope.
- You can access the Zope site at:
+ If you haven't used Zope before, you should head to the Zope web site
+ and read some documentation. The Zope Manager's Guide is a good place
+ to start. You can access the Zope site at:
'http://www.zope.org/'
-Notes
+ Have fun!
+
+Building Zope
+
+ There are some python scripts in the top-level directory that should
+ help you get started. You must run these scripts from the top-level
+ directory.
+
+ If you want to try out Zope in the simplest fashion using ZServer,
+ then run the script wo_pcgi::
+
+ python wo_pcgi.py
+
+ If you want to use PCGI and an existing web server run w_pcgi::
+
+ python w_pcgi.py
+
+ Notes
* You should be using Python 2.1 to run the build scripts.
@@ -67,12 +90,49 @@
* If you just want to use Zope components it's not necessary to build Zope
but it's a good idea since it will compile Python C extensions for you.
- * See the WEBSERVERS.txt file for more information about
- configuring Zope with an existing web server. See also the
- pcgi/README file for further informations on the installation of
- "PCGI" or "persistent CGI", a way to interface Zope with webservers
- which do not support "proxy passthrough".
+ * You can use PCGI and an existing web server if you use ZServer.
+
+Starting Zope with an existing web server
+
+ See the WEBSERVERS.txt file for more information about configuring Zope
+ with an existing web server. See also the pcgi/README file for further
+ informations on the installation of PCGI.
+
+Running Zope
+
+ There are two ways to run Zope:
+
+ - You can use ZServer, the integration of Zope and Medusa. You must
+ use ZServer if you want to use multiple concurrent threads.
+ ZServer is a server application that supports multiple protocols:
+
+ o HTTP -- ZServer is a Web server
+
+ o FTP -- ZServer is a file-transfer protocol server. This
+ allows you to use FTP-enabled publishing systems with Zope.
+
+ o PCGI -- PCGI is a lightweight protocol for forwarding
+ requests from other web servers, like Apache or Netscape, to
+ Zope. This makes it possible to use web server features like
+ connection encryption or logging with Zope.
+
+ o monitor -- ZServer has the capability to allow you to access
+ the Python interpreter directly over a network channel. If
+ you intend to use this, please read the 'DEBUGGING.txt'
+ document for more information.
+
+ With ZServer, you must start Zope manually using the z2.py script.
+ Typically, the command used to run the z2.py script will be put in
+ system startup scripts.
+
+ ZServer is the prefered way to run Zope.
+ - If you *only* want to use PCGI and you don't need multi-threaded
+ operation, you can have a special program, the pcgi_publisger,
+ start Zope for you. See the WEBSERVER.txt file for details on
+ using Zope with an existing webserver.
+ If you wish to enable Zope logging you must specify options on the
+ command line. See LOGGING.txt in the doc directory.