These instructions are truly wonderful. I feel I'm close to actually being able to do this. However, I'm having newbie installation problems and feel that I'm staring at the problem but can't see it. I know a tiny bit of Unix (the same tiny bit I've known since 1991, which technically makes me a slowbie, not a newbie). I've stepped through everything twice (include completely deleting everything and starting over again) and am scratching my head.
Perhaps I am reading the steps wrong or making some hilarious newbie error. I'll step you through my actions and the results:
Connect to wombatnation.com using ssh and cd into wombatnation.com directory
tar -xvf MT-2.5-full-lib.tar
O.k., I did this, but of course ssh into my own account and cd into my own bluehighways.com directory, and
gunzip MT-2.64-full-lib.tar.gz , then
tar -xvf MT-2.64-full-lib.tar
I see files fly by when I do the latter. So far so good--I assume.
Next, I followed these steps (again, working from the bluehighways.com directory, and with MT-2.64-full-lib ).
mv MT-2.5-full-lib mt
At this point, MT* is in the "mt" directory, and I am in the mt directory, as well, having just cd'ed there.
Just to be sure, I even list files, and see the MT* directory listed:
[salt]$ mv MT-2.64-full-lib mt
[salt]$ cd mt
[salt]$ ls MT-2.64-full-lib
Here's the first manifestation of whatever problem I've created with my previous actions:
"Edit Main Config and Password File"
(Note: I use pico, not emacs, but I'm assuming the editor is irrelevant, just as I am pretty sure we're not discussing a permissions or file-upload-corruption problem.)
Hmm. I am still in the bluehighways.com/mt directory, and I don't see an mt.cfg file. I know there is one in the underlying MT* directory, but perhaps I don't understand how "libraries" work and when I start editing it will magically appear.
oops... I'm not editing an existing mt.cfg file, like the instructions show; it's a brand-new file that pico helpfully started for me. That's not right. Hmm... let me verify that the mt.cfg file is where I thought it was anyway.
[salt]$ ls -al
drwxr-xr-x 3 kgs pg98513 4096 Jul 22 15:00 .
drwxr-xr-x 4 kgs pg98513 4096 Jul 22 15:00 ..
drwxr-xr-x 10 kgs pg98513 4096 Jul 22 15:00 MT-2.64-full-lib
O.k., that's a directory; I'll peek in it. Sure enough, the files are in here:
[salt]$ cd MT*
[salt]$ ls -al
drwxr-xr-x 10 kgs pg98513 4096 Jul 22 15:00 .
drwxr-xr-x 3 kgs pg98513 4096 Jul 22 15:00 ..
-rw-r--r-- 1 kgs pg98513 9261 Jun 5 00:16 LICENSE
Well, maybe the instructions REALLY mean I should edit the files inside this directory. So I do all that. For CGIPath, I specify http://www.bluehighways.com/mt in mimicry of these instructions:
Change value of CGIPath to http://www.wombatnation.com/mt/
Even though at this point I'm feeling uneasy. Still, I enter all the particulars and I make all the recommended changes (ObjectDriver, etc.), and modify the password file. Naturally, for mt.cfg, I use the db, db user, etc. that I have created (and later on I connect just fine to MySQL using the format "mysql -h host -u user - p db" which tells me that I am correctly naming the db, the user, the password, etc.).
I do the recommended permissions changes and then attempt the "sanity check of Perl install." The first time I tried this, in IE, it just hung (and then I tried mt-load.cgi, and that really threw a wrench in the works--everything froze and I couldn't even log into my shell for a while), so why not try good old lynx?
[salt]$ lynx http://www.bluehighways.com/mt/mt-check.cgi
Oh oh. 404. Well, everything else seems to be in that "other" directory, anyway.
So I try this:
Hey, it works! q.v.:
Current working directory: /home/.icarian/kgs/bluehighways.com/mt/MT-2.64-full-lib
Operating system: linux
Perl version: 5.6.1
At this point, I stop; I could go on and try mt-load.cgi, but then, I'm guessing, mt.cfg would need to be edited to change the CGIPath, and something tells me this isn't right.
So just for kicks and grins, let's see if the index.html file that MT provides displays o.k. from the Web, and from what directory:
And the Movable Type index page in this directory displays just fine.
So who wants to point out the Obvious Error(s)? I've got a clean reinstall to work from, so I can take it from the top.