Tine 2.0 is currently only available trough our SVN repository. We have not created any downloadable packages so far. If you like to install Tine 2.0 on your own system, you need check out the data from our SVN repository first. You need to have a SVN client installed on your system. Any up-to-date linux distribution contains a command line SVN client by default.

[edit] Download Tine 2.0 and ExtJS from SVN

To checkout the source code of Tine 2.0 from our SVN repository, just execute the following commands in your webservers document root:

cd /webservers/documentroot
svn co https://officespot-cs.svn.sourceforge.net/svnroot/officespot-cs/trunk/tine20 tine20

cd tine20
svn co https://officespot-cs.svn.sourceforge.net/svnroot/officespot-cs/vendor/extjs/current ExtJS

[edit] Download Zend Framework from Zend.com

Download the latest release of the Zend Framework 1.5.x from http://framework.zend.com/download and extract the downloaded file in a temporary directory. Then copy the directory /temporary/path/ZendFramework-1.5.x/library/Zend into your PHP include path. If you are unsure about your include path, just copy /temporary/path/ZendFramework-1.5.x/library/Zend into the same directory where you checked out /webservers/documentroot/tine20/ initially. The tine20 directory already contains a Zend subdirectory. You can simply copy the /temporary/path/ZendFramework-1.5.x/library/Zend directory over the existing one.

[edit] preparing the database

Create a database for Tine 2.0.

[edit] editing the configuration file config.ini

Currently we are using the Zend Framework class Zend_Config_Ini, to read the different configuration parameters (for example the database access settings) from the configuration file. This file must be placed above the document root of your webserver. If your document root is at

/var/www/htdocs

then you need to place the config.ini file into

/var/www/config.ini

This way we can ensure, that this file is not directly accessible through the webserver from the outside.

The config.ini file has the following format:

[database]
; the hostname of the database server
host = hostname

; the name of the database
dbname = databasename

; the username used to authenticate against the database
username = databaseusername

; the password used to authenticate against the database
password = yourSecretPasswort

; optional table prefix. defaults to tine20_
;tableprefix = tine20_

[logger]
filename = /var/log/tine20.log
priority = 7
 
[mail]
smtpserver = mail.yourserver
ssl = tls
port = 25

[authentication]
backend = sql

[accounts]
backend = sql

[edit] call setup.php

After you have prepared the database and the config.ini just point your browser to http://yourwebserver/tine20/setup.php. If everything goes well, you will see a bunch of SQL statements and no error message.

[edit] login as admin

After running setup.php you can point your browser to http://yourwebserver/tine20/ and log into Tine 2.0 using the username "tine20admin" and the password "lars". Later we will improve the setup process to allow you to specify the initial username and password.

[edit] user registration

We added the possiblity for new users to register themselves. If this option is enabled (in the config.ini, more on this later), a new button appears in the login dialog. If you click on this button ("Register"), you have to type in your first- and lastname, email address and username. The dialog will suggest a username, based on the given first- and lastname.

At the end of the registration process an email will be send to the user. In this email he will find his username and password for the tine20 login screen. If the expire option is set (greater than 0), the user has to activate his account by clicking on the link in the email.

Here are the relevant config.ini options (with default values):

[registration]
active = 0
expires = 0
accountPrimaryGroup = Users
accountStatus = enabled
emailValidation = zend

• active -> is user registration enabled?
• expires -> 0: account never expires, greater than 0: hours till account is deactivated (it will be enabled again when the email activation is done)
• accountPrimaryGroup -> primary group name for the new account
• accountStatus -> enabled/disabled
• emailValidation -> zend/none/[regexp]?