This does not affect Big Files, attachments that are stored directly on disk instead of in the database. You need to add a new user to PostgreSQL for the Bugzilla application to use when accessing the database. The following instructions assume the defaults in localconfig ; if you changed those, you need to modify the commands appropriately.
On most systems, to create the user in PostgreSQL, you will need to login as the root user, and then. The created user will not be a superuser -S and will not be able to create new users -R. He will only have the ability to create databases -d. In this file, you will need to add a new line to it as follows:. Now, you will need to restart PostgreSQL, but you will need to fully stop and start the server rather than just restarting due to the possibility of a change to postgresql.
You can use the existing tablespace or create a new one for Bugzilla. To create a new tablespace, run the following command:. Here, the name of the tablespace is 'bugs', but you can choose another name. 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. If installed in a subfolder say example. The included test suite testserver. Bugzilla's upgrade process is usually very simple, but make sure to read the Release Notes first. Upgrade from one major release to the next don't skip major releases. You may want to create a backup of your Bugzilla database before upgrading:.
Unpack Bugzilla into your destination directory, and copy the localconfig file over from the previous installation:.
The script will automatically check the dependencies and upgrade the database. After it completes successfully, make sure to log in as administrator and review your configuration settings.
Again, for MySQL:. If there are any errors during this step, you have to work out what went wrong, and then drop the database, create it again using the step above, and run the import again. Run checksetup. Unless you are using a newer version of Bugzilla on your new server, this should not make any changes. Activate your new Bugzilla by loading the front page on the new server, going to Administration Parameters General and removing the text from the shutdownhtml parameter.
Navigation next previous Bugzilla 5. Installation and Maintenance Guide ». Copy the database backup file from your old server to the new one.
0コメント