Any of you good people out there have extensive experience administering LOTS of php versions (on the same host)? If so could you take a moment to share some of your methods to managing multiple versions of an apache+php+ssl installation? I am currently working towards a scenario with multiple versions, simulatenously. It is begining to look something like this, with different directory hierarchies for each new version of a component. I figure that a symlink with a "basename" like "ssl" will point to the current version.
/usr/local/apache -> apache-1.3.22/ /usr/local/apache-1.3.22/ /usr/local/apache-1.3.23/ /usr/local/bin/ /usr/local/doc/ /usr/local/etc/ /usr/local/include/ /usr/local/lib/ /usr/local/libexec/ /usr/local/man/ /usr/local/openssl-0.9.6b/ /usr/local/openssl-0.9.6c/ /usr/local/postgresql -> postgresql-7.1.3/ /usr/local/postgresql-7.1.3/ /usr/local/sbin/ /usr/local/share/ /usr/local/src/ /usr/local/ssl -> openssl-0.9.6b/ I want to be able to have a "current version" of a php installation operating normally, while building/testing newer versions. I need a way to manage each instantiation of apache+php as DSO. I assume this will require running the new versions which are being tested via a different http port number so as not to conflict with the installation on port 80. That is simple... Can folks suggest other specific configuration ideas and file system topologies that will make this really easy? Than you very much! If people choose to not prepare an item for posting and want to simplly e-mail their notes to me, then I will post a summary... thx dk -- PHP Install Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
