On Sunday 22 June 2003 11:37, George Clark wrote:
> ** Reply to message from shane <shane@...> on Thu, 12 Jun 2003
> 18:21:46 -0400
> Hi all,
> In prep for the latest slashcode tags, I want to upgrade to mysql 4.
> At these reasonably current releases, should it really be as simple as
> running the apt-get upgrade? Any traps I should be aware of? Any other
> suggestions? (I know... I really ought to match a test system to my
> production system <g>)
I was working on doing this a few weeks ago. I have 2 identical boxes, one's
the production website, one's the dev website.
mysql 3.x was installed from source.
I shutdown apache, slashd, mysql, and other misc software on the dev box. Then
installed the binary of mysql4 (these are redhat machines. Krow had
recommended using either binary or rpm, but *not* src to install).
Anyway, after upgrading, I grabbed Slash's latest CVS, installed. It didn't
work. I had to update some modules from CPAN. So I did that. Ran
install-slashsite, made a new site. Took a db backup from the previous
evening from a production website, restored to this site's new db. Changed
hostname/etc info in db. Fired up slashd & httpd.
No problems what-so-ever.
The only thing that was recommended to me was to rebuild the full text
indexes, which I've unfortunately been too busy to do. if anyone's done this,
if you have the sql handy to do it, can you share it with us all? If not,
after I get around to doing it I'll post it somewhere.