Very Computer

by **dataweaver_onl..** » Fri, 03 Nov 2000 19:18:44

I have been using apache for some time now and I
find that in order to get a working build complied from source I have
to remove everything that I had from the previous version that includes
anything that refers to the previous version ..
ie i have to move all my sites and rm the directories any traces of the
previous version ie
..lib/apache, etc.. my previous ..httpd/conf directory plus possibly
the htpasswd file. I usually compile to my own directory structure for
document root plus use the options for max modules included. I find
this really iritating as I have to effectively disable my sites for a
long time in order to upgrade to a newer version of apache. Am I doing
something wrong?? what is the accepted wisdom on seamless upgrades??

Sent via Deja.com http://www.deja.com/
Before you buy.

by **steve** » Sat, 04 Nov 2000 20:15:48

> I have been using apache for some time now and I
> find that in order to get a working build complied from source I have
> to remove everything that I had from the previous version that
includes
> anything that refers to the previous version ..
> ie i have to move all my sites and rm the directories any traces of
the
> previous version ie
> ..lib/apache, etc.. my previous ..httpd/conf directory plus possibly
> the htpasswd file. I usually compile to my own directory structure for
> document root plus use the options for max modules included. I find
> this really iritating as I have to effectively disable my sites for a
> long time in order to upgrade to a newer version of apache. Am I doing
> something wrong?? what is the accepted wisdom on seamless upgrades??

You can't have a seamless upgrade since you have to stop one daemon in
order for another to bind to the same port. But it's not as hard as it
initially seems ...

I usually have a couple of apache directories, say
/opt/apache/apache_1.3.12/, /opt/apache/apache_1.3.14/ etc, and symlink
/opt/apache/apache/ to whichever version I want to run. There's no
reason you can't point your DocumentRoot to wherever you like and flick
between server versions, as long as your config supports whatever
content you're serving. Perhaps other people have other ways of doing it
but I find this quite clean and simple, as you can easily see which
versions are available and which is currently running.

--
steven

Sent via Deja.com http://www.deja.com/
Before you buy.

by **steve** » Sat, 04 Nov 2000 20:36:54

Quote:> I usually have a couple of apache directories, say
> /opt/apache/apache_1.3.12/, /opt/apache/apache_1.3.14/ etc, and
symlink
> /opt/apache/apache/ to whichever version I want to run. There's no
> reason you can't point your DocumentRoot to wherever you like and
flick
> between server versions, as long as your config supports whatever
> content you're serving. Perhaps other people have other ways of doing
it
> but I find this quite clean and simple, as you can easily see which
> versions are available and which is currently running.

I forgot to add, if you want to test the configuration of a new version
just run the server off of another port.

--
steven

Sent via Deja.com http://www.deja.com/
Before you buy.

Very Computer

Upgrading Apache concerns

Upgrading Apache concerns

Upgrading Apache concerns

Upgrading Apache concerns