php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #34195 Running PHP 4 and PHP 5 concurrently
Submitted: 2005-08-20 14:55 UTC Modified: 2007-12-26 18:35 UTC
Votes:2
Avg. Score:3.5 ± 0.5
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (100.0%)
From: phpnet at gwaihir dot net Assigned:
Status: Wont fix Package: Documentation problem
PHP Version: Irrelevant OS: all
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: phpnet at gwaihir dot net
New email:
PHP Version: OS:

 

 [2005-08-20 14:55 UTC] phpnet at gwaihir dot net
Description:
------------
This much needed bit of documentation is missing. It may not work the 3 -> 4 way, but A way is badly needed to get major hosts to start the transition period. After all, expecting folk to just "flip the switch" on a production machine just isn't realistic (nor would it get PHP a good rep).

So, I hear it can be done by adding php5 as CGI (initially). Can you write down how?

It would be even better of course, if some folk subsequently went out and familiarized some of the major hosting panel makers (such as CPanel) on how to make it part of their software..


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-08-20 22:07 UTC] 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
 [2005-08-22 14:23 UTC] 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-22 14:43 UTC] 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 15:41 UTC] 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..
 [2006-03-11 17:09 UTC] 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
 [2007-12-26 18:35 UTC] bjori@php.net
PHP4 is no longer supported => Wont Fix
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Oct 31 22:01:27 2024 UTC