Installing Scripts - Don't be Scared!

Getting Started with Script Installation

When I first launched a website, I imagined that putting a script on my server would be as easy as dropping a file into a folder and hitting refresh. Instead, I discovered that the process is a series of small, precise steps that require attention to detail. The most common mistake new webmasters make is skipping the ReadMe or INSTALL file that comes bundled with the script. Those files were written by the developers to prevent the very errors that ate up my first few hours.

The first thing you should do when you download a script is unzip it locally and read every line of the accompanying documentation. Most authors use plain text and a clear, step‑by‑step format. If the script is written in Perl, look for sections that mention “CGI,” “/cgi-bin,” or “PERL5LIB.” These clues point to the directories the script expects to find itself in. You’ll also see references to file permissions - watch for those because they affect whether the script can read or write data once it’s on the server.

Next, think about the environment your host provides. Most shared hosting plans run on a Unix‑like operating system, which means permissions, file paths, and command line utilities behave the same way they do on a Linux box. If you’re on a Windows host, the process is similar, but you’ll need to adjust paths and use the appropriate FTP client. For the rest of this guide, I’ll assume a typical Unix environment, as that is where the majority of CGI scripts run.

Once you understand the script’s prerequisites, the next step is to prepare the files. If the distribution contains a README, you’ll often find a list of required Perl modules, database drivers, or external programs. Some scripts require the Sendmail binary to be present for e‑mail notifications. A quick way to verify that your host has these tools is to SSH into the server and run perl -v or sendmail -v. If you don’t have SSH, many hosts provide a web‑based terminal or a list of available binaries on their support pages.

Now, before you even start the upload process, it helps to plan the directory layout. The most common approach is to create a separate subdirectory under /cgi-bin for each script. That keeps files tidy and avoids name clashes if you run multiple instances of the same script on the same server. For example, if you’re installing a survey script, you might create /cgi-bin/survey and copy all the .cgi files there. If you’re also running a logging script, give it its own folder, such as /cgi-bin/logger. A well‑structured layout simplifies future maintenance and makes it easier to back up or delete individual components.

After you’ve organized the folders on your local machine, it’s time to transfer them. You’ll need an FTP client that can preserve file permissions. A popular choice among hobbyists is