Installing the Ubuntu packages

Packages and an Apt repository are provided for use with Ubuntu 12.04 LTS and Ubuntu 14.04 LTS

To install LabTrove and its dependencies perform the following actions:

Adding the LabTrove APT repository

LabTrove has two different APT repositories, stable and testing. It is recommended you use stable, as testing is based on the latest commit to the SVN trunk, so may on occasions have problems. Execute the following command, on a single line, at a terminal to add the stable APT repository:

$ echo "deb http://www.labtrove.org/repo/stable ./ #Labtrove stable" | sudo tee /etc/apt/sources.list.d/labtrove.list > /dev/null

Alternatively, if you want to preview functionality in the latest version, execute the following command:

$ echo "deb http://www.labtrove.org/repo/testing ./ #Labtrove testing" | sudo tee /etc/apt/sources.list.d/labtrove.list > /dev/null

Installing LabTrove

Execute the following commands at a terminal.

$ sudo apt-get update

$ sudo apt-get install labtrove

You may see a warning similar to this:

WARNING: The following packages cannot be authenticated!
  labtrove
Install these packages without verification [y/N]?

You can safely answer 'y'.

If you have not previously configured MySQL server, its configuration script will now require you to supply an admin (root) password.

Configuring LabTrove

After LabTrove and its dependencies have been installed the Debconf based configuration script will guide you through the setup process.

Depending on the configuration options you select during LabTrove setup, you will be asked some or all of the following questions:

Database (MySQL) Configuration

LabTrove needs to create a MySQL database, please enter the hostname of the MySQL server.

If you intend to use the MySQL server just installed on the local machine, accept the default answer 'localhost', otherwise provide the hostname.

Please enter the MySQL root password.

If you intend to use the MySQL server just installed on the local machine, provide the same password that you set during MySQL configuration.

Please provide a name for the MySQL database to be created.

This is the main database used by LabTrove to store your data. Unless you have a reason not to, accept the default value.

A MySQL user account will be created for the labtrove database, please provide a username.

Used internally by LabTrove to access the database. Unless you have a reason not to, accept the default value.

Please provide a password for the newly created MySQL user account.

Used internally by LabTrove to access the database. You should provide a strong password.

Authentication Mechanism

Select a user authentication mechanism.

OpenID

LDAP

Local user database

Shibboleth (requires manual configuration)

Select the authentication mechanism you wish to use.

OpenID

Users will be prompted to select an OpenID provider to authenticate against at log in.

Please select the default access level for new LabTrove users.

None - Users can log in but may not view or modify content without admin approval.

View (default) - Users can view posts but require authentication before adding a comment.

User - At this level users can create posts and also their own Notebook.

Editor - Can read everything in the Trove but can modify only their own posts.

Administrator - Users can edit Trove settings as well as any post.

LDAP

Please supply the URL of the LDAP server.

e.g. ldaps://adsldap.example.ac.uk

Please supply the username to bind as.

Leave blank for anonymous bind

Please supply the password to bind with.

Leave blank for anonymous bind

Please supply the scope (base DN) against which to run the LDAP search.

e.g. OU=User, DC=EXAMPLE, DC=AC,DC=UK

Please supply the name of the LDAP attribute to map to the LabTrove username (i.e. login).

e.g. cn

Please supply the name of the LDAP attribute that hold's the user's full name.

e.g. displayname

Please supply the name of the LDAP attribute that holds the user's email address.

e.g. email

Please supply the name of the LDAP attribute that holds the user's Distinguished Name.

e.g. distinguishedname

Local user database

Please supply a password for the local LabTrove 'Administrator' account.

Use this when logging in to the LabTrove web interface.

Subsequent users can be added via the LabTrove admin interface.

Shibboleth

Shibboleth authentication requires the installation of further software and configuration outside of the scope of the LabTrove configuration script. This is covered in Setting_up_LabTrove_as_a_Shibboleth_Service_Provider

Web Server (Apache) Configuration

Configure and enable an Apache VirtualHost for LabTrove?

Answer 'yes' to create and enable a new VirtualHost stanza in /etc/apache2/sites-* of the form:

        <VirtualHost *:80>
                ServerAdmin webmaster@localhost
                DocumentRoot /usr/share/labtrove/docs
                ServerName labtrove-test
                SetEnv LABTROVE_CONFIG /etc/labtrove/config.php
                php_value post_max_size 32M
                php_value upload_max_filesize 32M
                <Directory />
                        Options FollowSymLinks
                        AllowOverride None
                </Directory>
                <Directory /usr/share/labtrove>
                        Options Indexes FollowSymLinks MultiViews
                        AllowOverride All
                        Order allow,deny
                        allow from all
                </Directory>
        </VirtualHost>

ServerName to use for this VirtualHost.

(e.g. labtrove.mydomain.com) used in the VirtualHost entry above.

General

Please supply a short title for your LabTrove instance.

This will be displayed in the header of each page. e.g. 'My LabTrove'

Please supply a one line description of your LabTrove instance.

This will be displayed under the title in the header of each page. e.g. 'An out of the box instance of LabTrove'.

Subsequent Reconfiguration

The values supplied to the configuration script are stored in /etc/labtrove/config.php. You can change the configuration at any time by editing this file. It will not be overwritten by package updates.