2 # With the introduction of a configurable index page using the
3 # template toolkit, Bugzilla's main index page is now index.cgi.
4 # Most web servers will allow you to use index.cgi as a directory
5 # index, and many come preconfigured that way, but if yours doesn't
6 # then you'll need an index.html file that provides redirection
7 # to index.cgi. Setting $index_html to 1 below will allow
8 # checksetup.pl to create one for you if it doesn't exist.
9 # NOTE: checksetup.pl will not replace an existing file, so if you
10 # wish to have checksetup.pl create one for you, you must
11 # make sure that index.html doesn't already exist
16 # For some optional functions of Bugzilla (such as the pretty-print patch
17 # viewer), we need the cvs binary to access files and revisions.
18 # Because it's possible that this program is not in your path, you can specify
19 # its location here. Please specify the full path to the executable.
20 $cvsbin = "/usr/bin/cvs";
25 # For some optional functions of Bugzilla (such as the pretty-print patch
26 # viewer), we need the interdiff binary to make diffs between two patches.
27 # Because it's possible that this program is not in your path, you can specify
28 # its location here. Please specify the full path to the executable.
34 # The interdiff feature needs diff, so we have to have that path.
35 # Please specify the directory name only; do not use trailing slash.
36 $diffpath = "/usr/bin";
40 # If you are using Apache as your web server, Bugzilla can create .htaccess
41 # files for you that will instruct Apache not to serve files that shouldn't
42 # be accessed from the web (like your local configuration data and non-cgi
43 # executable files). For this to work, the directory your Bugzilla
44 # installation is in must be within the jurisdiction of a <Directory> block
45 # in the httpd.conf file that has 'AllowOverride Limit' in it. If it has
46 # 'AllowOverride All' or other options with Limit, that's fine.
47 # (Older Apache installations may use an access.conf file to store these
48 # <Directory> blocks.)
49 # If this is set to 1, Bugzilla will create these files if they don't exist.
50 # If this is set to 0, Bugzilla will not create these files.
55 # This is the group your web server runs as.
56 # If you have a windows box, ignore this setting.
57 # If you do not have access to the group your web server runs under,
58 # set this to "". If you do set this to "", then your Bugzilla installation
59 # will be _VERY_ insecure, because some files will be world readable/writable,
60 # and so anyone who can get local access to your machine can do whatever they
61 # want. You should only have this set to "" if this is a testing installation
62 # and you cannot set this up any other way. YOU HAVE BEEN WARNED!
63 # If you set this to anything other than "", you will need to run checksetup.pl
64 # as root, or as a user who is a member of the specified group.
65 $webservergroup = "http";
70 # What SQL database to use. Default is mysql. List of supported databases
71 # can be obtained by listing Bugzilla/DB directory - every module corresponds
72 # to one supported database and the name corresponds to a driver name.
79 # How to access the SQL database:
81 $db_host = 'localhost'; # where is the database?
82 $db_name = 'bugzilla'; # name of the SQL database
83 $db_user = 'mysql'; # user to attach to the SQL database
85 # Sometimes the database server is running on a non-standard
86 # port. If that's the case for your database server, set this
87 # to the port number that your database server is running on.
88 # Setting this to 0 means "use the default port for my database
95 # Enter your database password here. It's normally advisable to specify
96 # a password for your bugzilla database user.
97 # If you use apostrophe (') or a backslash (\) in your password, you'll
98 # need to escape it by preceding it with a '\' character. (\') or (\)
99 # (Far simpler just not to use those characters.)
105 # MySQL Only: Enter a path to the unix socket for mysql. If this is
106 # blank, then mysql\'s compiled-in default will be used. You probably
113 # Should checksetup.pl try to verify that your database setup is correct?
114 # (with some combinations of database servers/Perl modules/moonphase this