Running the Unified Installer

Preparations

Crank up your platform's package manager and make sure you've got the following installed:

• gcc, the GNU Compiler Collection.
• g++, the C++ extensions for gcc.
• GNU make, the fundamental build-control tool.
• GNU tar. This is the version of tar on all Linux, BSD and OS X platforms, but not Solaris.
• bzip2 and gzip decompression packages. gzip is nearly standard; some platforms will require that bzip2 be installed.
  

Ideally, you should also have the libssl and readline libraries and development headers loaded (usually, the libssl-dev and readline-dev packages). These are not required, but add desirable functionality. libssl is required to use TLS with your mail server, which may be vital if it's not local. See the Unified Installer README.txt for details.

Now, choose a convenient working directory and unpack the .tar.gz archive (tarball) of the Unified Installer:

tar zxf Plone-VERSION-UnifiedInstaller.tar.gz

Then change into the newly created directory:

cd Plone-VERSION-UnifiedInstaller

("VERSION-" will vary with release.)

Running install.sh

If you've chosen to install with root privileges, either su to root or precede these commands with sudo.

ZEO Installation:

./install.sh zeo

Stand-Alone Zope Installation:

./install.sh standalone

Then, sit back and watch the progress messages.

If the progress messages don't start, it will typically mean that a vital installation tool is missing. Use your package manager to install the tool, and try again.

If the installation succeeds, you'll see a set of instructions for starting your new Zope/Plone install. Make note of the password for the "admin" user. These instructions will also be available in README.txt file, and the pass word in "adminPassword.txt", in your new install.

If the installation should fail, don't panic. Make note of any error messages or diagnostics and, if you can't remedy the problem yourself, ask for help in the plone-setup mailing list or the #plone IRC channel. We'll need precise information about your platform and all possible diagnostic information to help. Also, make sure to check the Platform Notes section of the README.txt file included with the installer to see if there might be a work-around or special requirement note for your platform.

The install script creates a detailed log file, install.log, that may help diagnose an installation failure.

Checking your installation

If your installation succeeded, try starting it by following the instructions displayed at the end of the install process (or in the README.txt file in the install directory). Startup problems are uncommon, but do occasionally happen. The most common cause is that some other process has already claimed the 8080 port (or one or more of the 8100, 8080 and 8081 ports if you're using ZEO). You may wish to stop or kill the competing process if it's an old Zope/Plone installation. If not, you may reassign the ports used by your Plone installation by editing the buildout.cfg file and running bin/buildout to reassign ports.

If the start is successful, test your installation by opening a web browser and navigating to http://localhost:8080. (If you're testing on another machine, substitute your server host name for "localhost".)

You should see a Zope welcome message. A test Plone site should be available at http://localhost:8080/Plone, and the Zope Management Interface at http://localhost:8080/manage.

If Zope appears to be running, but you cannot connect, check to see if a firewall may be in place and blocking the connection.