Chapter 2.  Installation

Table of Contents

Server installation
Configuration
Client installation
Linux installation
Windows installation
Proxy installation

Server installation

The server installation is fairly simple. Copy the ServerScripts directory of the Gubed archive to your webroot (or some other place in the web tree that you'd rather have it in)

If you're using some installation package, like the Windows installer, it might prompt you for a location to install the server scripts when you're installing the client.

It is important to realize that putting Gubed on a public server poses a security risk. Partly because if someone manages to hack it and make it contact their debug client, they can control how your scripts work and thus gain access to things they are not supposed to have access to.

Gubed also includes some scripts to help debugging Gubed it self, and upon request, these scripts scans the filesystem and displays the source of php files.

You have to protect your Gubed web tree , for example by using your webservers buildt in security handling. The very least you should do is to remove the debug directory of the Gubed web tree to prevent anyone from scanning your system for PHP files. (On the other hand, if your directory or server is protected, the develop directory might come in hand if you require support or experience problems.)

Configuration

Before you can start using Gubed, you'll have to configure the server scripts.

In the Gubed ServerScripts directory on your server, there is a file called localsettings_dist.php. Rename this file to localsettings.php and open it in a text editor.

If you're not running the client and the server on the same computer, you will need to specify what computer the client (or proxy, if you use it) is on by altering the following line

               $gbdDebugServer = "localhost";
            

You can also change the port used

               $gbdDebugPort = 8016;   // 8016 is Gubed default
            

Gubed uses a directory for cacheing the parsed PHP files so they wont need to be reparsed every time they are used. If you do not wish to use this feature, you can set the cache dir to a blank string, you can also change it to another location than the default one (which is the default temp dir).

               $GLOBALS['gbd']['cachedir'] = '/tmp/GubedCache/';
            

Last but no least, you can specify one or many filename patterns of files that you don't want Gubed to debug. The default settings makes Gubed not debug Smarty or ADOdb.

It's generally a good idea to be careful of what you put here, in case the non-debugged code genereates errors, Gubed might get confused.

               $GLOBALS['gbd']['gbdNoDebug'] = Array(
                  '.*?adodb\.inc\.php',
                  '.*?Smarty\.class\.php',
               );