The Bug Genie
The Bug Genie
Please log in to subscribe to updates for this article
The Bug Genie:How To:IISConfiguration
Last updated at Mon Aug 12 12:09, by kanto501

Howto setup The Bug Genie for Internet Information Services  ⇑ top

Step 1: Installing  ⇑ top

If you are impatient and use IIS 7 or later, we recommend you use the Microsoft Web Platform Installer tool to install IIS, MySQL and PHP for you. This tool does not currently install PostgreSQL. You will also need to install the URL Rewrite module. WebPI will also let you install the Microsoft Cache extension, which will improve performance. If you use IIS 6 or before, you will need to manually install, this includes finding an alternative URL Rewriting module.

If you do not wish to use this tool, then you will need to install the components separately, which is beyond the scope of this guide. We recommend you use Microsoft's PHP plugin for IIS rather than ISAPI filters for performance reasons.

Now, copy The Bug Genie to its installation place.

Step 2: Permissions  ⇑ top

The IIS user will need write access to various directories to install TBG. You will be informed which directories need permission, but if you get a mkdir error, it may be necessary to set the permissions in advance. These will need setting on:
This is a rough list, there may be others necessary.

You can now install, but it will fail at completion (when trying to log in) as the rules will not be set.

Step 3: URL Rewriting  ⇑ top

IIS 6  ⇑ top

Helicon make an excellent URL rewriting module, which is available in both free and commercial versions. If you use this ISAPI module, and you pay for the full version, your life will be a lot easier. This ISAPI module (in the commercial version) can parse the htaccess file generated by The Bug Genie installer, and so no further configuration will be necessary.

If you do not pay for the commercial version, some extra configuration will be necessary, as the free version will only parse a httpd.conf file. This can be edited using the provided tool found in the Start Menu. All that is necessary is to take the contents of the autogenerated htaccess file, and place its contents in the httpd.conf file. The Helicon tool will likely complain that the .svn rule is invalid, this can be safely commented out.
Alternative using IIRF  ⇑ top
On Code Plex, there is also a free and open source plugin called IIRF which also provides URL rewriting functionality. This is a little more complicated to set up, but SB#1 has written a great guide about it over on the forums:

IIS 7 and later  ⇑ top

You could also just use Helicon's plugin or IIRF, but this is native to IIS 7, so may be a better choice. Go to the URL Rewriting settings for your web site (not the server), and create a new rule.

This rule will convert the friendly URLs to the internal TBG ones. We are assuming that the directory containing index.php is at /thebuggenie/thebuggenie
  • Pattern: ^thebuggenie/thebuggenie(.*)$ (ignore case)
  • Conditions - match all
    • {REQUEST_FILENAME} Is Not a File
    • {REQUEST_FILENAME} Is Not a Directory
  • Action - rewrite
    • URL: /thebuggenie/thebuggenie/index.php?url={R:1}
    • Append query string
  • Stop processing of subsequent rules
You are now ready to use The Bug Genie on IIS!

Note: This rule has scope for improvement, and is just here to get you started. If your are able to improve it at all, please let us know!

Article attachments

There are no file attached to this article

Article comments (1)