History: SourceForge Install

            This is a specific install page, for general information see: ((installation)).


^This page is outdated and would need a clean-up ^


Initial version of the page was taken from [http://hispascal.sourceforge.net/phpwiki-1.3.3/index.php/Adrian15SourceForgeTikiWikiInstall]

This is an explanation on the additional steps required to install Tikiwiki on a SourceForge hosted project page.  Specifically this solves a problem with Tiki automatically logging you out after one or two page clicks.  This is caused by the PHP session file not being created successfully.

!! Activate your project's MySQL database
Please Read all of the documentation provided by SourceForge for setting up your project database.  It is provided here only for convenience.

# Go to your project admin page, select Database Admin.
# Click on 'create' and Sourceforge will make a DB with the same name as your project. It makes DB's about once an hour so you might have to wait before it says active. The username will also be your project name.
# Change the password to your liking and hit update. Once again, wait until it goes through the queue.
# This page will tell you the host, user, and database names

!! Tiki Modifications
These instructions assume that you have installed Tiki at: /home/groups/n/na/name/htdocs/tiki/

-=tiki/db/tiki-db.php=-
Edit /home/groups/n/na/name/htdocs/tiki/db/tiki-db.php, you must add the init_set line and edit the file according to the following lines:

{CODE()}
// Database connection for the tiki system
ini_set('include_path', '.:/usr/local/lib/php');
require_once('DB.php');
$host_tiki = 'mysql.sourceforge.net';
$user_tiki = 'projectname';
$pass_tiki = 'yourpassword';
$dbs_tiki = 'projectname';
{CODE}

-=tiki/sessions/=-
Create the following directory for PHP session files to be stored:

{CODE()}
mkdir /home/groups/n/na/name/htdocs/tiki/sessions
{CODE}

and set its permissions so that it can be written to by PHP

{CODE()}
chmod 766 /home/groups/n/na/name/htdocs/tiki/sessions
{CODE}

-=tiki/tiki-setup.php=-
after the line:

{CODE()}
$tiki_timer ->start();
{CODE}

add the following lines:

{CODE()}
ini_set("memory_limit", "16M");
session_save_path("/home/groups/n/na/name/htdocs/tiki/sessions");
{CODE}

!! Alternative setup 

-= Create database as explained above =-

That part of the explanation above is sourceforge specific. There is no other way to make the database.
Ofcourse, you'd need to run the sql script as described in the documentation manually using the project
shell servers.

{CODE()}
cd /home/groups/p/pr/projectname/htdocs/tiki/db
mysql -u projectname -h mysql projectname -p < tiki.sql
{CODE}

You will be prompted for your password, which you will supply.

The next step is to indeed change the tiki/db/tiki-db.php file. But only alter 4 lines

{CODE()}
// Database connection for the tiki system
require_once('DB.php');
$host_tiki = 'mysql'; // the mysql database is only accessible from sourceforge servers themselves
$user_tiki = 'projectname';
$pass_tiki = 'yourpassword';
$dbs_tiki = 'projectname';
{CODE}

-= Sessions =-

As an alternative setup procedure you can make the directory for sessions (it does not have to
be in the htdocs directory) and make sure that you can read/write to that directory using the 
nobody user. (ie: chmod 766 /home/groups/n/na/name/offsite/sessions).

-= Create a .htaccess file =-

Add a __.htaccess__ file to your project's htdocs directory. 

{CODE()}
cd /home/groups/n/na/name/htdocs
pico .htaccess
{CODE}

Add 3 lines to this file.

{CODE()}
php_value memory_limit "16M"
php_value session.save_path "/home/groups/n/na/name/offsite/sessions"
php_value include_path ".:/usr/local/lib/php:/home/groups/n/na/name/offsite"
{CODE}

Make of course sure that the n, na, name and offsite directory are the ones specific to your project.

__memory_limit & session.save_path__
This is the alternative to the above mentioned changes to tiki/tiki-setup.php

{CODE()}
ini_set("memory_limit", "16M");
session_save_path("/home/groups/n/na/name/htdocs/tiki/sessions");
{CODE}

Those lines need no longer to be inserted into tiki/tiki-setup.php.

__include_path__

The first 2 directory's are part of the include path that was in the sourceforge php.ini.
Everything after it are the directories (absolute) that you want to include files from.
In my example I have included an 'offsite' directory out of the htdocs directory.

Make sure that those directories are correctly chmodded

{CODE()}
chmod 751 /home/groups/n/na/name/offsite
{CODE}

You can move the db directory into it for instance (not the contents, but the DIRECTORY with the contents).

-= Testing the altered tiki and new settings =-

If you are not sure, you can always create a test.php in the htdocs directory that is
chmodded with 755 and contains

{CODE()}
<?
    phpinfo();
?>
{CODE}

You then direct your browser to your project page (or url) with extended to it '/test.php'

For instance

^
 http://projectname.sourceforge.net/test.php
^

Then look for the settings in the local column and compare it to the master column.



!!Adding the SourceForge.net logo to your site
As you may know or not know, all SF hosted projects are required to have the SF logo somewhere on their website. For more information about why you have to do this, see this page: [https://sourceforge.net/apps/trac/sourceforge/wiki/Use%20of%20sflogo%20for%20statistics%20tracking]

You can use ((Site Identity)) to put this logo in your site footer.



!2009 test install
*This is to record steps to install Tiki on SourceForge

# [https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20database|Activate MySQL and create a database as per SourceForge instructions]
** You need to have a username, a password and a database
# [https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web|Upload Tiki files as per SourceForge instructions]
** This will take a while, as there is no SSH. You need to upload files one by one via SFTP (or Rsync)
# Modify (presumably) Tiki files for SF's environment
* https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web%20and%20developer%20web%20platform#PHPScriptSupport