Web server and an FTP client (such as) to upload the files to your account and them on the server. Also, you should be modestly comfortable with editing HTML to customize the templates, and thus make your Weblog, journal, or photolog truly your own.

Upgrading From a Previous Version of

Users of a previous version of should download the 1.21c UpdatePak from and then upload the new files to your server. The UpdatePak will not over-write your templates, entries, or anything else; it simply provides new functionality and bug-fixes to . If you have patched your installation, you may want to read the changelog on the to see what has been added. New versions of patches will be available as soon as possible for Version 1.21c.

Before uploding the UpdatePak files, make sure you have the Perl pointer in correctly edited for your server. It's also wise to make a backup, just in case something goes wrong. After uploading the files, check to everything's okay, log in and make sure that everything's a-okay.

We hope that you'll like the UpdatePak as a way to upgrade without the chance of accidentally over-writing anything on your current installation.

Before You Start

During the process of installing , you will need to know some things about your account on your Web server and how you want your site to work. It would be helpful if you wrote them down or had them stored electronically, so you could have them as a reference. Yes, it's time to take some notes. :)

1. Where is Perl?
   The location of Perl is vitally important to running . Your Web host can tell you where Perl is located, or you can find out for yourself if you have access via telnet or SSH to your server. If you have such access, type 'whereis perl' at the prompt, and make note of that location. It will be something like '', '', or '5' on a Unix server. On a Windows server, it may be 'C:/perl/bin/perl.exe'.
   Once you know the location of Perl, make a note of it, and go on to the next step.
2. What will your site structure be?
   It seems silly to think about this so early, but setting the site structure is like building the foundation for a house. That's why we'll lay a good foundation now.
   First, it will be important to know how you want your log to appear. Some people like to have their -powered log appear on the main page of their site; when that is the case, bringing up / will show the log. Others like to have their log in another place, in what is called a subdirectory. In that case, it's usually something like , where is the location of the log.
   So, take some time to think about it. needs to know two things to properly present your log: where your main page for your log will be, and where you want your archives to be. If you wanted your main log to be at /weblog/, and the archives folder for that to be called "blatherings", your archives will be stored at .
3. Where are your CGI files kept on the server?
   When you upload and install , it will take a good stab how your Web server is set up. It will always find the directory where CGI files should be kept, assuming that you upload it to the right place.
   To make sure you do it right, start your FTP program and just look at your account's main folder. What is that folder called? [Write that down; if you can't see, try to go "up" a folder and see if you can see that.] Do you see a folder named If so, find that, and make a note of where it is in relation to the main folder of your site. That will help you later on in the installation process.

Once you've made these notes, you're ready to roll.

Installing For The First Time

1. Make sure you meet all the requirements, as specified above.
2. Separately, open the files very first line, which should say. Make sure that the Perl pointer here is correct; refer to your notes that you made. If, for example, your Perl directory is '', change the first line in each of the four files to reflect that. You must maintain the #! [the shebang, if you're wondering what to call it] before the directory, or it just won't work. This is the only time you'll ever need to touch the program code.
3. Refer to your notes above about site structure. If you want your main index file to be named something other than "index.htm", then rename the included index.htm file accordingly. For clarity's sake, we'll assume "index.htm" with the rest of the instructions.
4. Open your FTP program. Important note: All files except "gm-icon.gif" must be uploaded in ASCII mode; check your FTP program to find out how to make sure that all CGI files are uploaded as ASCII and not binary files.
5. Upload all the CGI files (they all begin with "gm" and end with ".cgi") to the CGI files directory you found above in your notes. All these files must be in the same directory on your account.
6. the files "gm.cgi", "gm-karma.cgi", "gm-comments.cgi", and "gm-upload.cgi" , and all the other .cgi files to 666.
7. Upload index.htm (or whatever you've renamed it to) and gm-icon.gif to the place where you want your log to be. Refer to your notes above for that process.
8. the index.htm file (or whatever you've renamed it to) to 666.
9. Create the directory where all your log entries and archives will be stored. Refer to your notes above when creating this directory. By default, will assume you name this directory "archives", but you can name it whatever you wish.
10. your entries/archives directory to .
11. Open your Web browser and run gm.cgi on your site (for example, if you run and you uploaded the files to the / subdirectory, then you'd type /gm.cgi in your browser). If all of the above went okay, then you should now see the logon prompt. (If you're getting a 500 Server Error or having other problems attempting to run gm.cgi, go back and make sure that everything is uploaded and ed correctly; read the "Troubleshooting" section in the manual for more information.)
12. Log on with the author name "Alice", and the password "wonderland".

Configuring Your Paths

We'll use the following example site structure to explain the paths setup; this is where a sizable group of new users have gotten confused before, so we'll work with this example and use it to explain all six paths.

Our example comes from the site structure of Geof Morris, one of the authors of this set of installation instructions. [Though it's about to be re-designed, it will still be clear for you.]

Geof's site is /, and he hosts a log on the front page. His entries and archives folder is , so it's found at . His server requires CGI files to be in the / directory, so his installation is found at /gm.cgi .

Now, the first time you look at your paths, they'll be wrong. That's okay! For an example, here's what Geof saw the first time he installed :

Next, he'd created in the main directory of his site, and that's where he wanted his archives and entries to be. So the Entries/Archives paths were going to have to change. Here's what they became:

What about the CGI files? Well, that's what gets correct every time. There's no need to change the two CGI paths, unless you want in a subdirectory of your

Diagnostics and Repair, Author Configuration

Return to Configuration and click "Diagnostics & Repair". This routine checks to see that all your files and paths are working correctly. If you aren't able to run it successfully, your paths are probably incorrect; check the Troubleshooting section of the manual. Once you've run it successfully, you'll be able to post your first entry.

Click "Edit Authors", create a new account for yourself with the name and password you'd like to use, and delete Alice. (You could keep Alice around, but for obvious security reasons, it's not recommended.) Since you're still logged on as Alice, you'll need to re-enter under the new name and password.

All done! You should now be able to post entries and get your Weblog, journal, or photolog going. (It's a good idea to set up a private test log first, and try creating and editing a few test entries, simply so you can get the hang of before doing it "for real".)

uses an extensive template system to allow you total control over every aspect of your Weblog and all the pages & elements it'll comprise. The default templates included with are quite plain-jane, but they should be enough to provide a starting point and, hopefully, to give you a basic idea of 's template & variable usage. Change the templates as much as you like (and just reupload the gm-templates.cgi file if you mess things up too much and want to start over) to suit your own design and style; refer to the manual for full information about all the template variables.

And that's that! Hopefully by now you're up and running in some form--after you add your first entry, open another window in your browser and load up your log's intended location. You can alter your templates anytime to change any aspect of your log's design and layout (be sure to "Rebuild Files" after changing the templates for to automatically update your site accordingly). Enjoy doing your log, and thanks for using . =)