Discussion:
Running multiple versions of PHP under Apache
David Suna
2014-08-25 20:24:40 UTC
Permalink
_______________________________________________
Linux-il mailing list
Linux-il-NSemkxREmS1YZAO8hgG6+***@public.gmane.org
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
E.S. Rosenberg
2014-08-25 22:43:09 UTC
Permalink
I have a Debian Wheezy machine two virtual hosts configured on a single
machine. One requires PHP 5.3 and the other requires PHP 5.4+. I am trying
to set up the machine to allow both to run.
So far I have added php-fpm (fastcgi) as per
https://www.linode.com/docs/websites/apache/running-fastcgi-php-fpm-on-debian-7-with-apache
.
This site (
http://www.howtoforge.com/how-to-use-multiple-php-versions-php-fpm-and-fastcgi-with-ispconfig-3-debian-wheezy)
talks about using ISPConfig 3 for this. I have downloaded and compiled the
5.3 version of PHP but using ISPConfig seems to be a big headache.
From http://thejibe.com/blog/14/02/phpfarm it would seem like I should be
able to have the configuration done within the virtualhost directives but
that page seems to be out of date and I didn't follow all of the changes
being suggested.
The page is barely a half year old and a quick scan seems to be that it is
in the right direction, it is using what you yourself were also
considering: fastcgi.
Is it possible to use fpm pools to reference different PHP versions?
What are my other options for having two virtual hosts using different PHP
versions on the same machine?
A very far fetched and convoluted way would be to run nginx with fastcgi
and specific php versions on different ports and modrewrite certain
paths/urls to it....
HTH,
Eliyahu - אליהו
Thanks
--
_______________________________________________
Linux-il mailing list
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
David Suna
2014-08-26 12:27:08 UTC
Permalink
_______________________________________________
Linux-il mailing list
Linux-il-NSemkxREmS1YZAO8hgG6+***@public.gmane.org
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
E.S. Rosenberg
2014-08-26 12:46:06 UTC
Permalink
Thanks for the response.
I have a Debian Wheezy machine two virtual hosts configured on a single
machine. One requires PHP 5.3 and the other requires PHP 5.4+. I am trying
to set up the machine to allow both to run.
So far I have added php-fpm (fastcgi) as per
https://www.linode.com/docs/websites/apache/running-fastcgi-php-fpm-on-debian-7-with-apache
.
This site (
http://www.howtoforge.com/how-to-use-multiple-php-versions-php-fpm-and-fastcgi-with-ispconfig-3-debian-wheezy)
talks about using ISPConfig 3 for this. I have downloaded and compiled the
5.3 version of PHP but using ISPConfig seems to be a big headache.
From http://thejibe.com/blog/14/02/phpfarm it would seem like I should
be able to have the configuration done within the virtualhost directives
but that page seems to be out of date and I didn't follow all of the
changes being suggested.
The page is barely a half year old and a quick scan seems to be that it is
in the right direction, it is using what you yourself were also
considering: fastcgi.
The page seems out of date as I checked the compile time options it showed
for PHP and many of the options are for older versions of PHP that are no
longer relevant as of PHP 5. Based on what I have read, including on this
page, fastcgi is the way to go. I have compiled the other version of PHP
and added fastcgi. My problem is that I don't have the last step of how to
configure fastcgi to allow different versions of PHP to be used by
different virtual hosts.
Could be the guy used his old compile time settings and as long as the
compiler doesn't bark at you most people will reuse the same settings every
time...
A very far fetched and convoluted way would be to run nginx with fastcgi
and specific php versions on different ports and modrewrite certain
paths/urls to it....
I am trying to keep to Apache as the web server.
Yes you have apache as the server and an nginx+fcgi+php instance doing the
actual php parsing, it's a backwards and over the top solution for when
nothing else works and you should be able to get away with not going to
such an extreme.
Basically it has apache working as a reverse proxy in front of nginx.
Regards,
Eliyahu - אליהו
--
Loading...