User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:run_multiple_mantis_sites_on_one_installation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mantisbt:run_multiple_mantis_sites_on_one_installation [2011/02/11 03:26] – beautifyed Phileasmantisbt:run_multiple_mantis_sites_on_one_installation [2013/06/21 16:30] (current) dregad
Line 1: Line 1:
-How to serve multiple mantis installations on the **windows** platform with :+===== How to serve multiple mantis installations on the windows platform ===== 
 + 
 +with 
   - just one mantis installation   - just one mantis installation
   - one or more databases   - one or more databases
Line 16: Line 19:
 ==== Database ==== ==== Database ====
 This is a no-brainer, do what ever you like, combine the DB or use seperate ones, just have it reflected in the correct config file. This is a no-brainer, do what ever you like, combine the DB or use seperate ones, just have it reflected in the correct config file.
 +
  
 ==== Configuration ==== ==== Configuration ====
 The various Mantis installations should all point to the same directory, each having their own hostheaders. The various Mantis installations should all point to the same directory, each having their own hostheaders.
-Based upon the hostheaders the correct config file can be selected within the normal config_inc.php (see sample below).+Based upon the hostheaders the correct config file can be selected within the normal ''config_inc.php'' (see sample below).
 Configuration of each installation, remains the same. All is handled in a dedicated config file. Configuration of each installation, remains the same. All is handled in a dedicated config file.
  
Line 31: Line 35:
 you need to copy the default script to ''read_email_mantis1.php'' and ''read_email_mantis2.php''. you need to copy the default script to ''read_email_mantis1.php'' and ''read_email_mantis2.php''.
 So for each installation you now can run the script in isolation and still have the option to select the correct config. So for each installation you now can run the script in isolation and still have the option to select the correct config.
 +
  
 ==== Updating mantis ==== ==== Updating mantis ====
Line 39: Line 44:
 That is all That is all
  
 +===== Examples of Configuration =====
 +
 +==== config_inc.php ====
 So how would your ''config_inc.php'' look: So how would your ''config_inc.php'' look:
  
Line 69: Line 77:
 <?php <?php
 // * HTTP_HOST is used to determine the config file needed for webservices                  * // * HTTP_HOST is used to determine the config file needed for webservices                  *
-// * SCRIPT_NAME is used to determine the config file needed for commandline services       * +// * SCRIPT_NAME is used to determine the  
-$hostheader = $_SERVER['HTTP_HOST'];+ 
 +if (isset($_SERVER['HTTP_HOST'])) { 
 +    $hostheader = $_SERVER['HTTP_HOST']; 
 +}
 $mailscript = $_SERVER['SCRIPT_NAME']; $mailscript = $_SERVER['SCRIPT_NAME'];
  
Line 93: Line 104:
  
 The contents of ''config_mantis1.php'' and ''config_mantis2.php'' is the normal config for each individual installation of mantis. The contents of ''config_mantis1.php'' and ''config_mantis2.php'' is the normal config for each individual installation of mantis.
 +
 +
 +==== custom_strings_inc.php ====
 +There is one other area which needs to be addressed which is the reference within Mantis to ''custom_strings_inc.php''.
 +
 +In the current setup it is assumed that these would be the same for all instances running of that single install. This clearly is not de facto true.
 +Good news is that it is not a real issue anyway. This can be handled pretty easily, exactly in the same way as for the base config !!
 +
 +Just move your custom strings into an instance dependent file called ''custom_strings_mantis1.php'' and so on.
 +Then your ''custom_strings_inc.php'' would look like :
 +
 +<code php>
 +<?php
 +// ******************************************************************************************
 +// * *
 +// * HTTP_HOST is used to determine the config file needed for webservices *
 +// * SCRIPT_NAME is used to determine the config file needed for commandline services *
 +// * *
 +// ******************************************************************************************
 +if (isset($_SERVER['HTTP_HOST'])) {
 +    $hostheader = $_SERVER['HTTP_HOST'];
 +}
 +$mailscript = $_SERVER['SCRIPT_NAME'];
 +
 +switch ($hostheader) {
 +   case "mantis1.yourdomainl.com" :
 +      include('custom_strings_mantis1.php');
 +   break;
 +   case "mantis2.yourdomainl.com" :
 +      include('custom_strings_mantis2.php');
 +   break;
 +}
 +
 +switch ($mailscript){
 +   case "read_mail_mantis1.php" :
 +      include('custom_strings_mantis1.php');
 +   break;
 +   case "read_mail_mantis2.php" :
 +      include('custom_strings_mantis2.php');
 +   break;
 +}
 +</code>
 +
 +==== custom_constants_inc.php ====
 +The same applies for the custom_constants_inc.php
 +
 +
mantisbt/run_multiple_mantis_sites_on_one_installation.1297412804.txt.gz · Last modified: 2011/02/11 03:28 (external edit)

CC Attribution-Noncommercial-Share Alike 4.0 International Driven by DokuWiki