4c732aa5d6
although most much of use case developer should modify laradock to suit their project. we can use *.conf.example to take effect. but we also need a dummy nginx conf to info other newer to know how to config their nginx conf. the *.conf.example should be. so i think we should only take *.conf to take effect. not *
35 lines
1.3 KiB
Nginx Configuration File
35 lines
1.3 KiB
Nginx Configuration File
user www-data;
|
|
worker_processes 4;
|
|
pid /run/nginx.pid;
|
|
daemon off;
|
|
|
|
events {
|
|
worker_connections 2048;
|
|
multi_accept on;
|
|
use epoll;
|
|
}
|
|
|
|
http {
|
|
server_tokens off;
|
|
sendfile on;
|
|
tcp_nopush on;
|
|
tcp_nodelay on;
|
|
keepalive_timeout 15;
|
|
types_hash_max_size 2048;
|
|
client_max_body_size 20M;
|
|
include /etc/nginx/mime.types;
|
|
default_type application/octet-stream;
|
|
access_log /dev/stdout;
|
|
error_log /dev/stderr;
|
|
gzip on;
|
|
gzip_disable "msie6";
|
|
|
|
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
|
|
ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS';
|
|
|
|
include /etc/nginx/conf.d/*.conf;
|
|
include /etc/nginx/sites-available/*.conf;
|
|
open_file_cache off; # Disabled for issue 619
|
|
charset UTF-8;
|
|
}
|