diff options
author | Gervase Markham <gerv@gerv.net> | 2014-12-05 22:52:48 +0100 |
---|---|---|
committer | Dylan William Hardison <dylan@hardison.net> | 2014-12-05 23:01:30 +0100 |
commit | d41a0a76217ebbfd18807128e8bd552d5276e87a (patch) | |
tree | d99e4d9f43a2e0ffb693da447d2061e8985680a6 /docs/en/rst/installing/multiple-bugzillas.rst | |
parent | f9e9cf2597bb5e2780a16c0191400998a595fa2b (diff) | |
download | bugzilla-d41a0a76217ebbfd18807128e8bd552d5276e87a.tar.gz bugzilla-d41a0a76217ebbfd18807128e8bd552d5276e87a.tar.xz |
Bug 1067416 - reorganize and update Bugzilla docs
Diffstat (limited to 'docs/en/rst/installing/multiple-bugzillas.rst')
-rw-r--r-- | docs/en/rst/installing/multiple-bugzillas.rst | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/docs/en/rst/installing/multiple-bugzillas.rst b/docs/en/rst/installing/multiple-bugzillas.rst new file mode 100644 index 000000000..1e2d7951f --- /dev/null +++ b/docs/en/rst/installing/multiple-bugzillas.rst @@ -0,0 +1,41 @@ +.. _multiple-bz-dbs: + +One Installation, Multiple Instances +#################################### + +This is a somewhat specialist feature; if you don't know whether you need it, +you don't. It is useful to admins who want to run many separate instances of +Bugzilla from a single installed codebase. + +This is possible by using the ``PROJECT`` environment variable. When accessed, +Bugzilla checks for the existence of this variable, and if present, uses +its value to check for an alternative configuration file named +:file:`localconfig.<PROJECT>` in the same location as +the default one (:file:`localconfig`). It also checks for +customized templates in a directory named +:file:`<PROJECT>` in the same location as the +default one (:file:`template/<langcode>`). By default +this is :file:`template/en/default` so ``PROJECT``'s templates +would be located at :file:`template/en/PROJECT`. + +To set up an alternate installation, just export ``PROJECT=foo`` before +running :command:`checksetup.pl` for the first time. It will +result in a file called :file:`localconfig.foo` instead of +:file:`localconfig`. Edit this file as described above, with +reference to a new database, and re-run :command:`checksetup.pl` +to populate it. That's all. + +Now you have to configure the web server to pass this environment +variable when accessed via an alternate URL, such as virtual host for +instance. The following is an example of how you could do it in Apache, +other Webservers may differ. + +.. code-block:: apache + + <VirtualHost 12.34.56.78:80> + ServerName bugzilla.example.com + SetEnv PROJECT foo + </VirtualHost> + +Don't forget to also export this variable before accessing Bugzilla +by other means, such as repeating tasks like those above. |