I notice that Coral 8.8.8 has been released, and I thought I'd take advantage to upgrade my old 8.0.0 setup.

 

I remember that back when I installed 8.0.0 over an old 7.x.x setup, there were many questions in the forum about how to run a simple upgrade and, back then, there were some suggestions about renaming directories, reinstalling, and copying across various configuration files (but no definitive list of which files to keep).

 

It seems that it's much the same story, still, which is a pity because, with a simple and intelligent upgrade procedure it seems to me that Uniform server would be easily the best WAMP setup around.

 

The reason that I prefer to use a pre-rolled WAMP setup, rather than to install Apache, MySQL and PHP seperately, is precisely because I don't know enough about the interactivity between the three tools to be confident of maintaining my own home-grown and secure setup. It would therefore be excellent if Uniform Server could detect existing installations of itself, and update the various binaries while keeping the config settings. As it is, I essentially end up re-configuring Apache, my virtual servers, MySQL and PHP each time...

 

At the very least, a clear and concise 'How To Upgrade' wiki page would be really cool.

Unfortunately, I have to agree with you on this point. The problem is that that approach ("automated update") needs to take into account many, many possible changes to the configurations, as well as the security situation. If we had the income and number of developers that WordPress has (or even 1%), it would be possible to do this.

 

I guess that's part of the impetus behind Series Zero, which is a "put-the-pieces-together" approach. It still doesn't auto-update, but I think we're headed in that direction. At least that's my impression.

 

Still, the best way to update right now is to install the new version, port your apps over, change the config variables to match your old installation, and then test.

 

Regards.

BobS

Thanks BobS

 

Series Zero is new since I last looked at Uniform - what does it do? In what way is it easier to update?

 

Do you think it would be useful, if only as a start point, to document in the Wiki, or as a sticky in the forums, the configuration files that probably should be kept between one 'fairly vanilla' install and another?

 

For example (and this is a largely ignorant shot-in-the-dark):

 

- stop and uninstall UniServer services

- back up your www directory (or directories if you have more than one, e.g. in the case of virtual hosts)

- rename UniServer directory (e.g. to UniServer_old or UniServer_yyyymmmdd ...)

- install the new UniServer package (i.e. copy the UniServer directory out of the zip, to the place where the previous one was before you renamed it)

- copy your old apache configuration from UniServer_old\usr\local\apache2\conf\httpd.conf to UniServer\usr\local\apache2\conf\httpd.conf

- copy your old mysql databases from UniServer_old\usr\local\mysql\data\* to UniServer\usr\local\mysql\data\*

- copy your old PHP config file from UniServer_old\usr\local\php\php.ini to UniServer\usr\local\php\php.ini

 

...?

 

I have the energy to write some kind of HOWTO, but lack sufficiently in-depth knowledge to make it watertight.

 

Cheers

 

Charlie