It reconfirms that all the modules are present, and notices the altered localconfig file, which it assumes you have edited to your satisfaction. After that, it asks for details of an administrator account. Bugzilla can have multiple administrators — you can create more later — but it needs one to start off with. Enter the email address of an administrator, his or her full name, and a suitable Bugzilla password. Configure your web server according to the instructions in the appropriate section.
If it makes a difference in your choice, the Bugzilla Team recommends Apache. To check whether your web server is correctly configured, try to access testagent. Regardless of which web server you are using, however, ensure that sensitive information is not remotely available by properly applying the access controls.
You can run testserver. These instructions: allow apache to run. Such changes would also apply to the Bugzilla directory… but they would also apply to many other places where they may or may not be appropriate. In most cases, including this one, it is better to be as restrictive as possible when granting extra access. Without this directive, Apache will not follow symbolic links to places outside its own directory structure, and you will be unable to run Bugzilla.
Please ensure you have run checksetup. You will need to create a virtual directory for the Bugzilla install. Put the Bugzilla files in a directory that is named something other than what you want your end-users accessing. Using the IIS Administration tool again, open up the properties for the new virtual directory and select the Configuration option to access the Script Mappings.
Create an entry mapping. The Active State install may have already created an entry for. IIS will also need to know that the index. On the Documents tab page of the virtual directory properties, you need to add index. Your Bugzilla should now be working. The URL above may be incorrect if you installed Bugzilla into a subdirectory or used a symbolic link from your web site root to the Bugzilla directory. Log in with the administrator account you defined in the last checksetup.
You should go through the Parameters page and see if there are any you wish to change. They key parameters are documented, you should certainly alter maintainer and urlbase; you may also want to alter cookie path or require login. Learn and enhance your Bugzilla Configuration skills.
Bugzilla Configuration. Bugzilla Configuration The poor Bugzilla configuration has led to many attackers. Bugzilla Configuration: localconfig Firstly, you should now run checksetup. Bugzilla Configuration: Database Server This section deals with configuring your database server for use with Bugzilla. Important points to note are: Be sure that the root account has a secure password set. If your web server and MySQL server are on the same machine, you should disable the network access.
Allow large attachments and many comments By default, MySQL will only allow you to insert things into the database that are smaller than 1MB. In this file, you will need to add a new line to it as follows: host all bugs Oracle Create a New Table space You can use the existing tablespace or create a new one for Bugzilla. You may rerun checksetup. Web server Configure your web server according to the instructions in the appropriate section. Add the following lines to a directive that applies to the location of your Bugzilla installation.
Find the Group line in httpd. Add the following information to your httpd. You could be looking at 30MB per httpd child, easily. Basically, you just need a lot of RAM. The more RAM you can get, the better. You can change localconfig and the params file manually, if you want, because those are re-read every time you load a page. Bugzilla has not been tested with more than one instance running. The initial size of the database file is set in this example to Mb, with an increment of 30 Mb everytime we reach the size limit of the file.
Here, we assume that the user name is 'bugs' and the tablespace name is the same as above. If you use Apache, append these lines to httpd. For instance:. No special configuration is required to run Bugzilla on SQLite. Next, rerun checksetup. It reconfirms that all the modules are present, and notices the altered localconfig file, which it assumes you have edited to your satisfaction. It compiles the UI templates, connects to the database using the 'bugs' user you created and the password you defined, and creates the 'bugs' database and the tables therein.
After that, it asks for details of an administrator account. Bugzilla can have multiple administrators - you can create more later - but it needs one to start off with. Enter the email address of an administrator, his or her full name, and a suitable Bugzilla password. You may rerun checksetup. Configure your web server according to the instructions in the appropriate section. If it makes a difference in your choice, the Bugzilla Team recommends Apache. To check whether your web server is correctly configured, try to access testagent.
If "OK" is displayed, then your configuration is successful. Regardless of which web server you are using, however, ensure that sensitive information is not remotely available by properly applying the access controls in Section 4. You can run testserver. Load httpd. Add the following lines to a directive that applies to the location of your Bugzilla installation. If such a section does not exist, you'll want to add one. These instructions: allow apache to run. It is possible to make these changes globally, or to the directive controlling Bugzilla's parent directory e.
Such changes would also apply to the Bugzilla directory In most cases, including this one, it is better to be as restrictive as possible when granting extra access. Find the Group line in httpd.
Without this directive, Apache will not follow symbolic links to places outside its own directory structure, and you will be unable to run Bugzilla. Add the following information to your httpd. Please ensure you have run checksetup. You could be looking at 30MB per httpd child, easily. Basically, you just need a lot of RAM. The more RAM you can get, the better. You can't just reload--you have to actually restart the server as in make sure it stops and starts again.
You can change localconfig and the params file manually, if you want, because those are re-read every time you load a page. And, in fact, we're fairly sure it won't work. Bugzilla has not been tested with more than one instance running. You will need to create a virtual directory for the Bugzilla install. Put the Bugzilla files in a directory that is named something other than what you want your end-users accessing.
Instead, place them in a different location, and then use the IIS Administration tool to create a Virtual Directory named "Bugzilla" that acts as an alias for the actual location of the files.
You will also need to tell IIS how to handle Bugzilla's. Using the IIS Administration tool again, open up the properties for the new virtual directory and select the Configuration option to access the Script Mappings. Create an entry mapping. The ActiveState install may have already created an entry for.
If so, this mapping should be removed as Bugzilla's. IIS will also need to know that the index. On the Documents tab page of the virtual directory properties, you need to add index. If you wish, you may remove the other default document types for this particular virtual directory, since Bugzilla doesn't use any of them. Also, and this can't be stressed enough, make sure that files such as localconfig and your data directory are secured as described in Section 4.
Your Bugzilla should now be working. If not, consult the Troubleshooting section, Appendix A, Troubleshooting. The URL above may be incorrect if you installed Bugzilla into a subdirectory or used a symbolic link from your web site root to the Bugzilla directory.
Log in with the administrator account you defined in the last checksetup. You should go through the Parameters page and see if there are any you wish to change. They key parameters are documented in Section 3. Bugzilla has several optional features which require extra configuration.
You can read about those in Section 2. Configuration Prev Chapter 2. Installing Bugzilla Next.
0コメント