yii2 - 如何配置NGINX+多个版本PHP么?
去年服务器和PHP弄得不好,公司里面最近的PHP程序员都离职了,我来挑大梁。
我基于YII 2,SVN,RSYNC配置了一套持续集成环境,弄之前就知道YII要PHP5.4以上,但弄完后才发现公司的老代码100%是PHP5.3,不可能全套迁移过了。
原本打算有9台服务器上PHP 5.6,今天再一想,为什么原来的8台服务器还要PHP 5.3呢?我不如每台服务器都NGINX+两套PHP环境,这样的话,新老代码都可以使用了。
有谁搞过的么?
我找到一个参考的。http://jingyan.baidu.com/article/a948d6517c63e60a2dcd2e39.html
请指正,谢谢。
回复内容:
去年服务器和PHP弄得不好,公司里面最近的PHP程序员都离职了,我来挑大梁。
我基于YII 2,SVN,RSYNC配置了一套持续集成环境,弄之前就知道YII要PHP5.4以上,但弄完后才发现公司的老代码100%是PHP5.3,不可能全套迁移过了。
原本打算有9台服务器上PHP 5.6,今天再一想,为什么原来的8台服务器还要PHP 5.3呢?我不如每台服务器都NGINX+两套PHP环境,这样的话,新老代码都可以使用了。
有谁搞过的么?
我找到一个参考的。http://jingyan.baidu.com/article/a948d6517c63e60a2dcd2e39.html
请指正,谢谢。
开启多个php-fpm,phpfpm的版本可以不同,绑定不同的sock或者port。
nginx按照条件将php请求转发到不同的sock或者port。
可以的.让不同版本的php-fpm运行在不同端口,然后ngxin按照路径反带到不同的upstream就好.
发一个我的配置文件,感觉稍微修改一下,应该可以满足到楼主
CMD启动PHP和Nginx的脚本,增加多几个版本的php-cgi,端口不一样
<code>@ECHO OFF set PHP_FCGI_MAX_REQUESTS=1000 echo Starting php-cgi RunHiddenConsole php\php-cgi.exe -b 127.0.0.1:9000 -c config\php_5.5.ini -i echo Starting nginx cd nginx start nginx EXIT </code>
然后在Nginx的配置文件里面,指定不同的应用给不同端口的PHP-CGI
<code> location ~ ^/phpPgAdmin/(.*\.php)$ { alias D:/Work/www/tools/phpPgAdmin/$1; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_pass 127.0.0.1:9000; include fastcgi_params; } </code>
采纳了一个答案,但还是自己搞了,因为我用的是LNMP,然后改的unix_sock
今天测试的时候遇到一个新的问题。
我同一台物理服务器上面有NGINX+PHP 5.6.6和PHP5.3.28,通过unix_sock来分开
两个PHP都能跑,但PHP5.3.28在跑某一个页面(JQUERY MOBILE+PHP)的时候,页面只加载了一半,看LOG都正常。换一台服务器,只有一个PHP5.3,可以正常运行出来。
奇怪,检查PHP和JQEURY代码完全一样。
把正常运行的INI文件复制过来,重启几遍NGINX和PHP,还是只出来一半。
有谁遇到过么?
遇到过相同问题
同求答案啊

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

The methods to view the running status of Nginx are: use the ps command to view the process status; view the Nginx configuration file /etc/nginx/nginx.conf; use the Nginx status module to enable the status endpoint; use monitoring tools such as Prometheus, Zabbix, or Nagios.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
