This document is valid for the current version of Plone.

Command-Line Options

Some less commonly used Unified Installer options that may still be useful to you.

You may add the following options to your command line to more finely control your installation:

Use to specify top-level path for installs. Plone instances and Python will be built inside this directory.
In a root install, sets the effective user for running the instance. Default is 'plone'. Ignored for non-root installs.
If you have an already built Python that's adequate to run Zope/Plone, you may specify it here.
virtualenv will be used to create an isolated Python environment for the installation. Your system's site library will not be touched. Python 2.4 is required for Plone 3.x, Python 2.6 for Plone 4.
Your Python must meet the needs of Plone, and the installer will test it for zlib, libssl and xml support before building for it.
If not specified, a random password will be generated.
SSL (usually OpenSSL) development libraries are needed to build a Python that will support SSL and TLS. Without it, Plone will be unable to use TLS in SMTP. The Unified Installer will ordinarily stop if it can't find the SSL headers and libraries. Use this option to tell the installer that you know what you're doing, and wish to proceed without SSL.
lxml, a Python wrapper for libxml2 and libxslt, is not required for Plone 4.1. But it is needed by some popular addons like Unless you specify this flag, the installer will try to build lxml with static libxml2 and libxslt libraries. This may not work on all platforms.

Skip running bin/buildout. You should know what you're doing. The main use for this option is if you want to use the Unified Installer to put all the pieces together, then plug in your own buildout.cfg.

The Unified Installer will try and figure out whether or not you have the libz, libjpeg and readline libraries on your system. If you do, great; if not, the installer will try to build them in the lib/ subdirectory of your installation target and link to them directly. This may not be what you want. If not, use the following command-line options to tune the behavior.




to have this program determine whether or not you need the library installed. If needed, will be installed to $PLONE_HOME. This is the default behavior.
to force install to $PLONE_HOME (or $LOCAL_HOME) for static link -- even if a system copy of the library is available.
to force no installation of the library.