The checksetup.pl script located in bin must be run before Codestriker can be used, or after each upgrade. There is no harm in running it as many times as you like. The purpose of the script is to ensure all of the necessary pieces on your system are installed, and complains if they aren't.
For Window systems, edit the first line from the files bin/checksetup.pl and bin/codestriker.pl.base. For example, if you have Perl installed in c:\perl\perl, then the first line of bin/checksetup.pl should look like:
#!c:/perl/perl -wThe first line of bin/codestriker.pl.base should look like:
#!c:/perl/perl -wTNote the use of forward slashes.
Perl is available by default for all *NIX systems. For Windows, you can download it for free from http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl. Missing Perl modules can be downloaded with the ppm command typed at the command prompt, for Windows, which is the Perl Package Manager. Installing new Perl modules is easy. To install the DBI module, simply type in the following at the ppm prompt.
install DBIThis will retrieve the DBI package and install it on your system.
Codestriker requires the following Perl modules in order to run:
LWP::UserAgent CGI CGI::Carp Net::SMTP DBI IPC::Run Template HTML::Entities File::TempYou'll also require DBD::Pg for PostgreSQL or DBD::Mysql for MySQL, depending on which database you are using. Its quite possible that you already have all/most of these modules on your system. Running the checksetup.pl script will check this for you automatically.
To run checksetup.pl under *NIX, do the following:
% cd /codestriker/install/location/bin % ./checksetup.plFor Windows, you need to do something like the following from the command prompt:
% cd c:\codestriker\bin % perl checksetup.pl
This will tell you what missing Perl modules you have, and will then attempt to try and initialise the Codestriker database. Make sure your database is running, and that you have the necessary DBD::Pg/DBD::Mysql modules installed.