Difference between revisions of "Plone"

From ArchWiki
Jump to: navigation, search
m (See Also: url typo)
(Updated for recent AUR changes, removed deprecated initscripts references.)
Line 3: Line 3:
  
 
== Installation ==
 
== Installation ==
[[Pacman|Install]] package {{AUR|plone-zeo}} from the [[AUR]]. Please be aware, that the AUR package installs the Plone Unified Installer in {{Ic|/usr/src}}, which is then run by Pacman upon initial install. The Unified Installer compiles and installs the package in {{Ic|/opt/Plone}}. The package is mainly intended to provide a convenient way to quickly install and get up and running with Plone, as it handles the dependencies and bundles the init script and a systemd unit file.
+
[[Pacman|Install]] package {{AUR|plone}} from the [[AUR]]. Please be aware, that the AUR package installs the Plone Unified Installer in {{Ic|/opt/Plone-$pkgver-UnifiedInstaller}}, which is then run by Pacman upon initial install. The Unified Installer compiles and installs the package in {{Ic|/opt/plone}}. The package is mainly intended to provide a convenient way to quickly install and get up and running with Plone, as it handles the dependencies and bundles the init script and a systemd unit file.
  
Note, that Plone site version upgrades are not handled by [[Pacman]] using the AUR package, because the files in {{Ic|/opt/Plone}} are not managed by Pacman directly. (see below for instructions on how to upgrade a Plone site)
+
Note, that Plone site version upgrades are not handled by [[Pacman]] using the AUR package, because the files in {{Ic|/opt/plone}} are not managed by Pacman directly. (see below for instructions on how to upgrade a Plone site)
  
 
==== Manual Installation ====
 
==== Manual Installation ====
  
The official way to install Plone is by using the Unified Installer, which is also used by the {{AUR|plone-zeo}} package. Doing a manual install will give you additional options.
+
The official way to install Plone is by using the Unified Installer, which is also used by the {{AUR|plone}} package. Doing a manual install will give you additional options.
  
 
The following prerequisites need to be installed:
 
The following prerequisites need to be installed:
Line 24: Line 24:
 
  wget http://launchpad.net/plone/${pver:0:3}/$pver/+download/Plone-$pver-UnifiedInstaller.tgz
 
  wget http://launchpad.net/plone/${pver:0:3}/$pver/+download/Plone-$pver-UnifiedInstaller.tgz
 
  tar -xzf *UnifiedInstaller.tgz
 
  tar -xzf *UnifiedInstaller.tgz
  ./Plone-$pver-UnifiedInstaller/install.sh --target=/opt/Plone zeo
+
  ./Plone-$pkgver-UnifiedInstaller/install.sh --target=/opt/plone zeo
 
The installer provides informative messages as well as saving an {{Ic|install.log}} to help analyse potential problems.
 
The installer provides informative messages as well as saving an {{Ic|install.log}} to help analyse potential problems.
  
Line 30: Line 30:
  
 
Manually start the service with:
 
Manually start the service with:
  sudo -u plone /opt/Plone/zeocluster/bin/plonectl start
+
  sudo -u plone /opt/plone/zeocluster/bin/plonectl start
 
Then try the site on {{Ic|http://yoursite:8080}}
 
Then try the site on {{Ic|http://yoursite:8080}}
  
Use the displayed login password, which can also be found in {{Ic|/opt/Plone/zeocluster/adminPassword.txt}} The start page allows you to create an initial site, by filling in the name of the new site and choosing optional add-ons.
+
Use the displayed login password, which can also be found in {{Ic|/opt/plone/zeocluster/adminPassword.txt}} The start page allows you to create an initial site, by filling in the name of the new site and choosing optional add-ons.
  
 
Stop the service with:
 
Stop the service with:
  sudo -u plone /opt/Plone/zeocluster/bin/plonectl stop
+
  sudo -u plone /opt/plone/zeocluster/bin/plonectl stop
 
==== Using Systemd ====
 
==== Using Systemd ====
 
To enable the Plone service by default at start-up, run:
 
To enable the Plone service by default at start-up, run:
  systemctl enable plone
+
  systemctl enable plone-standalone.service
==== Using SysVinit ====
+
To enable the Plone service by default at start-up just add {{Ic|plone}} to the {{Ic|DAEMONS}} array in {{ic|/etc/rc.conf}}:
+
DAEMONS=(... plone)
+
 
== Customizing ==
 
== Customizing ==
To change ports, or to install add-ons and themes edit the file {{Ic|buildout.cfg}} at {{Ic|/opt/Plone/zeocluster}}.
+
To change ports, or to install add-ons and themes edit the file {{Ic|buildout.cfg}} at {{Ic|/opt/plone/zeocluster}}.
  
 
Apply the new settings by running:
 
Apply the new settings by running:
  cd /opt/Plone/zeocluster
+
  cd /opt/plone/zeocluster
 
  sudo -u plone bin/buildout  
 
  sudo -u plone bin/buildout  
 
== Upgrades ==
 
== Upgrades ==
Line 54: Line 51:
 
  base.cfg
 
  base.cfg
 
  # versions.cfg
 
  # versions.cfg
  http://dist.plone.org/release/4.2-latest/versions.cfg  
+
  http://dist.plone.org/release/4.3-latest/versions.cfg  
 
Then stop Plone and re-run buildout:
 
Then stop Plone and re-run buildout:
  cd /opt/Plone/zeocluster
+
  cd /opt/plone/zeocluster
 
  sudo -u plone bin/buildout   
 
  sudo -u plone bin/buildout   
 
Restart Plone and visit the Management Interface at (http://yoursite:8080). You will likely see a message prompting you to run Plone's migration script. Click the Upgrade button next to the site and the upgrade script will run.
 
Restart Plone and visit the Management Interface at (http://yoursite:8080). You will likely see a message prompting you to run Plone's migration script. Click the Upgrade button next to the site and the upgrade script will run.

Revision as of 15:15, 26 February 2014

Plone is a free and open source content management system built on top of the Zope application server written in Python. Plone can be used for all kinds of websites, including blogs, internet sites, webshops and intranets. The strengths of Plone are its flexible and adaptable workflow, very good security, extensibility, high usability and flexibility.

Installation

Install package ploneAUR from the AUR. Please be aware, that the AUR package installs the Plone Unified Installer in /opt/Plone-$pkgver-UnifiedInstaller, which is then run by Pacman upon initial install. The Unified Installer compiles and installs the package in /opt/plone. The package is mainly intended to provide a convenient way to quickly install and get up and running with Plone, as it handles the dependencies and bundles the init script and a systemd unit file.

Note, that Plone site version upgrades are not handled by Pacman using the AUR package, because the files in /opt/plone are not managed by Pacman directly. (see below for instructions on how to upgrade a Plone site)

Manual Installation

The official way to install Plone is by using the Unified Installer, which is also used by the ploneAUR package. Doing a manual install will give you additional options.

The following prerequisites need to be installed:

Download the latest installer from here and follow the Plone Install Guide

For example to install Plone for production use, using a ZEO server configuration do the following as root:

pacman -S base-devel libxml2 libxslt libjpeg-turbo openssl sudo
pver=4.2.1 # replace this with the latest version
wget http://launchpad.net/plone/${pver:0:3}/$pver/+download/Plone-$pver-UnifiedInstaller.tgz
tar -xzf *UnifiedInstaller.tgz
./Plone-$pkgver-UnifiedInstaller/install.sh --target=/opt/plone zeo

The installer provides informative messages as well as saving an install.log to help analyse potential problems.

Starting Plone

Manually start the service with:

sudo -u plone /opt/plone/zeocluster/bin/plonectl start

Then try the site on http://yoursite:8080

Use the displayed login password, which can also be found in /opt/plone/zeocluster/adminPassword.txt The start page allows you to create an initial site, by filling in the name of the new site and choosing optional add-ons.

Stop the service with:

sudo -u plone /opt/plone/zeocluster/bin/plonectl stop

Using Systemd

To enable the Plone service by default at start-up, run:

systemctl enable plone-standalone.service

Customizing

To change ports, or to install add-ons and themes edit the file buildout.cfg at /opt/plone/zeocluster.

Apply the new settings by running:

cd /opt/plone/zeocluster
sudo -u plone bin/buildout 

Upgrades

Upgrades are done in a similar way using buildout. This should be fairly straightforward, from one minor version to another. For example to upgrade to Plone 4.2.x do the following: In your buildout.cfg, comment out versions.cfg and uncomment the line pointing to dist.plone.org, so it looks like this:

extends = 
base.cfg
# versions.cfg
http://dist.plone.org/release/4.3-latest/versions.cfg 

Then stop Plone and re-run buildout:

cd /opt/plone/zeocluster
sudo -u plone bin/buildout  

Restart Plone and visit the Management Interface at (http://yoursite:8080). You will likely see a message prompting you to run Plone's migration script. Click the Upgrade button next to the site and the upgrade script will run.

For more information on upgrades, especially between major versions of Plone read the Upgrade Guide

See Also