| add_action( 'init', function(){ | |
| if ( ! is_admin()) { | |
| if( is_ssl() ){ | |
| $protocol = 'https'; | |
| }else { | |
| $protocol = 'http'; | |
| } | |
| /** @var WP_Scripts $wp_scripts */ | |
| global $wp_scripts; |
| { | |
| "Airline": "Airline Industry Services", | |
| "American Restaurant": "New American Restaurant", | |
| "Amusement Park Ride": "Roller Coaster", | |
| "Amusement": "Arcade", | |
| "Amusement": "Bingo Hall", | |
| "Amusement": "Go Karting", | |
| "Amusement": "Laser Tag", | |
| "Antiques & Vintage": "Antique Store", | |
| "Antiques & Vintage": "Auction House", |
| user web; | |
| # One worker process per CPU core. | |
| worker_processes 8; | |
| # Also set | |
| # /etc/security/limits.conf | |
| # web soft nofile 65535 | |
| # web hard nofile 65535 | |
| # /etc/default/nginx |
By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk.
This process is outlined at the Nginx ngx_http_fastcgi_module page manual page.