History: InstallTikiGForge
Preview of version: 4
by Xavier de Pedro. October'2004.
I'll explain how I did install Tiki (1.8.4) on a server with GForge, and also two more tiki sites using its multi-install capability. In my case, I installed them on http://ourproject.org (op.o), which offers free hosting for free projects (with copylefted content). So these steps can be followed easily there, and I guess that they are reproducible at any GForge'd server (version 3 or later).
We have to take into account some specificities of a GForged server:
- For a multitiki install, there is a slightly different procedure than the one described in RecipeMultitiki, on InstallVirtualHosting, because with GForge, there is no need of root access to touch any httpd.conf.
. - If we consider, for instance, a parent tiki site called "myproject" and installed at URL http://myproject.ourproject.org, the URL of the multitiki child sites (for instance, site1, site2...) are of the form:
- http://myproject.site1.ourproject.org ,
- http://myproject.site2.ourproject.org ...
(instead of the common names for virtual hosting:
http://site1.myproject.ourproject.org,
http://site2.myproject.ourproject.org, ...).
. - The op.o GForged server allows users to connect through SSH to execute commands, to the path (for a user called "userX"):
Copy to clipboard/var/lib/gforge/chroot/home/users/userX/
- And the project, called "myproject", is created at:
Copy to clipboard/var/lib/gforge/chroot/home/groups/myproject/
We'll assume that you already have an account at any Gforge'd server (such as op.o)
- Download Tiki to your local computer.
. - Open a SSH file transfer connection to the Gforge'd server
. - Upload the file containing tiki install, and follow the common procedures described under the file "install" for a common single tiki install on Unix, except that permissions to directories have to be set, as far as I know, as 777 (permission to read execute and write to other users and groups in the server), instead of 755 or 775, as reported in other places in tw.o.
.
(if no success, get more information from InstallTiki to solve the problem that may have risen). - So that once you have your base tiki up and running, you have to execute again the setup command from the base directory where you installed tiki in (in my case, under /var/lib/gforge/chroot/home/groups/myproject/htdocs/ ):
- Log in again (if needed) to your gforged server account, using a ssh enabled program (such as Putty for Linux or M$ Window$, or Secure Shell for non commercial users on M$ Window$)
You should be in your home directory, like
Copy to clipboard/var/lib/gforge/chroot/home/users/userX/ - Move to the directory of your project "myproject", and execute the command
Copy to clipboardcd ../.. cd /groups/myproject/htdocs/ ./setup.sh userX groupX 02777 site1 site2
where userX is the name of the user, and groupX is the name of the project (groupX=myproject)
(in a similar manner to what is explained in InstallVirtualHosting)
. - Log in again (if needed) to your gforged server account, using a ssh enabled program (such as Putty for Linux or M$ Window$, or Secure Shell for non commercial users on M$ Window$)
- The local.php file, is as:
Copy to clipboard
<?php $db_tiki='mysql'; $dbversion_tiki='1.8'; $host_tiki="localhost"; $user_tiki="user"; $pass_tiki="****"; if ($_SERVER["HTTP_HOST"] == "myproject.ourproject.org") { $dbs_tiki = 'ddbb0'; $tikidomain = ''; } elseif ($_SERVER["HTTP_HOST"] == "myproject.site1.ourproject.org") { $dbs_tiki = 'ddbb1'; $tikidomain = 'site1'; } elseif ($_SERVER["HTTP_HOST"] == "myproject.site2.ourproject.org") { $dbs_tiki = 'ddbb2'; $tikidomain = 'site2'; } elseif ($_SERVER["HTTP_HOST"] == "myproject.site3.ourproject.org") { $dbs_tiki = 'ddbb3'; $tikidomain = 'site3'; } else { // default case, your choice is to block or open to a default domain $dbs_tiki = 'myproject'; $tikidomain = ''; } ?>
(...)
NOTE: If you follow this same strcutre, watch out to use the "exterminator" functions from "Admin>SystemAdmin" in tiki menu, because you'll delet some necessary directories from the directory tree in the servedr, under the templates_c. Reported as a bug at sf.net
(to be continued; no more time right now 😕)