#34195 [Opn->WFx]: Running PHP 4 and PHP 5 concurrently

From: Date: Wed, 26 Dec 2007 18:36:00 +0000
Subject: #34195 [Opn->WFx]: Running PHP 4 and PHP 5 concurrently
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-377@lists.php.net to get a copy of this message
ID: 34195 Updated by: bjori@php.net Reported By: phpnet at gwaihir dot net -Status: Open +Status: Wont fix Bug Type: Documentation problem Operating System: all PHP Version: Irrelevant New Comment: PHP4 is no longer supported => Wont Fix Previous Comments: ------------------------------------------------------------------------ [2006-03-11 17:09:27] gavin dot phpdoc at mac dot com We could possibly add a section containing a list of resources (links to other pages such as http://ez.no/community/articles/ multiple_apache_installations_howto) on the Installation on Unix Systems page? http://www.php.net/manual/en/install.unix.php ------------------------------------------------------------------------ [2005-08-22 15:41:32] phpnet at gwaihir dot net Oops.. sorry. Apparently missed that bit. Only saw the direct multi-port approach. So, a link to your document from the php.net docs would pretty much be all it takes to fill this hiatus. :) Although.. this approach moves sites (virtual hosts) over as a whole. Would there be a more finegrained way too, allowing an individual user to run some scripts on php4 still while running others on php5 already? I'm thinking towards using .php5 as extention, or a .htaccess directive in a specific folder.. ------------------------------------------------------------------------ [2005-08-22 14:43:34] derick@php.net That's exactly what the document describes - using mod_proxy to proxy through something that only is bind to localhost:8080. Ofcourse, if you have two external IPs you can simply bind each of the apaches to a different IP. ------------------------------------------------------------------------ [2005-08-22 14:23:40] phpnet at gwaihir dot net Derick, of course, if modules are possible that would be best. But while that setup of yours is an excellent one for testing with multiple versions, I don't quite see that work out on a "standard production server" just yet, where for various reasons (mainly firewalls and suspicions) all users will need to be served from port 80. Or is there is some way to internally redirect from one Apache to another? I.e. receive all requests with the Apache on port 80, but redirect some to another internally, with for example an .htaccess on a particular folder. ------------------------------------------------------------------------ [2005-08-20 22:07:47] derick@php.net I think that running as CGI is quite suboptimal. I prefer to run two different apache setups. Some info on that is here: http://ez.no/community/articles/multiple_apache_installations_howto ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/34195 -- Edit this bug report at http://bugs.php.net/?id=34195&edit=1

« previous php.doc.bugs (#377) next »