Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # If you are using Apache as your web server, Bugzilla can create .htaccess
- # files for you, which will keep this file (localconfig) and other
- # confidential files from being read over the web.
- #
- # If this is set to 1, checksetup.pl will create .htaccess files if
- # they don't exist.
- #
- # If this is set to 0, checksetup.pl will not create .htaccess files.
- $create_htaccess = 1;
- # The name of the group that your web server runs as. On Red Hat
- # distributions, this is usually "apache". On Debian/Ubuntu, it is
- # usually "www-data".
- #
- # If you have use_suexec turned on below, then this is instead the name
- # of the group that your web server switches to to run cgi files.
- #
- # If this is a Windows machine, ignore this setting, as it does nothing.
- #
- # 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
- # as root or as a user who is a member of the specified group.
- www-data = 'apache';
- # Set this to 1 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 this is a Windows box, ignore this setting, as it does nothing.
- #
- # If set to 0, checksetup.pl will set file permissions appropriately for
- # a normal webserver environment.
- #
- # If set to 1, checksetup.pl will set file permissions so that Bugzilla
- # works in a SuexecUserGroup environment.
- $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 of the module (before ".pm")
- # corresponds to a valid value for this variable.
- $db_driver = 'mysql';
- # The DNS name or IP address of the host that the database server runs on.
- $db_host = 'localhost';
- # The name of the database. For Oracle, this is the database's SID. For
- # SQLite, this is a name (or path) for the DB file.
- $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 (\)
- # (It is far simpler to just not use those characters.)
- $db_pass = '123456';
- # 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, and so you can try setting this to 0 to make checksetup.pl
- # run.
- $db_check = 1;
- # Path to a PEM file with a list of trusted SSL CA certificates.
- # The file must be readable by web server user.
- $db_mysql_ssl_ca_file = '';
- # Path to a directory containing trusted SSL CA certificates in PEM format.
- # Directory and files inside must be readable by the web server user.
- $db_mysql_ssl_ca_path = '';
- # Full path to the client SSL certificate in PEM format we will present to the DB server.
- # The file must be readable by web server user.
- $db_mysql_ssl_client_cert = '';
- # Full path to the private key corresponding to the client SSL certificate.
- # The file must not be password-protected and must be readable by web server user.
- $db_mysql_ssl_client_key = '';
- # 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 an index.html 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;
- # If you want to use the "Difference Between Two Patches" feature of the
- # Patch Viewer, please specify the full path to the "interdiff" executable
- # here.
- $interdiffbin = '/usr/bin/interdiff';
- # For the "Difference Between Two Patches" feature to work, we need to know
- # what directory the "diff" bin is in. (You only need to set this if you
- # are using that feature of the Patch Viewer.)
- $diffpath = '/usr/bin';
- # This secret key is used by your installation for the creation and
- # validation of encrypted tokens. These tokens are used to implement
- # security features in Bugzilla, to protect against certain types of attacks.
- # A random string is generated by default. It's very important that this key
- # is kept secret. It also must be very long.
- $site_wide_secret = 'yWBQcKo3yheFxGBE3ZzDiTCvVPuiKhnspbhP0v8oJ8DhE5vunNYDe2mOwsLRWdK9';
Add Comment
Please, Sign In to add comment