Guest User

Untitled

a guest
Apr 4th, 2019
56
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.64 KB | None | 0 0
  1. # If you are using Apache as your web server, Bugzilla can create .htaccess
  2. # files for you, which will keep this file (localconfig) and other
  3. # confidential files from being read over the web.
  4. #
  5. # If this is set to 1, checksetup.pl will create .htaccess files if
  6. # they don't exist.
  7. #
  8. # If this is set to 0, checksetup.pl will not create .htaccess files.
  9. $create_htaccess = 1;
  10.  
  11. # The name of the group that your web server runs as. On Red Hat
  12. # distributions, this is usually "apache". On Debian/Ubuntu, it is
  13. # usually "www-data".
  14. #
  15. # If you have use_suexec turned on below, then this is instead the name
  16. # of the group that your web server switches to to run cgi files.
  17. #
  18. # If this is a Windows machine, ignore this setting, as it does nothing.
  19. #
  20. # If you do not have access to the group your scripts will run under,
  21. # set this to "". If you do set this to "", then your Bugzilla installation
  22. # will be _VERY_ insecure, because some files will be world readable/writable,
  23. # and so anyone who can get local access to your machine can do whatever they
  24. # want. You should only have this set to "" if this is a testing installation
  25. # and you cannot set this up any other way. YOU HAVE BEEN WARNED!
  26. #
  27. # If you set this to anything other than "", you will need to run checksetup.pl
  28. # as root or as a user who is a member of the specified group.
  29. www-data = 'apache';
  30.  
  31. # Set this to 1 if Bugzilla runs in an Apache SuexecUserGroup environment.
  32. #
  33. # If your web server runs control panel software (cPanel, Plesk or similar),
  34. # or if your Bugzilla is to run in a shared hosting environment, then you are
  35. # almost certainly in an Apache SuexecUserGroup environment.
  36. #
  37. # If this is a Windows box, ignore this setting, as it does nothing.
  38. #
  39. # If set to 0, checksetup.pl will set file permissions appropriately for
  40. # a normal webserver environment.
  41. #
  42. # If set to 1, checksetup.pl will set file permissions so that Bugzilla
  43. # works in a SuexecUserGroup environment.
  44. $use_suexec = 0;
  45.  
  46. # What SQL database to use. Default is mysql. List of supported databases
  47. # can be obtained by listing Bugzilla/DB directory - every module corresponds
  48. # to one supported database and the name of the module (before ".pm")
  49. # corresponds to a valid value for this variable.
  50. $db_driver = 'mysql';
  51.  
  52. # The DNS name or IP address of the host that the database server runs on.
  53. $db_host = 'localhost';
  54.  
  55. # The name of the database. For Oracle, this is the database's SID. For
  56. # SQLite, this is a name (or path) for the DB file.
  57. $db_name = 'bugs';
  58.  
  59. # Who we connect to the database as.
  60. $db_user = 'bugs';
  61.  
  62. # Enter your database password here. It's normally advisable to specify
  63. # a password for your bugzilla database user.
  64. # If you use apostrophe (') or a backslash (\) in your password, you'll
  65. # need to escape it by preceding it with a '\' character. (\') or (\)
  66. # (It is far simpler to just not use those characters.)
  67. $db_pass = '123456';
  68.  
  69. # Sometimes the database server is running on a non-standard port. If that's
  70. # the case for your database server, set this to the port number that your
  71. # database server is running on. Setting this to 0 means "use the default
  72. # port for my database server."
  73. $db_port = 0;
  74.  
  75. # MySQL Only: Enter a path to the unix socket for MySQL. If this is
  76. # blank, then MySQL's compiled-in default will be used. You probably
  77. # want that.
  78. $db_sock = '';
  79.  
  80. # Should checksetup.pl try to verify that your database setup is correct?
  81. # With some combinations of database servers/Perl modules/moonphase this
  82. # doesn't work, and so you can try setting this to 0 to make checksetup.pl
  83. # run.
  84. $db_check = 1;
  85.  
  86. # Path to a PEM file with a list of trusted SSL CA certificates.
  87. # The file must be readable by web server user.
  88. $db_mysql_ssl_ca_file = '';
  89.  
  90. # Path to a directory containing trusted SSL CA certificates in PEM format.
  91. # Directory and files inside must be readable by the web server user.
  92. $db_mysql_ssl_ca_path = '';
  93.  
  94. # Full path to the client SSL certificate in PEM format we will present to the DB server.
  95. # The file must be readable by web server user.
  96. $db_mysql_ssl_client_cert = '';
  97.  
  98. # Full path to the private key corresponding to the client SSL certificate.
  99. # The file must not be password-protected and must be readable by web server user.
  100. $db_mysql_ssl_client_key = '';
  101.  
  102. # Most web servers will allow you to use index.cgi as a directory
  103. # index, and many come preconfigured that way, but if yours doesn't
  104. # then you'll need an index.html file that provides redirection
  105. # to index.cgi. Setting $index_html to 1 below will allow
  106. # checksetup.pl to create an index.html for you if it doesn't exist.
  107. # NOTE: checksetup.pl will not replace an existing file, so if you
  108. # wish to have checksetup.pl create one for you, you must
  109. # make sure that index.html doesn't already exist.
  110. $index_html = 0;
  111.  
  112. # If you want to use the "Difference Between Two Patches" feature of the
  113. # Patch Viewer, please specify the full path to the "interdiff" executable
  114. # here.
  115. $interdiffbin = '/usr/bin/interdiff';
  116.  
  117. # For the "Difference Between Two Patches" feature to work, we need to know
  118. # what directory the "diff" bin is in. (You only need to set this if you
  119. # are using that feature of the Patch Viewer.)
  120. $diffpath = '/usr/bin';
  121.  
  122. # This secret key is used by your installation for the creation and
  123. # validation of encrypted tokens. These tokens are used to implement
  124. # security features in Bugzilla, to protect against certain types of attacks.
  125. # A random string is generated by default. It's very important that this key
  126. # is kept secret. It also must be very long.
  127. $site_wide_secret = 'yWBQcKo3yheFxGBE3ZzDiTCvVPuiKhnspbhP0v8oJ8DhE5vunNYDe2mOwsLRWdK9';
Add Comment
Please, Sign In to add comment