##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# https://www.nginx.com/resources/wiki/start/
# https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
# https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled/ and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

server {
    listen 80 default_server;
    listen [::]:80;
    server_name loadingm.xyz *.loadingm.xyz;

    location /.well-known/acme-challenge/ {
        root /var/www/certbot;
    }

    # Uncomment to redirect HTTP to HTTPS
    location / {
        return 301 https://$host$request_uri;
    }
}

# Default server configuration
#
server {

	# SSL configuration
	listen 443 ssl default_server;
	listen [::]:443 ssl default_server;
    http2 on;

	server_name loadingm.xyz;

    ssl_certificate /etc/letsencrypt/live/loadingm.xyz/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/loadingm.xyz/privkey.pem;
    # include /etc/letsencrypt/options-ssl-nginx.conf;
    # ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/loadingm.xyz/chain.pem;

	root /data/site;

	location /hosted {
		index index.html; 
		autoindex on;
	}

	location / {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
	}

	# deny access to .htaccess files, if Apache's document root
	# concurs with nginx's one
	#
	#location ~ /\.ht {
	#	deny all;
	#}
}