Install Zenario from GitHub

You can get Zenario directly from our Github repository.

This is a free, quick and easy process, and once you've got your Zenario software checked out, it will allow you to update to new releases of Zenario easily.

How to install using GitHub

First, let's assume your website will be running under /var/www/mywebsite. You will need to make the directories public_html (for Zenario's main files), plus backup (for backups) and docstore (for storing documents). Like this:

cd /var/www/mywebsite
mkdir backup docstore
chmod 777 backup docstore
mkdir public_html

Your web server's DocumentRoot should be pointing to /var/www/mywebsite/public_html.

You will also need to make sure subversion is running on your server.

Change into public_html and get the files onto your server from GitHub. Then make a script executable (to update Zenario's file permissions) and run the script:

cd public_html
svn checkout . chmod 775 zenario/scripts/

Zenario's files should all now be present, and the permissions of key files should be writeable.

Make your database

You will need to prepare a MySQL database and get its connection parameters (not shown here as this will depend on your setup).

You will need to make note of:

  • the database hostname (often localhost but it can be different)
  • the database username for Zenario
  • the database password for that user.

Then, with your browser, to go to your website's main URL, where you should see the Zenario installer.

Run the installer, entering the details when prompted.

Updating when there's new Zenario software available

Note: Before updating your software, we strongly recommend you backup your database and files.

You can update your version to new releases of Zenario (when available) by using:

svn up .htaccess index.php robots.txt zenario

By specifying the list as described above, only the new core things will be updated, most of which is in the zenario directory, while files and directories containing custom things should be left alone. zenario_custom contains all of your customised layouts, skins, and possibly frameworks and modules if you write these yourself. cache, private and public directories are effectively caches and can be safely deleted or cleared out.

Having run the svn update, point your browser at your website, and log in as an administrator (or if already logged in, go to /admin in the URL).

You will be asked if you would like to apply updates to your database. You should apply the changes, and then you should be able to log in to your site as normal.