This file is indexed.

/usr/share/doc/mantis/README.MultipleInstances is in mantis 1.2.18-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
Multiple Instances of Mantis
----------------------------

Radek Antoniuk has requested support for multiple instances of Mantis on a 
single system to be in the Debian Package. This is useful for e.g. Webhosting
Companies who would like to offer Mantis as a pre-installed software package
for their customers. This README is provided to to help with setting this up,
as it can't be included as a standard-feature in the Debian package.

1. Introduction
Having multiple instances of mantis is all about having a unique configuration
and a unique database for every mantis instance. This can be archeived by 
several different approaches:

* Via <Location> and php_prepend_file ability of apache, but this assumes, 
  that the user is using mod_php.
* Via a special mantis configuration file which decides on the base of the
  $SERVER_NAME

The latter is the one, which i will describe in the following.

2. Preparations
In order for our approach to work we will have to care for some things:

- setup a strucuture for instance configuration files under /etc/mantis
- setup a 'dispatcher' which loads the appropriate config file or a default one

2.1 Setting up a structure under /etc/mantis
It is up to you how you want to organize your site configurations. 
In this example we'll use a sub-directory sites/ which will contain all site
configuration. More important is how the files will be named.
They must contain the domain name, under which the instance will and should
run.

 # mkdir /etc/mantis/sites
 # chown www-data.www-data /etc/mantis/sites

Also you may want to create a default.php in /etc/mantis/sites, which 
will be sourced if no site can be determined.

2.2 Setup a dispatcher 
Now you need a configuration dispatcher. This package already contains an 
example, but it is wise to customize it, as it is really just an example,
without too much error checking.

See /usr/share/doc/mantis/examples/site_dispatcher.php.sample

You will have to copy it to the default configuration location of mantis, 
which is: /etc/mantis/config_inc.php .

3. Setup configurations
Now you will have to setup configurations for different sites. You can skip
this step for now, but you will at least have to configure a default instance,
the one that is sourced if no site is found.

4. Setup database and mantis
In every instance call the install.php which will setup the database.

These instruction inside of this file are by no means perfect. 
It isn't meant to be. It is a guideline for you to get it up and running by
yourself and you will need to improve parts of it for your needs. But it would
be nice if you would share your knowledge with others by sending me your
comments, critisms and improvements / enhancements, so that i can integrate
them into this package.

For more information:
http://www.mantisbt.org/wiki/doku.php/mantisbt:run_multiple_mantis_sites_on_one_installation?s=multiple%20instances



 -- Silvia Alvarez <sils@powered-by-linux.com>, Tue, 10 May 2011 19:33:43 +0200
 -- Patrick Schoenfeld <schoenfeld@in-medias-res.com>  Mon, 18 Dec 2006 18:11:00 +0100