De configs die deze sessie zijn nagelopen en gefixt (slpsoftware-analytics.conf, slpsoftware-test-webserver.conf, slpsoftware.conf) stonden alleen als geplakte tekst in de chat en een tijdelijke scratchpad-map, niet in de repo of op de Pi's zelf toegepast. Dit zet ze duurzaam vast als referentiesnapshot, met een README die per bestand aangeeft wat er is aangepast en waarom. Nog steeds handmatig te kopiëren naar de Pi's; niet automatisch gesynchroniseerd. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
44 lines
1.2 KiB
Plaintext
44 lines
1.2 KiB
Plaintext
server {
|
|
|
|
server_name analytics.slpsoftware.nl;
|
|
|
|
error_log /var/log/nginx/slpsoftware-analytics_error.log;
|
|
access_log /var/log/nginx/slpsoftware-analytics_access.log;
|
|
|
|
location /.well-known/acme-challenge/ {
|
|
root /var/www/certbot;
|
|
}
|
|
|
|
location / {
|
|
proxy_pass http://192.168.1.103:3001;
|
|
|
|
proxy_set_header Host $host;
|
|
proxy_set_header X-Real-IP $remote_addr;
|
|
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
|
proxy_set_header X-Forwarded-Proto $scheme;
|
|
}
|
|
|
|
listen 443 ssl; # managed by Certbot
|
|
listen [::]:443 ssl; # managed by Certbot
|
|
ssl_certificate /etc/letsencrypt/live/analytics.slpsoftware.nl/fullchain.pem; # managed by Certbot
|
|
ssl_certificate_key /etc/letsencrypt/live/analytics.slpsoftware.nl/privkey.pem; # managed by Certbot
|
|
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
|
|
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
|
|
|
|
}
|
|
server {
|
|
if ($host = analytics.slpsoftware.nl) {
|
|
return 301 https://$host$request_uri;
|
|
} # managed by Certbot
|
|
|
|
|
|
listen 80;
|
|
listen [::]:80;
|
|
|
|
server_name analytics.slpsoftware.nl;
|
|
|
|
return 404; # managed by Certbot
|
|
|
|
|
|
}
|