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:

  1. Multitiki using domains: using different domain names (i.e.,, ...). or
  2. Multitiki using subdirectories: having your several tikis in subdirectories of the same domain (i.e. http://yourhost/site1/, http://yourhost/site2/, ...) .

There are some differences depending on the previous option, but there are three major requirements that must be satisfied in both cases:

1.1. Create a separate database for each url.

See an example of edited local.php file for multikis (either 'multitiki using domains' or 'multitiki using subdirectories') at Manual Installation.

1.2. Configure the server to host multiple Tikis

1.2.1. Multitiki using domains

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.

1.2.2. Multitiki using subdirectories

Add symlinks. See the instructions in Manual installation AND in MultiTiki Manual Installation for the time being (and/or improve this page).

1.3. Create the necessary directories within Tiki's main directory.

./ 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. 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.

1.4. Optionally, add .htaccess with rewrite rules

You optionally add some Apache Clean URLs for your tikis.

1.5. Sys admin tasks from the Console

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 root@server:/path/trunk# php console.php index:rebuild ...

Newer MultiTiki Utility Commands

Since Tiki 15 (??) you can use multitiki:list and multitiki:move to manage your multitiki domains.

For example:

List domains in the current Tiki
$ php console.php multitiki:list

List domains in another (local) Tiki
$ php console.php multitiki:list ../20.x

And then to preview moving one from 20.x to the current Tiki use:

Move a MultiTiki
$ php console.php multitiki:move ../20.x Will move: /home/auser/tiki/branches/20.x/db/ to /home/auser/tiki/branches/21.x/db/ Will move: /home/auser/tiki/branches/20.x/dump/ to /home/auser/tiki/branches/21.x/dump/ Will move: /home/auser/tiki/branches/20.x/img/wiki/ to /home/auser/tiki/branches/21.x/img/wiki/ Will move: /home/auser/tiki/branches/20.x/img/wiki_up/ to /home/auser/tiki/branches/21.x/img/wiki_up/ Will move: /home/auser/tiki/branches/20.x/img/trackers/ to /home/auser/tiki/branches/21.x/img/trackers/ Will move: /home/auser/tiki/branches/20.x/modules/cache/ to /home/auser/tiki/branches/21.x/modules/cache/ Will move: /home/auser/tiki/branches/20.x/temp/ to /home/auser/tiki/branches/21.x/temp/ Will move: /home/auser/tiki/branches/20.x/temp/cache/ to /home/auser/tiki/branches/21.x/temp/cache/ Will move: /home/auser/tiki/branches/20.x/temp/public/ to /home/auser/tiki/branches/21.x/temp/public/ Will move: /home/auser/tiki/branches/20.x/templates/ to /home/auser/tiki/branches/21.x/templates/ Will move: /home/auser/tiki/branches/20.x/themes/ to /home/auser/tiki/branches/21.x/themes/ Will move: /home/auser/tiki/branches/20.x/whelp/ to /home/auser/tiki/branches/21.x/whelp/ Will move: /home/auser/tiki/branches/20.x/mods/ to /home/auser/tiki/branches/21.x/mods/ Will move: /home/auser/tiki/branches/20.x/files/ to /home/auser/tiki/branches/21.x/files/ Will move: /home/auser/tiki/branches/20.x/tiki_tests/tests/ to /home/auser/tiki/branches/21.x/tiki_tests/tests/ 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 in the destination Tiki after the move as of 21.0

See Console

1.6. Other Installation Procedures for Multiple TikiWikis

See also

Related older pages


Multi-Tiki Multi Tiki MultiTiki 1.9 | MultiTiki Akira | MultiTiki Virtual Hosting Install | MultiTiki Recipe

History Source