Your installation of the RPM Development Environment requires a data directory to house all of the sources, patches, spec files, and built RPMs.

cd /path/to/www
mkdir -p rpm/{build_logs,SOURCES,SPECS,TMPSRC}

 When creating the following directories update distrodir to match the distribution directory.

mkdir -p rpm/base/distrodir
mkdir -p rpm/updates/distrodir
mkdir -p SRPMS/distrodir/{base,updates} 

 You also want to make sure that the apache user has write access to certain directories

chgrp apachegrp rpm/{SOURCES,SPECS,TMPSRC}
chmod g+w rpm/{SOURCES,SPECS,TMPSRC}

The next step in getting the RPMDE started is to configure the Apache server.  The following line will allow mod_perl to add the common modules to @INC.

PerlSwitches -I/path/to/common-modules-1.0

The following configuration options for Apache will allow the RPMDE front-end to execute properly.

DocumentRoot /path/to/rpmde-1.0/www
<Location />
    SetHandler perl-script
    PerlResponseHandler Kaizen::RPMDE
</Location>
<Location /images>
    SetHandler none
</Location>
<Location /css>
    SetHandler none
</Location>
<Location /js>
    SetHandler none
</Location>
<Location /rpm>
    SetHandler none
</Location>

These can be placed within a <VirtualHost> directive if you are running more than one website on the server.

Using your favorite text editor, edit rpmde-release-1.0/rpmde-1.0/etc/rpmde.conf to match your server settings.  You will then want to copy this file to a common location.

cp rpmde-release-1.0/rpmde-1.0/etc/rpmde.conf /etc

You will then want to copy the main web interface code to be included with the common-modules.

cd rpmde-release-1.0/rpmde-1.0/modules/Kaizen
cp RPMDE.pm /path/to/common-modules-1.0 

And that's it.  You should now be ready to open your browser and bring up the login page.  Use:

Username: username
Password: demo

Your first step should be to visit the Admin page to edit your username and password for the main administration account.