This chapter lists the steps required to install a new instance of the WebIssues Server.
-
Download and unpack the
webissues-server
package. Move all files from the unpacked directory to the web server's document root or your public HTML directory. Refer to the appropriate documentation for more information about configuring the web server. -
Create a database and a user with sufficient privileges to create tables. The Database chapter contains instructions for creating the database using the standard command line tools. If you are using a different tool for managing the databases, refer to the relevant documentation for more information.
-
Create the
storage
andlog
subdirectories in the server's location. Make sure they are writable for the web server and not accessible for anyone else. -
Copy
config/config-template.inc.php
toconfig/config.inc.php
and edit the created file to configure database connection and other settings. See Configuration for more information. -
Point your browser to the
setup.php
script in the server's location, for examplehttp://www.example.com/setup.php
and follow the installation steps. The script will check the configuration, create the database tables, set up the administrator account and import an initial set of issue types.
After the setup is finished, you will be able to connect to your server using the WebIssues Desktop Client application to configure the projects, folders, issue types and user accounts. Use the location of the index.php
script as the server's URL, for example http://www.example.com/index.php
.
If you wish to use email notifications, configure a cron job or Scheduled Task to periodically execute the cron.php
script and make sure the mailing engine is configured correctly. Refer to the Notifications section for more details.
Warning
Make sure the configuration file, file attachments and server logs are not accessible for unauthorized users. See the Security chapter for more information about security settings.
You can check if the WebIssues Server is working by opening its URL in the browser. It will connect to the database, test if it is configured correctly and display a status message. You can also use the error log to check if there are any problems.
Copyright © 2007-2009 WebIssues Team