Plone4安装指导
Plone4安装指导
http://www.315ok.org/blogfolder/203
http://www.315ok.org/logo.png
Plone4安装指导
Plone4安装指导
Installation Instructions
=========================
The installer will compile Python, Zope, and key required libraries from
source. (Basic build tools and common libraries are required. See
"Dependencies" and "Recommended Libraries" below.)
PLEASE NOTE: You have the option to run the installation as root or a
normal user. There are serious security implications to this choice.
The non-root method produces an install that will run the Zope server
with the same privileges as the installing user. This is probably not an
acceptable security profile for a production server, but may be
acceptable for testing and development purposes.
The 'root' method produces an install that runs the Zope server as a
distinct user identity with minimal privileges (unless you add them).
Providing adequate security for a production server requires many more
steps, but this is a better starting point.
PLEASE NOTE: You have the option to install Plone as a standalone
(single-instance) setup or as a clustered (ZEO) setup.
The clustered (ZEO) setup will take advantage of multi-core CPUs and is
recommended for a production deployment, while the standalone method is
easier for a desktop-based development setup.
For more detail on both root/non-root and ZEO/standalone choices, see
"Installing on Linux / Unix / BSD":http://plone.org/documentation/manual/installing-plone/installing-on-linux-unix-bsd
in the Plone.Org documentation section.
For a super-user (root) installation
————————————
If you run the installation with root privileges, it will install
Python/Zope/Plone to /usr/local/Plone
[Darwin (OS X) Note: Under Darwin, the default installation is to
/Applications/Plone for the root install. Please replace /usr/local with
/Applications in the instructions below.]
A "plone" user will be added, and Zope will be configured to
run under that user id. You will need to start Zope as root or via sudo.
To install Plone 4.1 in a stand-alone (single Zope instance) configuration:
PLEASE NOTE: You have the option to run the installation as root or a
normal user. There are serious security implications to this choice.
The non-root method produces an install that will run the Zope server
with the same privileges as the installing user. This is probably not an
acceptable security profile for a production server, but may be
acceptable for testing and development purposes.
The 'root' method produces an install that runs the Zope server as a
distinct user identity with minimal privileges (unless you add them).
Providing adequate security for a production server requires many more
steps, but this is a better starting point.
PLEASE NOTE: You have the option to install Plone as a standalone
(single-instance) setup or as a clustered (ZEO) setup.
The clustered (ZEO) setup will take advantage of multi-core CPUs and is
recommended for a production deployment, while the standalone method is
easier for a desktop-based development setup.
For more detail on both root/non-root and ZEO/standalone choices, see
"Installing on Linux / Unix / BSD":http://plone.org/documentation/manual/installing-plone/installing-on-linux-unix-bsd
in the Plone.Org documentation section.
For a super-user (root) installation
————————————
If you run the installation with root privileges, it will install
Python/Zope/Plone to /usr/local/Plone
[Darwin (OS X) Note: Under Darwin, the default installation is to
/Applications/Plone for the root install. Please replace /usr/local with
/Applications in the instructions below.]
A "plone" user will be added, and Zope will be configured to
run under that user id. You will need to start Zope as root or via sudo.
To install Plone 4.1 in a stand-alone (single Zope instance) configuration:
* cd to the installer directory and issue the following command:
>> sudo ./install.sh standalone (or `su; ./install.sh standalone` on a sudo-less system)
To install Plone 4.1 in a ZEO Cluster (ZEO server, 2 clients) configuration:
* cd to the installer directory and issue the following command:
>> sudo ./install.sh zeo (or `su; ./install.sh zeo` on a sudo-less system)
For a non-super-user (rootless) installation
——————————————–
If you run the installation while logged in as a normal (non-root) user,
Python/Zope/Plone will be built at $HOME/Plone (the user's home
directory, Plone subdirectory). You will need to start Zope using
the user identity used for the build, and it will run with the
privileges of that user.
To install Plone 4.1 in a stand-alone (single Zope instance) configuration:
* cd to the installer directory and issue the following command:
>> ./install.sh standalone
To install Plone 4.1 in a ZEO Cluster (ZEO server, 2 clients) configuration:
* cd to the installer directory and issue the following command:
>> ./install.sh zeo
Installation Options
====================
Usage: [sudo] install.sh [options] standalone|zeo
Install methods available:
standalone - install standalone zope instance
zeo - install zeo cluster
Use sudo (or run as root) for root install.
Options:
–target=pathname
Use to specify top-level path for installs. Plone instances
and Python will be built inside this directory.
Default is /usr/local/Plone for root install,
$HOME/Plone for non-root.
PLEASE NOTE: Your pathname should not include spaces.
–instance=instance-name
Use to specify the name of the operating instance to be created.
This will be created inside the target directory.
Default is 'zinstance' for standalone, 'zeocluster' for ZEO.
–clients=client-count
Use with the "zeo" install method to specify the number of Zope
clients you wish to create. Default is 2.
–user=user-name In a root install, sets the effective user for running the
instance. Default is 'plone'. Ignored for non-root installs. You should always
use the same user within a given target.
–with-python=/full/path/to/python2.6
If you have an already built Python that's adequate to run
Zope / Plone, you may specify it here.
virtualenv will be used to isolate the copy used for the install.
The specified Python will need to have been built with support
for libz and libjpeg and include the Python Imaging Library.
–password=InstancePassword
If not specified, a random password will be generated.
–libz=(auto|yes|no)
Overrides the automatic determination of whether and where to
install the libz compression library.
–libjpeg=(auto|yes|no)
Overrides the automatic determination of whether and where to
install the libjpeg JPEG library.
–readline=(auto|yes|no)
Optional. Installs a local readline library. Only necessary
on platforms with odd libraries (like OS X Leopard).
–without-ssl
Optional. Allows the build to proceed without ssl dependency tests.
–without-lxml
Prevents automatic build of lxml with static xml2 and xslt libraries
Note that you may run install.sh repeatedly for the same target so long
as you either use a different installation method or specify different
instance names. Installations to the same target will share the same Python
and egg/download cache.
Upgrade From Plone 2.5 or Non-Buildout 3.x
==========================================
See UPGRADING.txt
Dependencies
============
1) gcc
2) g++ (gcc-c++)
3) GNU make
4) GNU tar
5) gunzip and bunzip2
6) posix-compliant /bin/sh
Libraries and Utilities
=======================
Install libraries prior to running installer.
Development versions of some packages are required for headers. Debian/Ubuntu
package names are included below.
Required
——–
* Build Essentials (gcc, make)
build-essential
* libssl (SSL support)
libssl-dev
Recommended
———–
* zlib (GZ compression)
The Unified Installer will install this for you if necessary,
but system libraries are usually preferable.
zlib-dev
* libjpeg (jpeg support)
The Unified Installer will install this for you if necessary,
but system libraries are usually preferable.
libjpeg-dev
* readline (Python command-line history)
The Unified Installer will install this for you if necessary,
but system libraries are usually preferable.
libreadline5-dev readline-common
* wv (used to index Word documents)
wv
<http://wvware.sourceforge.net/>
May be installed after Plone install.
* poppler-utils (used to index PDFs)
poppler-utils
<http://poppler.freedesktop.org/>
May be installed after Plone install.
Install Location, Root Install
==============================
- Base install at /usr/local/Plone by default. This may be changed
with the –target installation option. If you change it, you'll also need
to change the paths below.
- Python installed at /usr/local/Plone/Python-2.6
- For ZEO Cluster
- ZEO cluster (server and 2 clients) installed and configured at /usr/local/Plone/zeocluster
Both –target and –name options may change this.
- Add-on Products folder at /usr/local/Plone/zeocluster/products.
(You may also install products via buildout.)
- Data.fs (ZODB) at /usr/local/Plone/zeocluster/var/filestorage
- adminPassword.txt at /usr/local/Plone/zeocluster/adminPassword.txt
- For Stand-Alone:
- Zope Instance installed and configured at /usr/local/Plone/zinstance
Both –target and –name options may change this.
- Add-on Products folder at /usr/local/Plone/zinstance/products
(You may also install products via buildout.)
- Data.fs (ZODB) at /usr/local/Plone/zinstance/var/filestorage
- adminPassword.txt at /usr/local/Plone/zinstance/adminPassword.txt
Install Location, Root-less Install
===================================
- Base install at $HOME/Plone, where $HOME is the user's home
directory, by default. This may be changed with the –target installation
option. If you change it, you'll also need to change the paths below.
- Python installed at $HOME/Plone/Python-2.6
- For ZEO Cluster
- ZEO cluster (server and 2 clients) installed and configured at $HOME/Plone/zeocluster
Both –target and –name options may change this.
- Add-on Products folder at $HOME/Plone/zeocluster/products
(You may also install products via buildout.)
- Data.fs (ZODB) at $HOME/Plone/zeocluster/var/filestorage
- adminPassword.txt at $HOME/Plone/zeocluster/adminPassword.txt
- For Stand-Alone:
- Zope Instance installed and configured at $HOME/Plone/zinstance
Both –target and –name options may change this.
- Add-on Products folder at $HOME/Plone/zinstance/products
(You may also install products via buildout.)
- Data.fs (ZODB) at $HOME/Plone/zinstance/var/filestorage
- adminPassword.txt at $HOME/zinstance/adminPassword.txt
=========================
The installer will compile Python, Zope, and key required libraries from
source. (Basic build tools and common libraries are required. See
"Dependencies" and "Recommended Libraries" below.)
PLEASE NOTE: You have the option to run the installation as root or a
normal user. There are serious security implications to this choice.
The non-root method produces an install that will run the Zope server
with the same privileges as the installing user. This is probably not an
acceptable security profile for a production server, but may be
acceptable for testing and development purposes.
The 'root' method produces an install that runs the Zope server as a
distinct user identity with minimal privileges (unless you add them).
Providing adequate security for a production server requires many more
steps, but this is a better starting point.
PLEASE NOTE: You have the option to install Plone as a standalone
(single-instance) setup or as a clustered (ZEO) setup.
The clustered (ZEO) setup will take advantage of multi-core CPUs and is
recommended for a production deployment, while the standalone method is
easier for a desktop-based development setup.
For more detail on both root/non-root and ZEO/standalone choices, see
"Installing on Linux / Unix / BSD":http://plone.org/documentation/manual/installing-plone/installing-on-linux-unix-bsd
in the Plone.Org documentation section.
For a super-user (root) installation
————————————
If you run the installation with root privileges, it will install
Python/Zope/Plone to /usr/local/Plone
[Darwin (OS X) Note: Under Darwin, the default installation is to
/Applications/Plone for the root install. Please replace /usr/local with
/Applications in the instructions below.]
A "plone" user will be added, and Zope will be configured to
run under that user id. You will need to start Zope as root or via sudo.
To install Plone 4.1 in a stand-alone (single Zope instance) configuration:
PLEASE NOTE: You have the option to run the installation as root or a
normal user. There are serious security implications to this choice.
The non-root method produces an install that will run the Zope server
with the same privileges as the installing user. This is probably not an
acceptable security profile for a production server, but may be
acceptable for testing and development purposes.
The 'root' method produces an install that runs the Zope server as a
distinct user identity with minimal privileges (unless you add them).
Providing adequate security for a production server requires many more
steps, but this is a better starting point.
PLEASE NOTE: You have the option to install Plone as a standalone
(single-instance) setup or as a clustered (ZEO) setup.
The clustered (ZEO) setup will take advantage of multi-core CPUs and is
recommended for a production deployment, while the standalone method is
easier for a desktop-based development setup.
For more detail on both root/non-root and ZEO/standalone choices, see
"Installing on Linux / Unix / BSD":http://plone.org/documentation/manual/installing-plone/installing-on-linux-unix-bsd
in the Plone.Org documentation section.
For a super-user (root) installation
————————————
If you run the installation with root privileges, it will install
Python/Zope/Plone to /usr/local/Plone
[Darwin (OS X) Note: Under Darwin, the default installation is to
/Applications/Plone for the root install. Please replace /usr/local with
/Applications in the instructions below.]
A "plone" user will be added, and Zope will be configured to
run under that user id. You will need to start Zope as root or via sudo.
To install Plone 4.1 in a stand-alone (single Zope instance) configuration:
* cd to the installer directory and issue the following command:
>> sudo ./install.sh standalone (or `su; ./install.sh standalone` on a sudo-less system)
To install Plone 4.1 in a ZEO Cluster (ZEO server, 2 clients) configuration:
* cd to the installer directory and issue the following command:
>> sudo ./install.sh zeo (or `su; ./install.sh zeo` on a sudo-less system)
For a non-super-user (rootless) installation
——————————————–
If you run the installation while logged in as a normal (non-root) user,
Python/Zope/Plone will be built at $HOME/Plone (the user's home
directory, Plone subdirectory). You will need to start Zope using
the user identity used for the build, and it will run with the
privileges of that user.
To install Plone 4.1 in a stand-alone (single Zope instance) configuration:
* cd to the installer directory and issue the following command:
>> ./install.sh standalone
To install Plone 4.1 in a ZEO Cluster (ZEO server, 2 clients) configuration:
* cd to the installer directory and issue the following command:
>> ./install.sh zeo
Installation Options
====================
Usage: [sudo] install.sh [options] standalone|zeo
Install methods available:
standalone - install standalone zope instance
zeo - install zeo cluster
Use sudo (or run as root) for root install.
Options:
–target=pathname
Use to specify top-level path for installs. Plone instances
and Python will be built inside this directory.
Default is /usr/local/Plone for root install,
$HOME/Plone for non-root.
PLEASE NOTE: Your pathname should not include spaces.
–instance=instance-name
Use to specify the name of the operating instance to be created.
This will be created inside the target directory.
Default is 'zinstance' for standalone, 'zeocluster' for ZEO.
–clients=client-count
Use with the "zeo" install method to specify the number of Zope
clients you wish to create. Default is 2.
–user=user-name In a root install, sets the effective user for running the
instance. Default is 'plone'. Ignored for non-root installs. You should always
use the same user within a given target.
–with-python=/full/path/to/python2.6
If you have an already built Python that's adequate to run
Zope / Plone, you may specify it here.
virtualenv will be used to isolate the copy used for the install.
The specified Python will need to have been built with support
for libz and libjpeg and include the Python Imaging Library.
–password=InstancePassword
If not specified, a random password will be generated.
–libz=(auto|yes|no)
Overrides the automatic determination of whether and where to
install the libz compression library.
–libjpeg=(auto|yes|no)
Overrides the automatic determination of whether and where to
install the libjpeg JPEG library.
–readline=(auto|yes|no)
Optional. Installs a local readline library. Only necessary
on platforms with odd libraries (like OS X Leopard).
–without-ssl
Optional. Allows the build to proceed without ssl dependency tests.
–without-lxml
Prevents automatic build of lxml with static xml2 and xslt libraries
Note that you may run install.sh repeatedly for the same target so long
as you either use a different installation method or specify different
instance names. Installations to the same target will share the same Python
and egg/download cache.
Upgrade From Plone 2.5 or Non-Buildout 3.x
==========================================
See UPGRADING.txt
Dependencies
============
1) gcc
2) g++ (gcc-c++)
3) GNU make
4) GNU tar
5) gunzip and bunzip2
6) posix-compliant /bin/sh
Libraries and Utilities
=======================
Install libraries prior to running installer.
Development versions of some packages are required for headers. Debian/Ubuntu
package names are included below.
Required
——–
* Build Essentials (gcc, make)
build-essential
* libssl (SSL support)
libssl-dev
Recommended
———–
* zlib (GZ compression)
The Unified Installer will install this for you if necessary,
but system libraries are usually preferable.
zlib-dev
* libjpeg (jpeg support)
The Unified Installer will install this for you if necessary,
but system libraries are usually preferable.
libjpeg-dev
* readline (Python command-line history)
The Unified Installer will install this for you if necessary,
but system libraries are usually preferable.
libreadline5-dev readline-common
* wv (used to index Word documents)
wv
<http://wvware.sourceforge.net/>
May be installed after Plone install.
* poppler-utils (used to index PDFs)
poppler-utils
<http://poppler.freedesktop.org/>
May be installed after Plone install.
Install Location, Root Install
==============================
- Base install at /usr/local/Plone by default. This may be changed
with the –target installation option. If you change it, you'll also need
to change the paths below.
- Python installed at /usr/local/Plone/Python-2.6
- For ZEO Cluster
- ZEO cluster (server and 2 clients) installed and configured at /usr/local/Plone/zeocluster
Both –target and –name options may change this.
- Add-on Products folder at /usr/local/Plone/zeocluster/products.
(You may also install products via buildout.)
- Data.fs (ZODB) at /usr/local/Plone/zeocluster/var/filestorage
- adminPassword.txt at /usr/local/Plone/zeocluster/adminPassword.txt
- For Stand-Alone:
- Zope Instance installed and configured at /usr/local/Plone/zinstance
Both –target and –name options may change this.
- Add-on Products folder at /usr/local/Plone/zinstance/products
(You may also install products via buildout.)
- Data.fs (ZODB) at /usr/local/Plone/zinstance/var/filestorage
- adminPassword.txt at /usr/local/Plone/zinstance/adminPassword.txt
Install Location, Root-less Install
===================================
- Base install at $HOME/Plone, where $HOME is the user's home
directory, by default. This may be changed with the –target installation
option. If you change it, you'll also need to change the paths below.
- Python installed at $HOME/Plone/Python-2.6
- For ZEO Cluster
- ZEO cluster (server and 2 clients) installed and configured at $HOME/Plone/zeocluster
Both –target and –name options may change this.
- Add-on Products folder at $HOME/Plone/zeocluster/products
(You may also install products via buildout.)
- Data.fs (ZODB) at $HOME/Plone/zeocluster/var/filestorage
- adminPassword.txt at $HOME/Plone/zeocluster/adminPassword.txt
- For Stand-Alone:
- Zope Instance installed and configured at $HOME/Plone/zinstance
Both –target and –name options may change this.
- Add-on Products folder at $HOME/Plone/zinstance/products
(You may also install products via buildout.)
- Data.fs (ZODB) at $HOME/Plone/zinstance/var/filestorage
- adminPassword.txt at $HOME/zinstance/adminPassword.txt