[Zope-Checkins] CVS: Zope/doc - INSTALL.txt:1.35.22.4
Chris McDonough
chrism@zope.com
Mon, 10 Mar 2003 09:46:14 -0500
Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv729
Modified Files:
Tag: new-install-branch
INSTALL.txt
Log Message:
Various edits.
=== Zope/doc/INSTALL.txt 1.35.22.3 => 1.35.22.4 ===
--- Zope/doc/INSTALL.txt:1.35.22.3 Wed Mar 5 13:54:44 2003
+++ Zope/doc/INSTALL.txt Mon Mar 10 09:46:10 2003
@@ -5,74 +5,74 @@
Building and installing Zope from source
----------------------------------------
- This document describes building and installing Zope on Unix.
- We will provide Windows instructions in later releases. We
- will also provide binary releases for some platforms.
+ This document describes building and installing Zope on UNIX and
+ Linux.
-Important notes
-
- Starting with Zope 2.7, Zope *REQUIRES* Python 2.2.2 or later.
- This is done to ease code sharing with Zope 3.
-
- See CHANGES.txt for important notes on this version of Zope.
+System requirements when building from source
+ bash or another Bourne shell variant
+ Python 2.2.2 or later installed somewhere in the system PATH
+ GNU make
Quick Start
If you are impatient, the following commands should get you up and
- running with Zope 2 using ZServer and ZODB 3 on Unix::
-
- ./configure --prefix=/where/to/install/zope
- make
- make instance
+ running on any UNIX that meet the system requirements::
- The last of these commands will prompt you to provide a user name
- and password for an administrator's account.
+ $ gunzip -c Zope-2.7.X-src.tar.gz | xar xvf
+ $ cd Zope-2.7.X
+ $ ./configure --prefix=/where/to/install/zope
+ $ make
+ $ make instance
These commands locate an appropriate version of Python, build Zope,
- and create a usable Zope "instance" in the current directory.
+ and create a usable Zope "instance" in the directory in which the
+ software was un-tarred. The last of these commands will prompt you
+ to provide a user name and password for an administrator's account.
You can now start Zope by running::
- ./bin/runzope
+ $ ./bin/runzope
If you get errors indicating that addresses are in use, then you
- will have to supply arguments to runzope to change the ports used for
- HTTP or FTP. The default HTTP and FTP ports used by ZServer are 8080
- and 8021 respectively. You can change the ports used by specifying
- the "port-base" parameter to runzope:
+ will have to supply arguments to runzope to change the ports used
+ for HTTP or FTP. The default HTTP and FTP ports used by Zope are
+ 8080 and 8021 respectively. You can change the ports used by
+ specifying the "port-base" parameter to runzope. For example, to
+ run Zope on ports 9080 and 9021:
- ./bin/runzope -X port-base=1000
+ $ ./bin/runzope -X port-base=1000
- You can then connect to Zope 2 by directing your browser to::
+ You can then connect to Zope by directing your browser to::
http://yourhost:8080/manage
- where yourhost is the name or address of the machine running Zope 2.
- If you changed the HTTP port as described, use a port number of 8080
- + the port-base value.
+ .. where 'yourhost' is the DNS name or IP address of the machine
+ running Zope. If you changed the HTTP port as described, use a port
+ number of 8080 + the port-base value.
You will be prompted for a user name and password. Use the user name
and password you provided in response to the prompts issued during
the "make instance" process.
- Now you're off and running! You should be looking at the Zope management
- screen which is divided into two frames. On the left you can navigate
- between Zope objects 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 Manager's Guide is a good place
- to start. You can access the Zope site at:
+ Now you're off and running! You should be looking at the Zope
+ management screen which is divided into two frames. On the left you
+ can navigate between Zope objects 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. You can access the Zope Book at:
- http://www.zope.org/
+ http://www.zope.org/Documentation/Books/ZopeBook
Have fun!
Building Zope
If you want to try out Zope in the simplest fashion, then run the
- conventional Unix build sequence::
+ conventional UNIX build sequence::
./configure --prefix /where/to/install/zope
make
@@ -109,41 +109,12 @@
build Zope but it's a good idea since it will compile Python C
extensions for you.
-Starting Zope with an existing web server
-
- See the WEBSERVERS.txt file for more information about configuring Zope
- with an existing web server.
-
-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.
+ * See CHANGES.txt for important notes on this version of Zope.
- With ZServer, you must start Zope manually using the one of the
- provided scripts. Typically, the command used to run the runzope
- script will be put in system startup scripts.
+Integrating Zope with an existing webserver
- ZServer is the prefered way to run Zope.
+ Zope doesn't require any existing webserver to run, but you can
+ integrate it with other webservers as necessary. See the
+ WEBSERVERS.txt file for more information about configuring Zope with
+ an existing web server.
- - If you *only* want to use PCGI and you don't need multi-threaded
- operation, you can have a special program, the pcgi_publisher,
- start Zope for you. See the WEBSERVER.txt file for details on
- using Zope with an existing webserver.