Installing Multiple Copies of a Script
Sometime you might want a second copy of a program
installed on the same server. You might have a content
rotator like Content Carousel displaying your
testimonials, for example, and you also want to rotate
webmaster tips or banners.
Unless it's specifically coded to do otherwise, a program
will maintain one set of related data in it's database(s).
So when you want to work with a different set of data, like
the Content Carousel example above, a separate copy
of the program needs to be installed and configured to
work with a separate database.
Probably any script you need a second copy of is a program
that interacts with a database in some way. A second
installation would then be a bit more complex than simply
uploading another copy with a different name.
The following assumes the license to your scripts do not
prohibit installation of multiple copies and that it is
otherwise legal for you to do so. (Licenses to our Master
Series of CGI programs
do not prohibit multiple copy installations on the same domain.)
Installing in the Same Directory
If your script allows you to specify the directory name
where the database(s) will reside, and/or allows you to
specify the database file name(s), then it is feasible
to install a second copy as a different file name in the
same directory as the current installation. The second
copy would specify different database directory or file
names.
This can be done with Content Carousel, for example.
Content Carousel allows you to specify the directory
name where the content databases will reside. To install a
second copy, simply specify a different database directory
name and then upload the script as a different file name.
Thus, you might have these two installations:
- Program /cgi-bin/ContentCarousel.cgi with
database directory /cgi-bin/cc1
- Program /cgi-bin/ContentCarousel2.cgi with
database directory /cgi-bin/cc2
For any script, you have another option -- installing each
copy of the program in its own unique directory.
Installing in Different Directories
Second and subsequent copies of any script may be installed
in their own directories. If your script does not allow you
to specify the database directory or file names, then
subsequent copies must be installed this way.
Master Syndicator is an example. That program requires a
database directory named "data". A multiple installation
might look like this:
- Program /cgi-bin/ms1/MasterSyndicator.cgi with
database directory /cgi-bin/ms1/data
- Program /cgi-bin/ms2/MasterSyndicator.cgi with
database directory /cgi-bin/ms2/data
Program Sets of More than One Script
The second installation of CGI programs composed of more
than one script should be in its own unique directory.
Actually, it is a good idea to put the first installation
in its own directory, also. In its own directory, the
numerous files won't get mixed up with other scripts.
Programs that Use No Databases
If a CGI program uses no databases, then it is unlikely you
will need additional copies installed -- it will probably
work quite well being accessed from different forms or
scripts. However, if you need another copy, it can be
installed either with a different file name or in a
separate directory.
Question:
Did you find this article interesting and understandable? How can it be improved?
Your response is anonymous.
When done typing, click anywhere outside the box. [more info]
Will Bontrager
©2001 Bontrager Connection, LLC
Please note:
Articles on this website are presented "as is". However -
If you have a question about a CGI script, HTML, CSS, PHP, or JavaScript
Ask one of our Experts and you'll have your answer!
Click here for details.
