4 ms·
> Common approach is to serve static files with nginx and use apache / php_mod to process. Not sure how common that really is, I've personally never set things
by cbg0 7y ago
> Common approach is to serve static files with nginx and use apache / php_mod to process.
Not sure how common that really is, I've personally never set things up like that and just use nginx + php-fpm and don't know anyone that still uses apache with mod_php.
- wolco 7y agoWe went from php_mod to php-fpm but we started moving back to php_mod after php 7 came out showing the benchmarks.
- larzang 7y agoThat's true for us as well with our legacy applications. Our newer applications are using litespeed instead, and we've found it to be significantly better. You basically get the features of a nginx + apache + varnish stack in a single easily managed service and with better performance too.
- locusm 7y agoI think its the default on Plesk installs
- snuxoll 7y agoPlenty of stuff still uses it, unfortunately. Performance is pretty janky, I just moved a Mediawiki install from Apache+mod_php to Nginx+php-fpm as part of getting the site(s) on kubernetes and it’s tremendously better to work with and uses less memory due to not needing mpm_prefork.