Files
nginx/sites-available/schleppecloud.config

82 lines
2.4 KiB
Plaintext

#
# 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.
##
# Default server configuration
# Default should define all the routes to upgrade to https and global rules!
server {
listen 443;
listen [::]:443;
server_name schleppe.cloud;
location / {
root /usr/share/nginx/schleppecloud/;
autoindex off;
index index.html;
}
ssl_certificate /etc/letsencrypt/live/schleppe.cloud/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/schleppe.cloud/privkey.pem; # managed by Certbot
}
server {
listen 443 http2;
listen [::]:443 http2;
server_name blockchain.schleppe.cloud;
location / {
root /home/kevin/blockchain;
autoindex off;
index index.html;
}
ssl_certificate /etc/letsencrypt/live/blockchain.schleppe.cloud/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/blockchain.schleppe.cloud/privkey.pem; # managed by Certbot
}
server {
listen 443 http2;
listen [::]:443 http2;
server_name wagovipps.schleppe.cloud;
# gzip on;
# gzip_min_length 1000;
# gzip_types text/plain application/json;
# TODO restrict to allow vipps servers
location / {
proxy_http_version 1.1;
add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, OPTIONS';
add_header 'Access-Control-Allow-Headers' 'Content-Type';
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
proxy_pass http://10.0.0.58:80;
}
ssl_certificate /etc/letsencrypt/live/wagovipps.schleppe.cloud/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/wagovipps.schleppe.cloud/privkey.pem; # managed by Certbot
}