Difference between revisions of "PHP-FPM"
Jump to navigation
Jump to search
(more relevant doc links) |
(diagnosis path) |
||
Line 24: | Line 24: | ||
==Notes== | ==Notes== | ||
* [[User:Woozle/nginx]]: trying to repair a borked [[PHP-FPM]] installation | * [[User:Woozle/nginx]]: trying to repair a borked [[PHP-FPM]] installation | ||
+ | ** The connection chain seems to go like this: [web server] <=:FastCGI:=> [PHP-FPM] <=> [php] | ||
+ | ** You can problem-isolate by removing PHP-FPM from the chain: [web server] <=:FastCGI:=> [php-cgi] | ||
+ | *** If PHP still doesn't respond to web requests, you can see what the web server is sending by running [[User:Woozle/port listener|this script]]. | ||
+ | **** FastCGI can connect via a [[UNIX pipe]] or a network port, but the above code is written for a port. |
Latest revision as of 20:34, 24 June 2012
About
PHP-FPM is a process manager for PHP. It is useful as part of the interface between PHP and the web server software (WSS), especially when the WSS does not have an option to integrate directly with PHP.
Common Uses
Links
- official site
- current documentation (on the official PHP site)
- nginx documentation:
- Tutorials:
Notes
- User:Woozle/nginx: trying to repair a borked PHP-FPM installation
- The connection chain seems to go like this: [web server] <=:FastCGI:=> [PHP-FPM] <=> [php]
- You can problem-isolate by removing PHP-FPM from the chain: [web server] <=:FastCGI:=> [php-cgi]
- If PHP still doesn't respond to web requests, you can see what the web server is sending by running this script.
- FastCGI can connect via a UNIX pipe or a network port, but the above code is written for a port.
- If PHP still doesn't respond to web requests, you can see what the web server is sending by running this script.