[Checkins] SVN: zope2book/trunk/ Small updates to installing and infrastructure, updated some screenshots

Hanno Schlichting plone at hannosch.info
Wed Feb 11 09:44:56 EST 2009


Log message for revision 96448:
  Small updates to installing and infrastructure, updated some screenshots
  

Changed:
  U   zope2book/trunk/Figures/controlpanel.jpg
  U   zope2book/trunk/Figures/quickstart.png
  U   zope2book/trunk/Figures/zmi.png
  U   zope2book/trunk/source/InstallingZope.rst
  U   zope2book/trunk/source/ZopeArchitecture.rst

-=-
Modified: zope2book/trunk/Figures/controlpanel.jpg
===================================================================
(Binary files differ)

Modified: zope2book/trunk/Figures/quickstart.png
===================================================================
(Binary files differ)

Modified: zope2book/trunk/Figures/zmi.png
===================================================================
(Binary files differ)

Modified: zope2book/trunk/source/InstallingZope.rst
===================================================================
--- zope2book/trunk/source/InstallingZope.rst	2009-02-11 14:44:28 UTC (rev 96447)
+++ zope2book/trunk/source/InstallingZope.rst	2009-02-11 14:44:56 UTC (rev 96448)
@@ -164,14 +164,14 @@
 a recent Python version, the source Zope distribution does not.  Zope
 developers try to use the most recent Python for Zope, but often the latest
 Python version is more recent than the officially-supported Zope version.
-Zope 2.7 requires Python 2.3.2 or later, and Zope versions 2.5 and 2.6
-require a Python 2.1.*x* version equal to or greater than 2.1.3.  For the
+Zope 2.12 requires Python 2.5.4 or later, and Zope versions 2.11 and 2.10
+require a Python 2.4.*x* version equal to or greater than 2.4.3.  For the
 most recent information on which version of Python is required for
 compiling Zope, see the release notes on the release Web page.
 
 You can obtain detailed instructions for downloading, compiling, and
 installing Python from source at the `Python.org <http://www.python.org/>`_
-website.  Some Linux distributions ship with a pre-installed Python 2.3,
+website.  Most Linux distributions ship with a pre-installed Python 2.5,
 but care is required when attempting to use a vendor-installed Python to
 compile Zope: some of these vendor-supplied Python distributions do not
 ship the necessary Python development files needed to compile Zope from
@@ -205,23 +205,23 @@
   $ ./configure --prefix=/where/to/install/zope
 
 Replace */where/to/install/zope* above with an appropriate path, such as
-``~/myzope/zope2.7``.  This path is referred to as the *ZOPE_HOME*.  If you
+``~/myzope/zope2``.  This path is referred to as the *ZOPE_HOME*.  If you
 want to install Zope in a system directory instead of your user home,
-replace ``~/myzope/zope2.7`` with an appropriate path, e.g.,
-``/usr/local/zope2.7``, and make sure that you have suitable privileges for
+replace ``~/myzope/zope2`` with an appropriate path, e.g.,
+``/usr/local/zope2``, and make sure that you have suitable privileges for
 installing and starting Zope ('sudo' or 'root').
 
 If the configure script is unable to find your Python installation, it will
 report an error not unlike this one::
 
-  $ ./configure --prefix=~/myzope/zope2.7
+  $ ./configure --prefix=~/myzope/zope2
 
   Configuring Zope installation
   Testing for an acceptable Python interpreter...
 
   No suitable Python version found. You should install
-  Python version 2.3.3 before continuing. Versions
-  2.3.2 2.3.1 2.3 2.2.3 2.2.2 also work, but not as optimally.
+  Python version 2.5.4 before continuing. Versions
+  2.6.1 2.6.0 also work, but not as optimally.
 
 In this case, you must point the installer to your Python interpreter,
 which you should have installed previously, either from a binary package or
@@ -230,7 +230,7 @@
 Use the ``--with-python`` option to the configure script, e.g,. for a python
 living under ``/usr/local`` ::
 
-  $ ./configure --prefix=~/myzope/zope2.7 \
+  $ ./configure --prefix=~/myzope/zope2 \
   --with-python=/usr/local/bin/python
 
 Replace ``/usr/local/bin/python`` with the path to your Python executable.
@@ -248,7 +248,7 @@
   $ make install
   [ lots of output snipped ]
   Zope binaries installed successfully.
-  Now run '~/myzope/zope2.7/bin/mkzopeinstance.py'
+  Now run '~/myzope/zope2/bin/mkzopeinstance.py'
 
 With the Zope binaries installed, you are now ready to create a *Zope
 instance*, which holds configuration and runtime data for a single Zope
@@ -259,7 +259,7 @@
 ``~/myzope/instance``, in order to create a Zope instance, you would run
 the following command::
 
-  $ ~/myzope/zope2.7/bin/mkzopeinstance.py
+  $ ~/myzope/zope2/bin/mkzopeinstance.py
 
 You will need to provide the following values:
 
@@ -274,7 +274,7 @@
   username or password for your initial Zope user, run::
 
   $ cd ~/myzope/instance
-  $ ~/myzope/zope2.7/bin/zpasswd.py inituser
+  $ ~/myzope/zope2/bin/zpasswd.py inituser
 
 You will have to provide the username and password you wish to set;
 optionally, you can specify the hashing method and an additional domain
@@ -384,9 +384,7 @@
 ``ZServer`` (Zope's server) supports ``setuid()`` on POSIX systems in order
 to be able to listen on low-numbered ports, such as 21 (FTP) and 80 (HTTP),
 but drop root privileges when running; on most POSIX systems, only the
-``root`` user can do this.  Versions of Zope prior to 2.6 had less robust
-versions of this support.  Several problems were corrected for the 2.6
-release.
+``root`` user can do this.
 
 The most important thing to remember about this support is that you don't
 *have* to start ZServer as root, unless you want to listen for requests on
@@ -407,17 +405,10 @@
 Your Zope Installation
 ----------------------
 
-To use and manage Zope, you will need a web browser.  Since Zope's
-management interface (ZMI) is written entirely in HTML, any browser that
-understands modern HTML enables you to manage a Zope installation.
-Mozilla, any 3.0+ version of Microsoft Internet Explorer, or Netscape
-Navigator will do.  Other browsers that are known to work with Zope include
-Opera, Galeon, Konqueror, OmniWeb, Lynx, and W3M.
+To use and manage Zope, you will need a web browser. Start a web browser on the
+same machine on which you installed Zope, and browse to the URL
+`http://localhost:8080/ <http://localhost:8080/>`_.
 
-Start a web browser on the same machine on which you installed
-Zope, and browse to the URL `http://localhost:8080/
-<http://localhost:8080/>`_.
-
 If your Zope instance has been properly installed, and you're visiting the
 correct URL, you will be presented with the Zope "QuickStart" screen.
 
@@ -432,11 +423,10 @@
 Logging In
 ----------
 
-To do anything remotely interesting with Zope, you need to use its
-management interface: the *ZMI*.  Zope is completely web-manageable.  To
-log into the ZMI, use your web browser to navigate to Zope's management
-URL.  Assuming you have Zope installed on the same machine from which you
-are running your web browser, the Zope management URL will be
+For some of the tasks you want to do with Zope, you need to use its management
+interface: the *ZMI*. To log into the ZMI, use your web browser to navigate to
+Zope's management URL. Assuming you have Zope installed on the same machine
+from which you are running your web browser, the Zope management URL will be
 `http://localhost:8080/manage <http://localhost:8080/manage>`_.
 
 Successful contact with Zope via this URL will result in an authentication
@@ -462,7 +452,7 @@
 
 The Control Panel displays information about your Zope, such as the Zope
 version you are running, the Python version that Zope is using, the system
-platform, the INSTANCE_HOME, the ZOPE_HOME, Zope's process id, the network
+platform, the INSTANCE_HOME, the CLIENT_HOME, Zope's process id, the network
 services that have been started, how long Zope has been running for, and
 other installation specifics.  Several buttons and links will also be
 shown.
@@ -485,13 +475,6 @@
 Controlling the Zope Process from the Command Line
 --------------------------------------------------
 
-To stop a manually-run Zope on Windows, press "Ctrl+C" while the console
-window under which Zope is running is selected.  To stop a Zope on Windows
-that was run as a service, find the service with the name you assigned to
-your Zope in the Services Control Panel application, and stop the service.
-
-To stop Zope on UNIX, do one of the following:
-
 - If you started Zope in the foreground, press "Ctrl+C" in the terminal
   window from which you started Zope.
 
@@ -499,21 +482,17 @@
 
   $ ~/myzope/instance/bin/zopectl stop
 
-* Use the UNIX "kill" command against the process id in the
+* On Unix use the "kill" command against the process id in the
   "var/Z2.pid" file inside the Zope instance directory::
 
   $ kill `cat var/Z2.pid`
 
 
-
 Customizing your Zope instance
 ------------------------------
 
-As of Zope 2.7.0, configuration is no longer done with a mix of environment
-variables and command line options. Instead, the file
-'$INSTANCE_HOME/etc/zope.conf' contains numerous configuration directives
-for customization.  This configuration scheme greatly enhances Zope
-manageability and configurability.
+Zope's configuration is done via the file '$INSTANCE_HOME/etc/zope.conf'.
+This contains numerous configuration directives for customization.
 
 The ``zope.conf`` file features extensive inline documentation, which we
 will not reproduce here.  Instead, we will give an overview and some
@@ -559,18 +538,6 @@
 unnecessary overhead, you should ensure that this directive is set to
 ``off`` unless you are actively troubleshooting a problem.
 
-Additional ``products`` directories
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-This directive can be used to specify additional ``Products`` directories,
-or additional folders in which Zope looks for third-party and other add-on
-Zope Products.  Specifying a separate directory for commonly-used,
-third-party Products, such as CookieCrumbler or CMF and Plone packages,
-maintains a better separation of core Zope Products and third-party add-ons
-and improves maintainability.  Another common use for this directive is
-employed by Zope Product developers, who use it to specify a
-version-controlled development directory.
-
 Switch the User the Zope process runs as: ``effective-user``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -581,16 +548,6 @@
 first place is to be able to bind to *privileged* ports, or ports with
 values below 1024.
 
-Configuring the Session machinery
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Use the ``maximum-number-of-session-objects`` directive to limit the number
-of session objects.  This value defaults to 1000 objects; 0 means
-unlimited.
-
-``session-timeout-minutes`` sets the Session timeout period in minutes. The
-default is 20.
-
 Logging
 ~~~~~~~
 
@@ -620,36 +577,6 @@
 Troubleshooting and Caveats
 ---------------------------
 
-Running zopectl returns with an OSError
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-When running Zope on a 2.6.x Linux kernel, Solaris or Mac OS X, zopectl
-returns an error ``OSError: [Errno 10] No child processes``. This is due to
-a bug in Zope 2.7.0. You have the following options:
-
-- Install a patch currently in CVS. See http://zope.org/Collectors/Zope/1235
-  for the collector log and a small patch. The patch file is named
-  ``zdctl.diff``. Download it to a temporary directory, e.g., ``/tmp``. Then
-  'cd' to the directory ``$ZOPE_HOME/lib/python/zdaemon`` (continuing our
-  previous example, this would be ``~/myzope/zope2.7/lib/python/zdaemon``)
-  and run the patch command, e.g.::
-  
-   $ cd ~/myzope/zope2.7/lib/python/zdaemon
-   $ patch < /tmp/zdctl.diff'.
-  
-  The patch program should respond with an output similar to ``patching
-  file zdctl.py``.
-
-- If running on Linux: downgrade to a 2.4.x kernel
-
-- Work around this issue by placing Zope in the background manually with::
-
-   $ nohup ~/myzope/instance/bin/runzope &
-
-Note though that your Zope instance will not be automatically restarted by
-'zdaemon' this way, and that this method should not be used on a production
-server.
-
 Browser cannot connect to port 8080
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -662,11 +589,11 @@
 
  ...
  ------
- 2004-04-21T21:48:27 INFO(0) ZServer HTTP server started at Wed Apr 21 21:48:27 2004
+ 2009-01-21T21:48:27 INFO(0) ZServer HTTP server started at Wed Jan 21 21:48:27 2009
  Hostname: arod
  Port: 9673
  ------
- 2004-04-21T21:48:27 INFO(0) ZServer FTP server started at Wed Apr 21 21:48:27 2004
+ 2009-01-21T21:48:27 INFO(0) ZServer FTP server started at Wed Jan 21 21:48:27 2009
  Hostname: arod
  Port: 8021
  ...
@@ -680,11 +607,6 @@
 information can be found in the ``log/event.log`` file in your
 ``INSTANCE_HOME`` directory.
 
-Certain versions of Microsoft Internet Explorer 5.0.1 and 5.5 are
-incompatible with the ZMI in some respects, which manifest themselves as an
-inability to properly log in.  If you have trouble logging in with IE 5.0.1
-or IE 5.5, try a different browser or upgrade to a later version.
-
 Forgot administrative password
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

Modified: zope2book/trunk/source/ZopeArchitecture.rst
===================================================================
--- zope2book/trunk/source/ZopeArchitecture.rst	2009-02-11 14:44:28 UTC (rev 96447)
+++ zope2book/trunk/source/ZopeArchitecture.rst	2009-02-11 14:44:56 UTC (rev 96448)
@@ -117,26 +117,23 @@
 Through-The-Web Management
 --------------------------
 
-To create and work with Zope objects, you use your Web browser
-to access the *Zope management interface* (ZMI). All management and
-application development can be done completely through the Web
-using only a browser. The ZMI provides a
-familiar, Windows Explorer-like view of the Zope object
-system. Through the ZMI, a developer can create
-and script Zope objects, or even define new kinds of objects,
-without requiring access to the file system of the web server.
+To create and work with Zope objects, you can use your Web browser to access
+the *Zope management interface* (ZMI). Basic management and application
+configuration tasks can be done completely through the Web using only a
+browser. The ZMI provides a familiar, Windows Explorer-like view of the Zope
+object system.
 
-Objects can be dropped in anywhere in the object hierarchy. Site
-managers can work with their objects by clicking on tabs that
-represent different "views" of an object. These views vary
-depending on the type of object. A "DTML Method" Zope object,
-for example, has an "Edit" tab, which allows you to edit the
-document's source; a "Database Connection" Zope object
-provides views that let you modify its connection string or
-caching parameters. All objects also have a
-"Security" view that allows you to manage their individual access control
-settings.
+Any object in the object hierarchy can be configured. Site managers can work
+with their objects by clicking on tabs that represent different "views" of an
+object. These views vary depending on the type of object. For example a
+"Database Connection" Zope object provides views that let you modify its
+connection string or caching parameters. All objects also have a "Security"
+view that allows you to manage their individual access control settings.
 
+Zope had a much larger focus on Through-The-Web activities in its beginning.
+In recent years the Through-The-Web model has been discouraged for any kind of
+development and reduced to configuration tasks.
+
 Security and Safe Delegation
 ----------------------------
 
@@ -201,19 +198,18 @@
 Acquisition
 -----------
 
-One of the most powerful aspects of Zope is *acquisition*, whose
-core concepts are simply that:
+One more prominent aspect of Zope is *acquisition*, whose core concepts are
+simply that:
 
-*  Zope objects are contained inside other objects (such as Folders).
+* Zope objects are contained inside other objects (such as Folders).
 
-*  Objects can "acquire" attributes and behavior from
-   their containers.
+* Objects can "acquire" attributes and behavior from their containers.
 
 The concept of acquisition works with all Zope objects and
 provides an extremely powerful way to centralize common
 resources. A commonly-used SQL query or snippet of HTML, for
 example, can be defined in one Folder, and objects in sub-folders
-can use it automatically through acquisition. If the query needs
+can use it through acquisition. If the query needs
 to be changed, you can change it in one place without worrying
 about all of the sub-objects that use the same query.
 
@@ -226,34 +222,23 @@
 this analogy; these are discussed in the 
 `Advanced Zope Scripting <ScriptingZope.html>`_ chapter.
 
-Because objects are acquired by starting at the current level in
-their containment hierarchy and searching upward, it is easy to
-specialize areas of your site with a minimum level of work. If, for
-example, you had a Folder named "Sports" on your site containing
-sports-related content, you could create a new header and footer
-document in the Sports Folder that use a sports-related
-theme. Content in the Sports folder and its sub-folders will then
-use the specialized sports-related header and footer found in the
-Sports Folder, rather than the site's main header and footer.
-
 Acquisition is explained in further detail in the chapter on
 `Acquisition <Acquisition.html>`_ .
 
 Zope Is Extensible
 ------------------
 
-Zope is highly extensible, and advanced users can create new
-types of Zope objects, either by writing new Zope add-ons in
-Python, or by building them entirely through the Web. The Zope
+Zope is highly extensible, and component developers can create new
+types of Zope objects by writing new Zope add-on in Python. The Zope
 software provides a number of useful, built-in components to aid
 extension authors in development, including a robust set of framework classes
 that take care of most of the details of implementing new Zope
 objects.
 
-A number of Zope add-on products are available that provide
+A number of Zope add-ons are available that provide
 features like drop-in web discussion topics, desktop data
 publishing, XML tools, and e-commerce integration. Many of these
-products have been written by highly active members of the
+add-ons have been written by highly active members of the
 Zope community, and most are also open source.
 
 Fundamental Zope Components
@@ -297,6 +282,7 @@
 
 Relational database
 -------------------
+
 You don't have to store your information in Zope's object database if you
 don't want to.  Zope also works with other relational databases,
 including *Oracle*, *PostgreSQL*, *Sybase*, and *MySQL*.
@@ -307,14 +293,10 @@
 Zope can, of course, work with documents and other files stored on your
 server's file system.
 
-ZClasses
---------
-
-Zope allows site managers to add new object types to Zope using the ZMI.
-These new object types are called *ZClasses*.
-
 Products
 --------
 
 Zope also allows site managers to add new, pre-built object types to Zope
-by installing *Product* files on the Zope server file system.
+by installing add-ons on the Zope server file system. These are referred to
+as Products or Add-ons. Technically they are normal Python packages.
+



More information about the Checkins mailing list