• Installing Mantis On Windows

New users can be set up for accessing Mantis Bug Tracker. Create a new user for Mantis. Installing Mantis. Download a copy of Mantis. Mantis 1.1.0 is what was used for this installation. Unzip this and put it into the new folder that was previously created for storing the PHP pages on the web server. Installing Mantis On Iis Dahlia PHP with IIS, run multiple PHP versions, get the information about PHP. How to install and configure mantis bugtracker. In our organization we were using some bugtracking system that is a paid service. My Particular Experience was with IIS on. If you have trouble installing some perl modules such as “DateTime. How To: Install Bugzilla on Windows.

Mantis is a web application, provides a private website to individuals or set of requested users belonging to the same company/project. Mantis can be run at the server side. It is a PHP-based application and supports all OS platforms such as Windows, Linux of different versions, MAC, etc. It supports mobile browsers as well in mobile views. System Requirements Since Mantis is a web-application, it follows the concept of client/server.

This means, Mantis can be installed centrally on the server and users can interact with it through web-browsers using a website from any computer. Web Server − Mantis is tested with Microsoft IIS and Apache. However, it can work with any latest web server software.

Mantis only uses.php file. Configure the web server with.php extension only. PHP − The web server should support PHP. It can be installed as CGI or any other integration technology. Mandatory PHP Extensions − Extensions for RDBMS are mysqli, pgsql, oci8, sqlsrv mbstring is required for Unicode - UTF-8 support. Optional Extensions − Curl, GD, Fileinfo.

Database − Mantis requires a database to store its data. MySQL and PostgreSQL are supported RDBMS.

Client Requirements − Firefox 45 and above, IE 10 and above, Chrome, Safari, and Opera. Users can separately install all the requirements either manually or automatically to use Mantis. Installation of System Requirements If a user has adequate knowledge about the installation process, all the requirements can be installed one by one separately before proceeding to Mantis. Alternatively, there are many all-in-one packages available, having all the requirements and can be automatically installed in the system by exe file. Here, we will take the help of XAMPP to install pre-requisites easily. Step 1 − Go to and click XAMPP for Windows as shown in the following screenshot. Step 2 − A pop-up will display to save the file.

Click Save File. It will start downloading the file. Step 3 − Run the.exe file to run the installation wizard. After clicking the.exe file, XAMPP Setup wizard displays. The following screenshot shows the XAMPP setup wizard. Step 4 − The next wizard displays all the component files that will install as shown in the following screenshot.

Click Next after making a selection of components. Step 5 − Provide a folder name where XAMPP will be installed and click Next. Ready to Install wizard is displayed.

Step 6 − Click Next to start the installation. Step 7 − After successful installation, it will ask to start the control panel. Check the checkbox and click Finish. It will open the XAMPP control panel as displayed in the following screenshot. Step 8 − Click the Start button for Apache and MySQL, required for Mantis as shown in the above screenshot. Step 9 − To verify whether all the pre-requisites such as Apache, PHP, and MySQL is installed properly, navigate to any of the browser, type and press Enter.

It will display the dashboard of XAMPP. Click phpAdmin at the right top corner as shown in the following screenshot. The next screenshot will display General Settings, Application Settings, Details of Database, Web Server, and phpMyAdmin. If the installation is not proper, this page won’t be displayed. Till this point, all the pre-requisites are successfully installed in the system. Install and Launch Mantis Step 1 − To download Mantis, go to Download.

Step 2 − Click Download on the next page as shown in the following screenshot. Step 3 − Again click Download as shown in the following screenshot and save the.zip file. Step 4 − Go to XAMPP folder where it is installed and navigate to htdocs folder. Unzip the downloaded mantis and place it as shown in the following screenshot. Step 5 − Rename the folder name mantis 2.5.1 as mantis for better URL.

Step 6 − Now open a browser and type in the navigation bar and press Enter. It will display the index of mantis as shown in the following screenshot.

Click mantis-2.5.1. It will display the Pre-Installation page as shown in the following screenshot. Step 7 − Go to the Installation section and make changes, if required. Then, click the Install/Upgrade Database button. Once installation is complete, it will display the Check installation page and will be marked as Good, i.e. Mantis is installed properly. Step 8 − To launch mantis, use the URL and click mantis-2.5.1.

It will display the Login page of Mantis as shown in the following screenshot. Note − Make sure the Web server and the Database, both are running before using the URL, otherwise Problem Loading Page error will be displayed.

Step 9 − Provide the username as “Administrator” and click Login. It will ask to enter the password. Use “root” as password and click Login. After successful Login, it will display the Dashboard of Mantis.

Personal Bug Tracking with Mantis on Windows GBB Services::: Personal Bug Tracking with Mantis on Windows by Whenever I do work for a client, I check my changes into their version control system, and I update my tasks using their bug tracking system (when they have one). Independently of that, I also use my own personal version control system to track the changes I make as I develop. But, I've never used a personal bug tracking system.

That I should change my evil ways, and so I did. After hearing about the hassles a client had with the closed source product TestTrack Pro from Seapine Software (the outgoing mail port is hard coded) I decided to go with an open source product.

If I need to tweak things, I don't want to depend on the owners of the source to get around to making the changes I want, if they make them at all. Free is nice, but not crucial. GBB Services spends thousands of dollars every year on development software (and thousands more on hardware). We're willing to spend money for the right products!

The best known open source bug tracker seems to be, and I downloaded it. That's about as far as I got. It's way too complicated for my purposes, and I dumped it quickly. Then I heard about. 'Easy to install, easy to customize, free, open source, works on Windows 2000.'

Installing Mantis On Windows

It sounded good. It took me a while to get Mantis working, mostly because I didn't know what I was doing. Knowing what I know now, I can get Mantis installed on a fresh machine a LOT faster.

With this note I'll be sharing some of what I learned. Mantis requires that at least two other open source programs are installed and working. They are the database application MySQL, and the scripting language PHP. I didn't have either before I started, so I had to install and use both for the first time, and then I had to coordinate their use with Mantis. It's no problem, if things go well.

I'll be mentioning some diagnostics you can run to immediately tell if things are going well or not. Also, Mantis requires that a web server be installed. I've gotten it working on two machines: a windows 2000 machine with IIS running, and a windows XP machine with Apache running.

Some details are different, depending on the http server used. If you don't care which one you use, it's probably less of a hassle to work with IIS. Incidentally, every bug tracking product I know of requires a database program, and just about all the bug tracking systems are accessed via a browser, which means that a web server has to installed.

You won't get away from these requirements by avoiding Mantis! If you haven't installed IIS, Apache, or some other http server, you'll need to that first. I've provided some pointers, but it's not the main emphasis of this essay. Also, if you care about security, you won't find any help here. I'm not really concerned about password security (for web server administration, mysql administration, or Mantis administration) since I'm the only one who's accessing my machines. Finally, if you're interested in setting up email notifications, you won't find any help here.

I don't need them for personal bug tracking. I could only find two sources of information for installing Mantis on Windows 2000 systems. One is by (the leader of the Mantis project) at, and the other is by (a contract programmer specializing in Java and C programming for the Web, Windows and Macintosh).

Both sources were extremely helpful, and although these notes are meant to be usable without them, it sure wouldn't hurt to read them. I strongly recommend methodically going through the following steps in order, and not starting any step until all previous steps have been successfully achieved: In this essay I'll be recommending that you create various diagnostic files which are to be placed in the location Since I've already created them and placed them in the zip file (1,238 bytes), you can save yourself some typing (or at least some cut and paste mouse clicking) by downloading. Just create the subdirectory mantisinfo under the web root and unzip the files there. This section is extremely sketchy compared to the other sections. It's the bare minimum you'll need to get through the installation. If you're looking to install IIS on a Windows 2000 machine, open up the control panel, click on 'Add/Remove Programs', then click on 'Add/Remove Windows Components' (which is a button to the left of the 'Currently installed programs' list). If 'Internet Information Services (IIS)' is unchecked, check it.

Hit 'Next' and get your Windows 2000 Professional installation disk. Once you've successfully installed IIS, you'll probably want to become familiar with the command line incantations 'net start w3svc' and 'net stop w3svc'. If you're looking to install, download the installation program and follow the instructions. The configuration file you'll have to become familiar with is 'C: Program Files Apache Group Apache conf httpd.conf'. Being able to type 'net start apache' and 'net stop apache' at the command line will also come in handy. Create a page 'index.html' in your (web site) root directory, and then point your web browser to it. You will probably want to use the url Firstly, go to the site at and download the file 'mysql-4.0.17-win.zip'.

It's 23,911,855 bytes and is available in the section. Look for 'Windows 95/98/NT/2000/XP/2003 (x86) 4.0.17 22.8M') To install MySQL, unzip 'mysql-4.0.17-win.zip', placing the files in some temporary directory. Then run the 'setup.exe' program. It will offer to install MySQL in the 'C: mysql' directory. That's fine with me. I then choose the 'Typical' option and let the installation program run to completion. The next step is to copy one of the files my-huge.cnf, my-large.cnf, my-medium.cnf, my-small.cnf in 'C: mysql ' to 'C: my.cnf'.

This becomes the initialization file for MySQL. The 'huge', 'large', etc descriptors refer to the amount of memory and disk space of the local machine. I've gone with copying 'my-medium.cnf' to 'C: my.cnf'. There's a couple of lines in my.cnf that read. C: tempnet start mysql System error 2 has occurred. The system cannot find the file specified.

C: temp you need to fix this before continuing. The first thing I would check is the 'path to executable' as described above. OK, now let's test the that the server is working by running some client programs. The easiest thing to try is to type 'c: mysql mysql.exe' (not 'mysql d' this time, we want the client program, not the server daemon). You should get a welcome message and the mysql prompt 'mysql'.

Type 'exit' to quit the application. The entire interaction should look something like.

C: tempnet stop mysql The MySQL service is stopping. The MySQL service was stopped successfully.

C: tempc: mysql bin mysql ERROR 2003: Can't connect to MySQL server on 'localhost' (10061) C: tempnet start mysql The MySQL service is starting. The MySQL service was started successfully. C: tempc: mysql bin mysql Welcome to the MySQL monitor. Commands end with; or g. Your MySQL connection id is 1 to server version: 4.0.17-max-debug Type 'help;' or ' h' for help.

Type ' c' to clear the buffer. Mysql exit Bye C: temp At this stage the MySQL stage of the installation is done. If you haven't got the server running, there isn't much point to doing anything else.

You've got to find out why it's not working. If you can't, you can try running mysql as a standalone application ( 'mysql d -standalone'). The details of what to get are different, depending on whether you're using or as your web server. Either way, you'll want to get the installer. Get the file 'php-4.3.4-installer.exe' (1,068,496 bytes) from the php section.

Look for 'PHP 4.3.4 installer 1,043Kb - 03 November 2003'. Run the program 'php-4.3.4-installer.exe'. I just go with the defaults.

For my Windows2000/IIS system, the Server Type was identified as 'Microsoft IIS 4 or higher', which is correct. Run the installation to the end. Skip the next section and got to. Get the file 'php-4.3.4-installer.exe' (1,068,496 bytes) from the php section. Look for 'PHP 4.3.4 installer 1,043Kb - 03 November 2003'. Run the program 'php-4.3.4-installer.exe'. I just go with the defaults, EXCEPT for picking the Server Type as 'Apache'.

For my WindowsXP/Apache system, the Server Type was identified as 'Microsoft IIS 4 or higher', which is NOT correct. Run the installation to the end. Now get 'php-4.3.4-Win32.zip' (6,978,847 bytes) from the php section. Look for 'PHP 4.3.4 zip package 6,815Kb - 03 November 2003'.

Unzip the contents of 'php-4.3.4-Win32.zip' in some temporary directory. Now move the unzipped 'sapi' subdirectory so that it becomes a subdirectory of 'c: php'.

Now move the file c: php php4ts.dll to c: php sapi php4ts.dll. The final step is to modify the Apache configuration file 'httpd.conf'.

Firstly, stop the apache server via the command line: 'net stop apache'. Add the following 3 lines to httpd.conf. Connected successfully 2003-12-28 02:24:51 Assuming that you're getting something like the above two lines, it's finally time to install Mantis itself. Go to the site at and download the 0.18.0 release. You'll want to get the file 'mantis-0.18.0.tar.gz' (543,328 bytes). The first thing to do is to unzip 'mantis-0.18.0.tar.gz', keeping the directory structure intact.

All the files will be rooted at 'mantis-0.18.0'. The next step is to move that Mantis root directory to 'c: inetpub wwwroot mantis' (assuming that the root directory of your http server is 'c: inetpub wwwroot'). The last thing to do to make sure that you have a minimal installation working is to copy the file configinc.php.sample to configinc.php Point your browser to. You should get a diagnostics page that shows 5 colored boxes, with all of them green, except for the second one.

You should have green ( GOOD ) for 'Opening connection to database on host' but red ( BAD ) for 'Selecting database' The next step is to turn all 5 boxes to green. Kill the browser window and continue with the steps below. To make life a little easier, I'll stick with defaults and call the database 'bugtracker'.

To do this, open a command line window and type 'c: mysql bin mysql', and hit return. Assuming that the mysql server is running, you should get the mysql prompt 'mysql'. At that prompt type 'CREATE DATABASE bugtracker;' and hit return.

These are sql instructions, and the semicolon is necessary. By the way, if you're unfamiliar with sql, I don't think it will matter for working with Mantis. Once you've set things up, you really don't need to do much with MySQL at all.

If all went well, you should see something like the message: Query OK, 1 row affected (0.02 sec) The mysql prompt should be available again. Type 'exit' and hit return.

You're should now be back to seeing the command line prompt. Now type 'c: mysql bin mysql bugtracker. C: tempc: mysql bin mysql Welcome to the MySQL monitor. Commands end with; or g. Your MySQL connection id is 6 to server version: 4.0.17-max-debug Type 'help;' or ' h' for help.

Type ' c' to clear the buffer. Mysql CREATE DATABASE bugtracker; Query OK, 1 row affected (0.01 sec) mysql exit Bye C: tempcd c: mysql bin C: mysql binmysql bugtracker At this stage, Mantis should work. Pointing to should give you a page with 5 green 'GOOD' table entries.

If, like me, you don't want email notification, and you don't want to see email error information for the email capability you're not using, there's one more step. Change the line. $gtoemail = '; $genableemailnotification = OFF; Now you're done! You should now be able to point to and get a login form. Using the Username 'administrator' and the Password 'root', you should be able to get in. Add a few users, add a project or two, create some categories, and go for it. You should definitely bookmark the following pages: You should also be aware of the admin page: and the stylesheet modification page: You should be aware of the following configuration files: c: my.cnf (the configuration file for MySQL) c: winnt php.ini (the configuration file for php) c: inetpub wwwroot mantis configinc.php (the configuration file for Mantis).

Something you might want to do is to have two or more completely separate Mantis projects. One possible reason might be to create a throwaway project that you can use to experiment with. Another reason might be to keep client projects completely separate from each other. One way to do have another Mantis project is by copying the 'mantis' subdirectory to a new 'mantis A' subdirectory.

Then go to c: inetpub wwwroot mantis and edit configinc.php The default database used by Mantis is 'bugtracker'. Since the whole point of a second Mantis installation is to keep the Mantis databases separated, change the default 'bugtracker' in configinc.php to something else, say 'bugtracker A' All that's left is the mysql magic incantation.

C: tempcd c: mysql bin C: mysql binmysqldump bugtracker bugtrackerBackup.txt C: mysql binmysql bugtracker mysql Welcome to the MySQL monitor. Commands end with; or g. Your MySQL connection id is 3 to server version: 4.0.17-max-debug Type 'help;' or ' h' for help. Type ' c' to clear the buffer. Mysql DROP DATABASE bugtracker; Query OK, 0 rows affected (0.13 sec) mysql CREATE DATABASE bugtracker; Query OK, 1 row affected (0.00 sec) mysql exit Bye C: mysql binmysql bugtracker If you have corrections, additions, modifications, etc please let me know January 1 2004 Posted January 3 2004 Last Updated.