===========================================================================
== 3.3   Configuring the main program
===========================================================================

Congratulations! You should now have correctly configured podvars.pm - the
main configuration section of the Personal Open Directory.

You've just got two more little steps to do, these require modification
to the main script (pod.cgi). So, load the pod.cgi file into your
favourite text editor and let's make the alterations:


===========================================================================
== 3.3.1   Setting the path to Perl
===========================================================================

First of all, you need to tell pod.cgi where your Perl interpreter
is. If you aren't sure where Perl is, have a look at 'Appendix A -
Finding Perl'.

Now load pod.cgi into your text editor, and look at the first line:
 #!/usr/bin/perl
change this to reflect where your Perl interpreter is.

For example, if
 Your Perl Interpreter is in:      Then this line needs to read:
 /usr/bin/perl                     #!/usr/bin/perl
 /usr/perl/perl                    #!/usr/perl/perl
 /bin/perl                         #!/bin/perl
 
Now move onto the next step...


===========================================================================
== 3.3.2   Setting the path to podvars.pm
===========================================================================

This is the step that often causes the most problems.

In line 31 of pod.cgi (marked by 'Configuration area') you need to tell
the script where podvars.pm is located so that it can read in all your
settings - if you don't set this correctly pod.cgi will fail.

If you upload podvars.pm and pod.cgi into the same directory, you can
normally get POD to work by using the line:
 require "podvars.pm";
but if this doesn't work, you need to set the full server path of the
location of podvars.pm. If you aren't quite sure where podvars.pm is
stored in the server path, try telnetting to your server, logging
in, going to the directory that podvars.pm and typing:
 pwd
This (at least on Posix machines - ie Unix, Linux, BSD etc.) returns
the current path such as:
 /home/user/public_html/cgi-bin/
Then just set the 'requires' line to this, thusly:
 require "/home/user/public_html/cgi-bin/podvars.pm";
 
If you are having serious difficulties in getting pod.cgi to work, you
can try cutting and pasting the entire podvars.pm file into the *end*
of pod.cgi (after the line marked 1; in pod.cgi). Then you just
need to insert a hash character in front of the require line to
disable the inclusion section - ie
 #require "anything at all";
 
Now save the pod.cgi file and now you are ready to upload....

===========================================================================
== 3.3.3   Uploading the main program
===========================================================================

Uploading is normally the simple half of this two part process - the
file permission settings are usually the hardest part. If you have
installed a cgi program before, this bit should be second nature :)

Using your ftp program (such as WSFtp, FTPc, FTPclient, AbsoluteFTP etc)
upload the following files:

 header.html   footer.html   into your 'templates directory' - see section
                             '3.2.1 Script Configuration' regarding the
                             variable $pod_templatedir
                          and
 pod.cgi       podvars.pm    into your cgi-bin.
 
This directory (cgi-bin) may not be called cgi-bin, it may be called
'cgibin', 'cgis', 'bin' etc. It may also be located either inside your
html directory (ie in /home/user/public_html/cgi-bin ) or outside
( /home/user/cgi-bin ).

If you can't find a suitably named directory, don't panic. Your
server administrator can probably tell you where you should upload
Perl cgi programs (if you can run them on your server). You may
be told that you don't need to put them in a specific directory -
if so, just upload them anywhere! (within reason of course :) ).

Check with your webmaster that your web server has GET and POST
allowed.

Now to set the file permissions...

Pod.cgi needs to be executable and readable by everyone accessing
it - but the method of doing so various from setup to setup, have
a look at 'Appendix B - Setting file permissions' for details

And that's it - POD should now be working on your system!