Or how to set up multiple Tikis on the same server with a single Tiki file set installation. For managing different Tiki installations (several copies of the same installation files) in the same or different servers, see Tiki Manager instead.
It is possible to have multiple Tikis on a single server and using a single copy of the installation file set. This can be done through:
There are some differences depending on the previous option, but there are three major requirements that must be satisfied in both cases:
See an example of edited local.php file for multikis (either 'multitiki using domains' or 'multitiki using subdirectories') at Manual Installation.
Typically, each Tiki will be accessed by a separate URL through Apache. Generally, the URLs are specified as virtual hosts — often in VirtualHost stanzas within Apache's configuration file. Remember to restart Apache after you have changed the configuration files. On Linux this is usually best done with the "apachectl" graceful command.
On shared hosting, you can use "parked a domain" to have extra domains pointing to the same TikiWiki installation.
./setup.sh apache apache 02755 domain1 domain2 domain3
Create the directories manually for Windows hosting.
It is possible to add additional tikis after you have installed a single Tiki. However, with the exception of the case in the following paragraph, you will have to manually create the needed directories. If you are hosting on a Unix system, you will also need to manually set the ownership and permissions.
http://tikiwiki.org/tiki-index.php?page=RecipeMultiTiki has a detailed recipe tested under ))RedHat((, version 8 and version 9 and Yellow Dog Linux, version 3.0. Root access to the Linux machine is required for this approach. If you follow the instructions exactly, there is a Python script you can use to add additional Tikis later.
There are a few minor problems that crop up with this approach. The admins for the various tikis have the ability to overwrite each others changes to the css. Ordinary. users with the same login names on different tikis would also be able to overwrite each other's changes to css files. Finally, you must use Apache's mod_rewrite if you want the different Tikis to have their own favicons.
You optionally add some Apache Clean URLs for your tikis.
Since Tiki11, you can rebuild the Search Index and many other sys admin tasks from the command line also for Multitiki setups. And Since Tiki12.3, you can also handle the Mail Queue and the Daily Reports. You can use commands like:
root@server:/path/trunk# php console.php index:rebuild --site=site1.example.com root@server:/path/trunk# php console.php index:rebuild --site=site2.example.com ...
Since Tiki 15 (??) you can use multitiki:list and multitiki:move to manage your multitiki domains.
$ php console.php multitiki:list example.com other.example.com
$ php console.php multitiki:list ../20.x staging.example.com
And then to preview moving one from 20.x to the current Tiki use:
$ php console.php multitiki:move staging.example.com ../20.x Will move: /home/auser/tiki/branches/20.x/db/staging.example.com to /home/auser/tiki/branches/21.x/db/staging.example.com Will move: /home/auser/tiki/branches/20.x/dump/staging.example.com to /home/auser/tiki/branches/21.x/dump/staging.example.com Will move: /home/auser/tiki/branches/20.x/img/wiki/staging.example.com to /home/auser/tiki/branches/21.x/img/wiki/staging.example.com Will move: /home/auser/tiki/branches/20.x/img/wiki_up/staging.example.com to /home/auser/tiki/branches/21.x/img/wiki_up/staging.example.com Will move: /home/auser/tiki/branches/20.x/img/trackers/staging.example.com to /home/auser/tiki/branches/21.x/img/trackers/staging.example.com Will move: /home/auser/tiki/branches/20.x/modules/cache/staging.example.com to /home/auser/tiki/branches/21.x/modules/cache/staging.example.com Will move: /home/auser/tiki/branches/20.x/temp/staging.example.com to /home/auser/tiki/branches/21.x/temp/staging.example.com Will move: /home/auser/tiki/branches/20.x/temp/cache/staging.example.com to /home/auser/tiki/branches/21.x/temp/cache/example.com Will move: /home/auser/tiki/branches/20.x/temp/public/example.com to /home/auser/tiki/branches/21.x/temp/public/staging.example.com Will move: /home/auser/tiki/branches/20.x/templates/staging.example.com to /home/auser/tiki/branches/21.x/templates/staging.example.com Will move: /home/auser/tiki/branches/20.x/themes/staging.example.com to /home/auser/tiki/branches/21.x/themes/staging.example.com Will move: /home/auser/tiki/branches/20.x/whelp/staging.example.com to /home/auser/tiki/branches/21.x/whelp/staging.example.com Will move: /home/auser/tiki/branches/20.x/mods/staging.example.com to /home/auser/tiki/branches/21.x/mods/staging.example.com Will move: /home/auser/tiki/branches/20.x/files/staging.example.com to /home/auser/tiki/branches/21.x/files/staging.example.com Will move: /home/auser/tiki/branches/20.x/tiki_tests/tests/staging.example.com to /home/auser/tiki/branches/21.x/tiki_tests/tests/staging.example.com Use --confirm to perform moves
Then run the same command again with --confirm at the end to actually perform the move.
Note: You will need to then run
sh setup.sh in the destination Tiki after the move as of 21.0