Personal tools
You are here: Home Documentation Tutorials Installing Plone 3 with the Unified Installer Root or User Install?
Support

Get Help

Join our chat rooms or support forums if you have more specific questions.

Plone Training
Learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.
Find Plone training…
 
Document Actions

Root or User Install?

The cases for and against installation as the root user.

smcmahon

The Unified Installer is a kit for installing Zope and Plone from source on most Unix-like systems, including Linux, BSD, OS X and Solaris. This tutorial introduces its use and options.
Page 2 of 6.
The install.sh script for the Unified Installer may be run as root (typically via sudo) or as a normal user. Key differences are:


The root install:

  • Installs by default to /opt/Plone-3.0/;
  • Installs libz and libjpeg as system libraries;
  • Creates a "plone" user, sets this user as owner of the appropriate files, and configures Zope to run as the effective user "plone".

The normal (non-root) user install:

  • Installs by default to $HOME/Plone-3.0;
  • Installs libz and libjpeg as local libraries;
  • Is meant to be run by and under the effective user id of the installing user.

Why Choose root or normal?

Installing as root (or with root privileges via sudo) is the best choice for a production installation of Plone. Since this install runs under the user id of a user created specifically for this purpose, it should have a more controllable level of access to resources. It is a generally accepted "best practice" to run persistent processes (like Zope) as unique users with limited rights.

Installing as a normal user (perhaps with your own user identity) may be a good choice for a test or development instance. It makes it very easy to install and edit custom products without worrying about user rights or identities.

 

 
by smcmahon — last modified June 29, 2007 - 22:29 All content is copyright Plone Foundation and the individual contributors.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by