I wrote:
The transition is easy.
1) deinstall all your ports(modules) depended on apache13
2) install apache13-modssl.
3) recompile all ports(modules)
You can use apache13-modssl just as a replacment to apache13.
But apache13-modssl uses extrand API, so you have to
culley harrelson wrote:
I am a little shaky in the knees at this prospect. This is on a
production web server getting over 1 million page views per day. I
use
mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other
ports
installed like squirrelmail, mnogosearch, a bunch of
I made the same transition... I had apache13 installed from ports,
and then found myself in need of SSL support.
I didn't uninstall apache13, I simply went to the apache13-modssl port
and typed: make all install clean
No problems. There was a new httpsd.conf file under my /usr/local/etc/apache
The transition is easy.
1) deinstall all your ports(modules) depended on apache13
2) install apache13-modssl.
3) recompile all ports(modules)
You can use apache13-modssl just as a replacment to apache13.
But apache13-modssl uses extrand API, so you have to
recompile all apache modules with
You have complete backups, right? You probably should have a test
server where you can test the software upgrade under non-production
conditions...
Yes of course. I am 1/2 way through a 4 month stint on the road and all
I have is a laptop...
___
I am currently running /usr/ports/www/apache13 and I want to switch to
/usr/ports/www/apache13-modssl. Has anyone make this transition? I
don't know what to expect and I don't have a freebsd test box right now.
I am worried about the ports dependent on apache13-- what happens to
them if I
Don't install it on top of you old installation.
cd /usr/ports/www/apache13
make deinstall
- or -
pkg_delete -f apache-1.3.xx
Then:
cd /usr/ports/www/apache13-modssl
make install clean
make certificate (optional)
Your original httpd.conf won't be deleted. You can use the new one
