Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
Zope
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
Zope
Commits
5903b545
Commit
5903b545
authored
Oct 06, 2009
by
Chris Withers
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
- Tidy up installation docs
- Cover use on Windows - Cover buildout-based instances
parent
bdddae9c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
214 additions
and
75 deletions
+214
-75
doc/INSTALL.rst
doc/INSTALL.rst
+214
-75
No files found.
doc/INSTALL.rst
View file @
5903b545
============================
============
============================
Building and
installing Zope from sourc
e
Building and
Installing Zop
e
============================
============
============================
Welcome to Zope! This document describes building and installing
.. highlight:: bash
Zope on UNIX and Linux.
See ``doc/WINDOWS.rst`` for information about Windows
.
This document descibes how to get going with Zope
.
Prerequisites
Prerequisites
-------------
=============
System requirements when building from source
In order to use Zope, you must have the following pre-requisites
available:
- A supported version of Python, including the development support if
- A supported version of Python, including the development support if
installed from system-level packages. Supported versions include:
installed from system-level packages. Supported versions include:
...
@@ -24,58 +24,100 @@ System requirements when building from source
...
@@ -24,58 +24,100 @@ System requirements when building from source
headers installed which correspond to your system's ``zlib``.
headers installed which correspond to your system's ``zlib``.
- A C compiler capable of building extension modules for your Python
- A C compiler capable of building extension modules for your Python
(gcc recommended).
(gcc recommended). This is not necessary for Windows as binary
releases of the parts that would need compiling are always made
available.
- If you wish to install Zope as a Service on Windows, you will need
to have the `pywin32`__ package installed.
Building Zope using zc.buildout
__ https://sourceforge.net/projects/pywin32/
-------------------------------
Installing Zope
===============
Unless using buildout to build a zope instance as described
:ref:`below <buildout-instances>`, you will need to install Zope
separately. If you want to create a buildout-based Zope instance,
please skip directly to that section.
Installing Zope using virtualenv
--------------------------------
Zope can be installed within a virtualized Python environment using
``virtualenv`` as follows::
$ virtualenv --no-site-packages my_zope
$ cd my_zope
$ source bin/activate
$ bin/easy_install -i http://download.zope.org/Zope2/index/<Zope version> Zope2
Using ``virtualenv`` is **highly recommended**. Otherwise, you may encounter
unexpected conflicts with packages that have already been installed.
Once you've installed Zope, you'll need to :ref:`create an instance <classic-instances>`.
Installing Zope using zc.buildout
---------------------------------
Zope is built using the ``zc.buildout`` library, which needs to be
Unless you are `developing zope`__, you most likely
"bootstrapped" with your Python version. You have to download the Zope 2
want to be creating a :ref:`buildout-based Zope instance <buildout-instances>` rather
source distribution from `PyPI <http://pypi.python.org/pypi/Zope2>`_ first. E.g.::
that installing using buildout as described in this section.
$ wget http://pypi.python.org/packages/source/Z/Zope2/Zope2-2.12.0.tar.gz
__ http://docs.zope.org/developer/
However, if you really just want to create Zope instances using the
classic ``mkzopeinstance`` but with the software installed by buildout,
then you need to do the following:
- Download the Zope 2 source distribution from `PyPI`__
__ http://pypi.python.org/pypi/Zope2
- Bootstrap the buildout
- Run the buildout
On Linux, this can be done as follows::
$ wget http://pypi.python.org/packages/source/Z/Zope2/Zope2-<Zope version>.tar.gz
$ tar xfvz Zope2-2.12.0.tar.gz
$ tar xfvz Zope2-2.12.0.tar.gz
$ cd Zope2-2.12.0
$ cd Zope2-2.12.0
$ /path/to/your/python bootstrap/bootstrap.py
$ /path/to/your/python bootstrap/bootstrap.py
The bootstrap script creates a ``buildout`` script in ``bin``; run this
script to finish building Zope::
$ bin/buildout
$ bin/buildout
Once you've installed Zope, you'll need to :ref:`create an instance <classic-instances>`.
Installing Zope using easy_install
Installing Zope using easy_install
----------------------------------
----------------------------------
Zope can be installed using ``easy_install``
either using a global
Zope can be installed using ``easy_install``
, but it is recommended to
easy_install installation or within a virtualized Python environment
use ``virtualenv`` as described above to avoid unexpected conflicts
(using ``virtualenv``)::
with other packages installed directly in your python installation.
$ virtualenv --no-site-packages my_zope
However, if you want to use easy_install globally, all you need to do
$ cd my_zope
is::
$ source bin/activate
$ bin/easy_install -i http://download.zope.org/Zope2/index/<Zope version> Zope2
This will create the related scripts like ``mkzopeinstance`` within the
$ easy_install -i http://download.zope.org/Zope2/index/<Zope version> Zope2
``bin`` folder of your global or virtualized Python environment.
Using ``virtualenv`` is **highly recommended**. Otherwise you may encounter
This will create the related scripts such as ``mkzopeinstance`` within the
unexpected conflicts with already installed packages.
scripts folder of your python installation. You can then use them to
create instances as described below.
.. _classic-instances:
Creating a Zope Instance
Creating a
classic
Zope Instance
------------------------
================================
Once you've performed the install step, to begin actually using
Once you've installed Zope, you will need to create an "instance
Zope, you will need to create an "instance home", which is a
home". This is a directory that contains configuration and data for a
directory that contains configuration and data for a Zope server
Zope server process. The instance home is created using the
process. The instance home is created using the ``mkzopeinstance``
``mkzopeinstance`` script::
script::
$ bin/mkzopeinstance
$ bin/mkzopeinstance
If you use Zope from SVN, you will need to specify the Python interpreter
You can specify the Python interpreter to use for the instance
to use for the instance explicitly::
explicitly::
$ bin/mkzopeinstance --python=$PWD/bin/zopepy
$ bin/mkzopeinstance --python=$PWD/bin/zopepy
...
@@ -86,13 +128,96 @@ command-line options, run the script with the ``--help`` option::
...
@@ -86,13 +128,96 @@ command-line options, run the script with the ``--help`` option::
$ bin/mkzopeinstance --help
$ bin/mkzopeinstance --help
.. note::
.. note::
The traditional ``inplace`` build is no longer supported. You should
The traditional "inplace" build is no longer supported. If using
not use your buildout or virtualenv environment for creating a Zope
``mkzopeinstance``, always do so outside the buildout/virtualenv
instance. So create your Zope instance using ``mkzopeinstance`` always
environment. If you wish to manage your Zope instance using
outside the buildout/virtualenv environment.
buildout, please see the section below.
.. _buildout-instances:
Creating a buildout-based Zope Instance
=======================================
If you wish to use buildout to manage your Zope instance, then the
instance is created as follows:
* Create a directory for your instance. In this directory, create a
``etc``, ``logs`` and ``var`` subdirectories.
* Download the following file into your instance directory:
`http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py`__
__ http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py
.. highlight:: none
* Create a buildout configuration as follows:
.. topic:: buildout.cfg
:class: file
::
[buildout]
parts = instance
extends = http://svn.zope.org/*checkout*/Zope/tags/<Zope version>/versions.cfg
[instance]
recipe = zc.recipe.egg
eggs = Zope2
interpreter = py
scripts = runzope zopectl
initialization =
import sys
sys.argv[1:1] = ['-C',r'${buildout:directory}/etc/zope.conf']
This is the minimum but all the usual buildout techniques can be
used.
* Create a Zope configuration file starting as follows:
.. topic:: etc/zope.cfg
:class: file
::
%define INSTANCE <path to your instance directory>
python $INSTANCE/bin/py[.exe on Windows]
instancehome $INSTANCE
.. highlight:: bash
* Now, run the following commands::
$ /path/to/your/python bootstrap.py
$ bin/buildout
In the ``bin`` subdirectory of your instance directory, you will
find ``runzope`` and ``zopectl`` scripts that can be used as
normal.
Using your Zope instance
========================
There are various ways to run Zope from your newly created
instance. They are all described below.
Running Zope in the Foreground
------------------------------
To run Zope without detaching from the console, use the ``fg``
command (short for ``foreground``)::
Starting Zope as a Daemon
$ /path/to/zope/instance/bin/zopectl fg
In this mode, Zope emits its log messages to the console, and does not
detach from terminal.
Running Zope as a Daemon
-------------------------
-------------------------
Once an instance home has been created, the Zope server can now be
Once an instance home has been created, the Zope server can now be
...
@@ -104,23 +229,47 @@ During start, zope emits log messages into ./log/event.log
...
@@ -104,23 +229,47 @@ During start, zope emits log messages into ./log/event.log
You can examine it with the usual tools (cat, more, tail)
You can examine it with the usual tools (cat, more, tail)
and see if there are any errors preventing zope from starting.
and see if there are any errors preventing zope from starting.
.. highlight:: none
.. note::
Running Zope in the Foreground
For this to work on Windows, the Zope instance must be installed as
------------------------------
a Service. This is done with::
By default, ``zopectl start`` will start a background process (a
bin\zopectl install
"daemon) that manages Zope. ``zopectl stop`` will stop the background
process. To run Zope without detaching from the console, use the ``fg``
command (short for ``foreground``)::
$ /path/to/zope/instance/bin/zopectl fg
If you later want to remove this Service, do the following::
In this mode, Zope emits its log messages to the console, and does not
bin\zopectl remove
detach from terminal.
For the full list of options available for setting up Zope as a
Windows Service, do::
bin\zopectl install --help
.. highlight:: bash
Integrating with System Startup
-------------------------------
zopectl can be linked as rc-script in the usual start directories
on linux or other System V unix variants.
You can use ``zopectl`` interactively as a command shell by just
calling it without any arguments. Try ``help`` there and ``help <command>``
to find out about additionally commands of zopectl. These commands
also work at the command line.
.. note::
On Windows, a Service can be installed and set to start
automatically with the following:
.. code-block:: none
bin\zopectl install --startup=auto
Configuring Zope
Configuring Zope
----------------
================
Your Zope instance is configured through a file, either found by
Your Zope instance is configured through a file, either found by
default::
default::
...
@@ -136,8 +285,8 @@ or passed explicitly on the commandline::
...
@@ -136,8 +285,8 @@ or passed explicitly on the commandline::
Config file: /tmp/other.conf
Config file: /tmp/other.conf
When starting Zope, if you see errors indicating that an address is in
When starting Zope, if you see errors indicating that an address is in
use, then you
will have to supply arguments to runzope to change the ports
use, then you
may have to change the ports Zope uses for HTTP or FTP.
used for HTTP or FTP.
The default HTTP and FTP ports used by Zope are
The default HTTP and FTP ports used by Zope are
8080 and 8021 respectively. You can change the ports used by
8080 and 8021 respectively. You can change the ports used by
editing ./etc/zope.conf appropriately.
editing ./etc/zope.conf appropriately.
...
@@ -152,21 +301,8 @@ The section in the configuration file looks like this::
...
@@ -152,21 +301,8 @@ The section in the configuration file looks like this::
The address can just be a port number as shown, or a host:port
The address can just be a port number as shown, or a host:port
pair to bind only to a specific interface.
pair to bind only to a specific interface.
Integrating with System Startup
-------------------------------
zopectl can be linked as rc-script in the usual start directories
on linux or other System V unix variants.
You can use ``zopectl`` interactively as a command shell by just
calling it without any arguments. Try ``help`` there and ``help <command>``
to find out about additionally commands of zopectl. These commands
also work at the command line.
Logging In To Zope
Logging In To Zope
------------------
==================
Once you've started Zope, you can then connect to the Zope webserver
Once you've started Zope, you can then connect to the Zope webserver
by directing your browser to::
by directing your browser to::
...
@@ -181,6 +317,11 @@ You will be prompted for a user name and password. Use the user name
...
@@ -181,6 +317,11 @@ 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
and password you provided in response to the prompts issued during
the "make instance" process.
the "make instance" process.
If you are using a buildout-based Zope instance, you will need to
create a user as follows::
$ bin/zopectl adduser username password
Now you're off and running! You should be looking at the Zope
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
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
can navigate between Zope objects and on the right you can edit them
...
@@ -189,12 +330,10 @@ of the frame.
...
@@ -189,12 +330,10 @@ of the frame.
If you haven't used Zope before, you should head to the Zope web
If you haven't used Zope before, you should head to the Zope web
site and read some documentation. The Zope Documentation section is
site and read some documentation. The Zope Documentation section is
a good place to start. You can access it at:
a good place to start. You can access it at http://docs.zope.org/
http://docs.zope.org/
Troubleshooting
Troubleshooting
---------------
===============
- This version of Zope requires Python 2.5.4 or better, including
- This version of Zope requires Python 2.5.4 or better, including
2.6.x. It will *not* run with Python 3.x.
2.6.x. It will *not* run with Python 3.x.
...
@@ -210,4 +349,4 @@ Troubleshooting
...
@@ -210,4 +349,4 @@ Troubleshooting
you built Python from source all the configuration information
you built Python from source all the configuration information
should already be available.
should already be available.
- See
``doc/CHANGES.rst`
` for important notes on this version of Zope.
- See
the :doc:`CHANGES
` for important notes on this version of Zope.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment