Annotation of /puppet/modules/bugzilla/templates/localconfig


# If you are using Apache as your web server, Bugzilla can create .htaccess
# files for you that will instruct Apache not to serve files that shouldn't
# be accessed from the web browser (like your local configuration data and non-cgi
# executable files).  For this to work, the directory your Bugzilla
# installation is in must be within the jurisdiction of a <Directory> block
# in the httpd.conf file that has 'AllowOverride Limit' in it.  If it has
# 'AllowOverride All' or other options with Limit, that's fine.
# (Older Apache installations may use an access.conf file to store these
# <Directory> blocks.)
# If this is set to 1, Bugzilla will create these files if they don't exist.
# If this is set to 0, Bugzilla will not create these files.
$create_htaccess = 0;

# Usually, this is the group your web server runs as.
# If you have a Windows box, ignore this setting.
# If you have use_suexec switched on below, this is the group Apache switches
# to in order to run Bugzilla scripts.
# If you do not have access to the group your scripts will run under,
# set this to "". If you do set this to "", then your Bugzilla installation
# will be _VERY_ insecure, because some files will be world readable/writable,
# and so anyone who can get local access to your machine can do whatever they
# want. You should only have this set to "" if this is a testing installation
# and you cannot set this up any other way. YOU HAVE BEEN WARNED!
# If you set this to anything other than "", you will need to run checksetup.pl
# asroot, or as a user who is a member of the specified group.
$webservergroup = 'apache';

# Set this if Bugzilla runs in an Apache SuexecUserGroup environment.
# (If your web server runs control panel software (cPanel, Plesk or similar),
# or if your Bugzilla is to run in a shared hosting environment, then you are
# almost certainly in an Apache SuexecUserGroup environment.)
# If you have a Windows box, ignore this setting.
# If set to 0, Bugzilla will set file permissions as tightly as possible.
# If set to 1, Bugzilla will set file permissions so that it may work in an
# SuexecUserGroup environment. The difference is that static files (CSS,
# JavaScript and so on) will receive world read permissions.
$use_suexec = 0;

# What SQL database to use. Default is mysql. List of supported databases
# can be obtained by listing Bugzilla/DB directory - every module corresponds
# to one supported database and the name corresponds to a driver name.
$db_driver = 'pg';

# The DNS name of the host that the database server runs on.
$db_host = 'pgsql.mageia.org';

# The name of the database
$db_name = 'bugs';

# Who we connect to the database as.
$db_user = 'bugs';

# Enter your database password here. It's normally advisable to specify
# a password for your bugzilla database user.
# If you use apostrophe (') or a backslash (\) in your password, you'll
# need to escape it by preceding it with a '\' character. (\') or (\)
# (Far simpler just not to use those characters.)
$db_pass = 'bugs';

# Sometimes the database server is running on a non-standard port. If that's
# the case for your database server, set this to the port number that your
# database server is running on. Setting this to 0 means "use the default
# port for my database server."
$db_port = 0;

# MySQL Only: Enter a path to the unix socket for MySQL. If this is
# blank, then MySQL's compiled-in default will be used. You probably
# want that.
$db_sock = '';

# Should checksetup.pl try to verify that your database setup is correct?
# (with some combinations of database servers/Perl modules/moonphase this
# doesn't work)
$db_check = 1;

# With the introduction of a configurable index page using the
# template toolkit, Bugzilla's main index page is now index.cgi.
# Most web servers will allow you to use index.cgi as a directory
# index, and many come preconfigured that way, but if yours doesn't
# then you'll need an index.html file that provides redirection
# to index.cgi. Setting $index_html to 1 below will allow
# checksetup.pl to create one for you if it doesn't exist.
# NOTE: checksetup.pl will not replace an existing file, so if you
#       wish to have checksetup.pl create one for you, you must
#       make sure that index.html doesn't already exist
$index_html = 0;

# For some optional functions of Bugzilla (such as the pretty-print patch
# viewer), we need the cvs binary to access files and revisions.
# Because it's possible that this program is not in your path, you can specify
# its location here.  Please specify the full path to the executable.
$cvsbin = '/usr/bin/cvs';

# For some optional functions of Bugzilla (such as the pretty-print patch
# viewer), we need the interdiff binary to make diffs between two patches.
# Because it's possible that this program is not in your path, you can specify
# its location here.  Please specify the full path to the executable.
$interdiffbin = '/usr/bin/interdiff';

# The interdiff feature needs diff, so we have to have that path.
# Please specify the directory name only; do not use trailing slash.
$diffpath = '/usr/bin';

1	dmorgan	188
2			# If you are using Apache as your web server, Bugzilla can create .htaccess
3			# files for you that will instruct Apache not to serve files that shouldn't
4			# be accessed from the web browser (like your local configuration data and non-cgi
5			# executable files). For this to work, the directory your Bugzilla
6			# installation is in must be within the jurisdiction of a <Directory> block
7			# in the httpd.conf file that has 'AllowOverride Limit' in it. If it has
8			# 'AllowOverride All' or other options with Limit, that's fine.
9			# (Older Apache installations may use an access.conf file to store these
10			# <Directory> blocks.)
11			# If this is set to 1, Bugzilla will create these files if they don't exist.
12			# If this is set to 0, Bugzilla will not create these files.
13			$create_htaccess = 0;
14
15			# Usually, this is the group your web server runs as.
16			# If you have a Windows box, ignore this setting.
17			# If you have use_suexec switched on below, this is the group Apache switches
18			# to in order to run Bugzilla scripts.
19			# If you do not have access to the group your scripts will run under,
20			# set this to "". If you do set this to "", then your Bugzilla installation
21			# will be _VERY_ insecure, because some files will be world readable/writable,
22			# and so anyone who can get local access to your machine can do whatever they
23			# want. You should only have this set to "" if this is a testing installation
24			# and you cannot set this up any other way. YOU HAVE BEEN WARNED!
25			# If you set this to anything other than "", you will need to run checksetup.pl
26			# asroot, or as a user who is a member of the specified group.
27			$webservergroup = 'apache';
28
29			# Set this if Bugzilla runs in an Apache SuexecUserGroup environment.
30			# (If your web server runs control panel software (cPanel, Plesk or similar),
31			# or if your Bugzilla is to run in a shared hosting environment, then you are
32			# almost certainly in an Apache SuexecUserGroup environment.)
33			# If you have a Windows box, ignore this setting.
34			# If set to 0, Bugzilla will set file permissions as tightly as possible.
35			# If set to 1, Bugzilla will set file permissions so that it may work in an
36			# SuexecUserGroup environment. The difference is that static files (CSS,
37			# JavaScript and so on) will receive world read permissions.
38			$use_suexec = 0;
39
40			# What SQL database to use. Default is mysql. List of supported databases
41			# can be obtained by listing Bugzilla/DB directory - every module corresponds
42			# to one supported database and the name corresponds to a driver name.
43			$db_driver = 'pg';
44
45			# The DNS name of the host that the database server runs on.
46			$db_host = 'pgsql.mageia.org';
47
48			# The name of the database
49			$db_name = 'bugs';
50
51			# Who we connect to the database as.
52			$db_user = 'bugs';
53
54			# Enter your database password here. It's normally advisable to specify
55			# a password for your bugzilla database user.
56			# If you use apostrophe (') or a backslash (\) in your password, you'll
57			# need to escape it by preceding it with a '\' character. (\') or (\)
58			# (Far simpler just not to use those characters.)
59			$db_pass = 'bugs';
60
61			# Sometimes the database server is running on a non-standard port. If that's
62			# the case for your database server, set this to the port number that your
63			# database server is running on. Setting this to 0 means "use the default
64			# port for my database server."
65			$db_port = 0;
66
67			# MySQL Only: Enter a path to the unix socket for MySQL. If this is
68			# blank, then MySQL's compiled-in default will be used. You probably
69			# want that.
70			$db_sock = '';
71
72			# Should checksetup.pl try to verify that your database setup is correct?
73			# (with some combinations of database servers/Perl modules/moonphase this
74			# doesn't work)
75			$db_check = 1;
76
77			# With the introduction of a configurable index page using the
78			# template toolkit, Bugzilla's main index page is now index.cgi.
79			# Most web servers will allow you to use index.cgi as a directory
80			# index, and many come preconfigured that way, but if yours doesn't
81			# then you'll need an index.html file that provides redirection
82			# to index.cgi. Setting $index_html to 1 below will allow
83			# checksetup.pl to create one for you if it doesn't exist.
84			# NOTE: checksetup.pl will not replace an existing file, so if you
85			# wish to have checksetup.pl create one for you, you must
86			# make sure that index.html doesn't already exist
87			$index_html = 0;
88
89			# For some optional functions of Bugzilla (such as the pretty-print patch
90			# viewer), we need the cvs binary to access files and revisions.
91			# Because it's possible that this program is not in your path, you can specify
92			# its location here. Please specify the full path to the executable.
93			$cvsbin = '/usr/bin/cvs';
94
95			# For some optional functions of Bugzilla (such as the pretty-print patch
96			# viewer), we need the interdiff binary to make diffs between two patches.
97			# Because it's possible that this program is not in your path, you can specify
98			# its location here. Please specify the full path to the executable.
99			$interdiffbin = '/usr/bin/interdiff';
100
101			# The interdiff feature needs diff, so we have to have that path.
102			# Please specify the directory name only; do not use trailing slash.
103			$diffpath = '/usr/bin';
104