0009854: config even more separate for multi instance installations - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0009854	mantisbt	installation	public	2008-11-18 13:09	2009-06-26 12:02

Reporter	01	Assigned To	vboctor
Priority	normal	Severity	tweak	Reproducibility	N/A
Status	closed	Resolution	duplicate
Product Version	1.1.2

Summary	0009854: config even more separate for multi instance installations
Description	Hi mantis team, as we are going to use more often mantis as issue management system for us and our customers I came across the following point: I would like to have a mechanism like for typo3 where you can put ONE source package (ie ONE distribution) somewhere and then just link to this for every instance you like to have for each customer for example. In addition you have you config locally so that you really have it separated from the application itself. Please refer to addition information section for an example.
Additional Information	Let's suppose you want to provide a mantis installation to three of your customers - A,B and C. Then you may install mantis distribution in /opt/mantis and for each customer you just put into his home directory a link like for A: /home/A/public_html/mantis/mantis_src is a link to /opt/mantis In addition you are able to place the config in As home like /home/A/public_html/mantis/conf/config_inc.php And there you have three instances with just three config files and except for this you can be sure that they are identical as they all refer to the very same distribution.
Tags	No tags attached.

thraxisp 2008-11-18 13:21 reporter ~0019934	There is a mechanism to use an environment variable (MANTIS_CONFIG) to point to the configuration. Each virtual server would have to set this appropriately. I did do a customization to set configuration by server name as well. I can find a patch if needed.

01 2008-11-21 11:47 reporter ~0019972	ok. I will have a look at it and this is already a step ahead. but what about if you have 2 mantis installation for one vhost? i mean domain.tld/mantis1 and domain.tld/mantis2 - then again you would need to complete mantis directories... I think in the end I will investigate about a typo3-integration. then we'll have functionality and design and config separated. :->>

thraxisp 2008-11-21 11:59 reporter ~0019974	I think that Apache can do this by putting the appropriate 'SetEnv' command in the alias for the directory. I would need to look into it some more.

vboctor 2008-11-23 04:09 manager ~0019993	Currently, only the configuration file is controlled via the environmental variable. I think we need a solution where we can point to a folder that contains all customizations aspects like: config file. custom strings. custom functions. custom constants. attachments folder root or use database. plugins

tmatijas 2008-11-23 04:47 reporter ~0019995	Sound like these link contains the answer: http://www.mantisbt.org/bugs/view.php?id=8401

01 2008-11-24 04:42 reporter ~0020005	agreed. the other task is what I initially meant. but it seems that it is still patching the mantis distribution... I would prefer having it in. :-) and during conversation here it comes to my mind, that in additon to the "pure config" the layout could be customizable in a farm also... what brings me to the typo3-integration-idea. so, I suggest to close this isse here (as it can be seen as a duplicate of 8401) and I will reopen another that does not deal with configuration in a farm but with layout in a farm.