8
8
and the following configuration lines in your apache config file:
11
RewriteRule ^(.*/cgi-bin/bugzilla)/?$ $1/index.cgi [R]
12
RewriteRule ^(.*/bugzilla)/?$ $1/index.cgi [R] [L]
11
RewriteRule ^(.*/cgi-bin/bugzilla3)/?$ $1/index.cgi [R]
12
RewriteRule ^(.*/bugzilla3)/?$ $1/index.cgi [R] [L]
14
14
# Proper URI for cgi scripts
15
RewriteCond %{REQUEST_URI} ^/bugzilla/.*\.cgi
16
RewriteRule ^/bugzilla/(.*\.cgi.*) /cgi-bin/bugzilla/$1 [PT]
15
RewriteCond %{REQUEST_URI} ^/bugzilla3/.*\.cgi
16
RewriteRule ^/bugzilla3/(.*\.cgi.*) /cgi-bin/bugzilla3/$1 [PT]
18
18
The database is not purged when the package is purged.
20
About GraphViz and dependency graphs ("webdotbase", "webdotdir")
21
------------------------------------------------------------------------------
23
The "webdotbase" configuration paramter (/etc/bugzilla3/params) has
24
to be set to `/usr/bin/dot`. This parameter can be configured by Bugzilla's
25
"Parameters >> Dependency Graphs" too. The "webdotdir" configuration
26
parameter has to be set to the directory where `/webdot` sub-directory
27
exists. In our case it is `/var/lib/bugzilla3/data`. The "/webdot" directory
28
is sym-linked from `/usr/lib/cgi-bin/bugzilla3`. This is mandatory for
29
configuration simplificity. Images created by GraphViz (/usr/bin/dot) are
30
stored in the `/webdot` subdirectory. With the sym-link it's possible to
31
reference them by the URL "urlbase"/webdot/XXXX.png. Make sure your
32
HTTP server configuration follow sym-links in `/usr/lib/cgi-bin/bugzilla3`
34
For examples check the examples in `/usr/share/doc/bugzilla3/examples`.
20
36
About the "urlbase" setting
21
37
------------------------------------------------------------------------------
23
39
Whe bugzilla is installed for the first time, you have to edit the conffile
24
/etc/bugzilla/params and change the value of urlbase to something that makes
40
/etc/bugzilla3/params and change the value of urlbase to something that makes
25
41
sense according to your installation. For instance, you can set it to
26
'/cgi-bin/bugzilla/' if you don't use VirtualHosts.
42
'/cgi-bin/bugzilla3/' if you don't use VirtualHosts.
27
43
That parameter will be used by Bugzilla for building links in a lot of places,
28
44
so take care to its value.
46
How to set several VirtualHosts with this package
47
------------------------------------------------------------------------------
49
If you want to provide several virtual hosts of Bugzilla, you can achieve that
50
goal easily thanks to your Apache configuration.
52
You will need to enable the Apache mod_env module first:
56
Then, you have to prepare a configuration directory for your virtual
57
host. The simpliest way is to copy the one the package created:
59
Name this new configuration directory like that:
60
`/etc/bugzilla3/sites/host' where `host' is the name of your virtual host.
62
You have now to add a virtual host section in your Apache configuraiton file.
63
This can be achieved in different ways, depending on the kind of VirtualHost
66
This package comes with two virtual host examples, located under
67
`/usr/share/doc/bugzilla3/examples/'.
69
If you want a vritualhost that uses the same static files as the orginal
70
package, just use the example: `vh-basic.conf'.
72
If you'd rather have different static files for the virtual host, you can
73
use the other example: `vh-custom-static.conf'.
75
As you can see in those examples, two environment variables are provided for
77
- X_BUGZILLA_SITE which is the name of the virtual host, it is used to find
78
wich configuration directory to use: `/etc/bugzilla3/sites/X_BUGZILLA_SITE'.
79
- X_BUGZILLA_WEBPATH wich is the prefix to prepend to every static files in
82
When you are ok with the apache configuration, you can restart it and
83
test your virtual host.
85
If you want to have specific templates for a given virtual host, that's also
86
possible, just copy `/var/lib/bugzilla3/template' to
87
`/var/lib/bugzilla3/template-X_BUGZILLA_SITE' and apply your changes there.
88
Take care to preserve permissions when you copy the files.
90
At this time, you can set a different database for each virtual host,
91
customize templates for another or even share the same database... Everything
92
is possible with few effort.
94
Even though each bugzilla site will be updated with checksetup.pl, the params
95
file won't be updated. The only params file that is updated during the
96
postinst phase is the standard one: `/etc/bugzilla3/params'.
98
Thanks to Yann Dirson for the mod_env idea.
100
-- Raphael Bossek <bossekr@debian.org> Mon, 05 May 2008 13:07:36 +0200