You need to install all the requirements corresponding to your operating system:
These are all required. If they are not installed, you won’t be able to install Silva.
To set up a production or development environment we recommend you do a SVN check out of the Buildout located in the Infrae SVN.
This will let you track your changes, and let you easily upgrade your Silva instance at a later date.
First you need to install Setuptools which is needed to install ZopeSkel. On Unix systems, this can be installed through your operating system package manager, for example on Ubuntu / Debian systems, you can do:
$ sudo apt-get install python-setuptools
Under Mac OS X, you can use MacPorts:
$ sudo port install py-setuptools
Otherwise you can install Setuptools manually by downloading the ez_setup script from http://peak.telecommunity.com/dist/ez_setup.py and then running it with the python version you want to use. For example under Unix:
$ cd /tmp $ wget http://peak.telecommunity.com/dist/ez_setup.py $ sudo python2.6 ez_setup.py
$ sudo easy_install-2.6 -U ZopeSkel
If you are using Mac OS X, you can use the option -s to specify a installation directory for scripts installed with a package. By default easy_install install all packages scripts in the same directory as Python, which is hidden inside a framework directory on Mac OS X. By specifying -s /opt/local/bin scripts are going to be installed in the same directory as the MacPorts software:
$ sudo easy_install-2.6 -s /opt/local/bin -U ZopeSkel
This installation step can take a while. easy_install will download some Python packages from external software repositories like sourceforge.net. It could be that one of these servers is temporarily unavailable. In that case you will get a connection timeout error, but you can try it again, until the command succeeds.
The ZopeSkel package installs a script called paster on your system. This can be used to install several CMS products including Silva. You can list all available products like this:
$ paster create --list-templates
Paster will print a list of templates, which should contain an entry called silva_buildout.
You can now create a Silva environment with the paster script. First go to a directory where you want to install Silva, then run the paster script with the following arguments:
$ paster create -t silva_buildout
Paster will ask you the following questions:
Enter project name
This is the name of your project, a directory with this name will be created to install the Silva instance in.
Path to an existing Zope 2 setup, leave this blank to download and create a new one.
Choose to install the stable version of Silva.
The name of the user to access and administrate the site.
A password for the user mentioned above. You must fill in something here, otherwise you will not be able to log in.
HTTP Port number on which the server will run.
Debug mode is useful for tracking down problems when developing. For a simple test deployment we recommend to turn it off.
Again, really only useful in a development context.
After replying to those questions, paster will generate a Silva environment in the project name directory.
Now that you have a Silva project environment, you can run the Buildout script to install Silva:
$ cd 'project name' $ python2.6 bootstrap.py $ ./bin/buildout
As result, the command bin/paster will be created. It will let you start and use Silva. See: Starting your Zope instance and creating a Silva site.
For production deployment or development we recommend you to install Silva by getting it from the Infrae subversion.
You need to install Subversion if it’s not already installed on your system.
There are different buildout SVN trees for different Silva versions. An SVN tag corresponds to a specific release of Silva, the tag repository is located here:
We highly recommend to use tags for production websites.
The development branches of Silva versions are located in in the branch repository``:
For the latest development version of Silva go to the trunk repository:
All buildout trees work the same way.
Pay close attention to how your SVN is configured. Especially the global-ignores section of you SVN config file. For more information see svn-configuration.
Run the following command to fetch files from SVN:
$ svn co https://svn.infrae.com/buildout/silva/tag/Silva-2.3 Silva
You can consult the README.txt file in the newly created Silva directory which contains additional information for the specific Silva version.
The Silva directory will be referenced as your Buildout tree from now on.
First you need to bootstrap your Buildout directory, and create a configuration file. You can create a new configuration as an extension of one of the available profiles located in the profiles sub-directory of your Buildout tree. Below we will use the simple-instance.cfg profile:
$ python2.6 bootstrap.py --buildout-profile profiles/simple-instance.cfg
Running this command creates essential files, most importantly one called buildout.cfg. The buildout.cfg file is a default Buildout configuration file. It controls what you want installed, and how. To extend your buildout see Extending and customising your installation with Buildout.
After generating the buildout files, run the installation:
When finished the command bin/instance will be available. It will let you start and use Silva: Starting your Zope instance and creating a Silva site.
The following profiles are available in the profiles directory:
Setup Silva in development mode. Debug options are activated by default, and some extra development tools are installed.
Recommanded profile for a production instance.
Base profile for a ZEO setup. This installs a ZEO server and a ZEO client instead of a simple instance. Refer to Zope Enterprise Object Setup for more details about that profile.
You can read more about the following sections to customize your setup:
The generic procedure to upgrade a Silva site is:
You cannot upgrade only one instance of Silva inside a Zope instance to a specific version. All Silva sites in a Zope instance run the same version of Silva (which is the one installed on the file-system).
Downgrade of versions is not supported. After you upgrade a Silva site, the only way to get back to the old version you were running is to restore a backup.
To change the version of Silva your are running on the file-system:
if you have an SVN checkout, you can switch Silva versions by running svn switch, for instance to upgrade to the version 2.3.1:
$ cd Silva $ ./bin/instance stop $ svn switch https://svn.infrae.com/buildout/silva/tag/Silva-2.3.1 $ ./bin/buildout
if you made your own buildout profile that refers directly to the Silva Buildout configuration using buildout’s extends option be sure to update the URL used.
If you are using any specific extra and/or custom extensions with Silva, you should check that they are compatible with the version of Silva you want to upgrade to. Failing to test these extensions may break your site and cause the upgrade to fail.
As standard upgrade procedure, we recommend to first copy your site as a test site, and then do the upgrade procedure on the copy. After checking that everything on your site works, you can do the same procedure on your production site. This is especially recommended for upgrades that jump between versions, and for major releases of Silva.
Please refer to the specific upgrade notes for the version you are upgrading to.
It’s recommended to backup your data before attempting any upgrade operations.
If you changed your configuration files, or updated your buildout tree, you need to re-run buildout:
We highly recommend stopping your Zope instance(s) before running buildout.
A Buildout tree contains the following sub-directories:
Contains all generated scripts for using the installed software. This should contain start/stop scripts for your Zope/ZEO instance/server, maildrophost server.
Contains software components. When you re-run buildout to upgrade your tree this directory might be deleted. You should not make any changes inside it.
Directory that can contains additional Zope products to be used.
Contains default configuration profiles, that can be used or extended.
Contains all data created and used by the software. The var/filestorage dir contains the Zope database. For backing up your website This is the directory you want to backup.
var/log contains all the logs generated by Zope and Silva. You might want to install a tool like logrotate in order to rotate them and control their sizes.
Buildout downloads software in the eggs and download directory by default. When you use buildout multiple times on the same host it’s best to share those directories between other buildout trees, this prevents downloading duplicate packages and centralizes your packages.
In a network setup, it is even possible to share the download directory among different hosts using NFS or something similar.
To create a cache you need to create a .buildout directory in your home directory, which contains a default.cfg file. The content of this file is:
[buildout] eggs-directory = /path/to/your/cache/eggs download-cache = /path/to/your/cache/download download-directory = /path/to/your/cache/download
In this example I used a directory called cache located in /path/to/your directory. You will also see the directories eggs and download. You need to create these directories in your cache directory.
Please refer first to those sections in case of any problems or questions while running Buildout, or see the link below.