Hi,

little summary:

1. start php-fpm
2. point yaws to the ip:port of the php-fpm process (you cant use sockets, so you need to change config of php-fpm to listen on port)
3. maybe whine because you cant use .htaccess files


As most php apps today are based of single index.php files, you maybe want to use something like my error_mod, which redirects not found paths first to the php script:
https://github.com/Flyingmana/cookbooks/blob/master/yaws/files/default/yaws_fcgi_404_to_index_php.erl
actually I missused things a bit, as I did use the first solution I got working.
Also you need to care about securing directories for older applications.

The sure way to tell how php is running is via the phpinfo()


coming from apache you first need to learn, that php-fpm runs as a complete independent process from the webserver and has its own worker management.

Hope it helps, if you have more specific questions, just continue writing to the list.





2014-04-07 21:22 GMT+02:00 Ian <yaws@poetmail.net>:
Thanks for the quick reply, but it seems I'm confused.

I've installed php5-fpm but it doesn't seem to have made any difference.

In fact I haven't found a sure way to tell whether PHP is running as
plain CGI or FastCGI.

Sorry, I'm used to using it as a module under Aparche.



------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list