mirror of
https://gitlab.archlinux.org/archlinux/infrastructure.git
synced 2026-09-19 07:39:13 +02:00
Mark HegrebergandChristian Heusel
410f59cb5a
these are all the systems that the new redirect snippet can be cleanly applied to. there are a few others not included, that will need a more manual approach: - gitlab (multiple domains) - mta.sts(multiple domains) - archweb(mutltiple domains, snippets) - buildbtw(dynamic dev domains) - redirects(different structure) - public html(multiple domains) - archweb maintenence(different structure) - maintenence(different structure) some of these might be solvable by tweaking the snippet to accept multiple domains. I'll look into this Co-authored-by: Christian Heusel <christian@heusel.eu>
34 lines
887 B
Django/Jinja
34 lines
887 B
Django/Jinja
include snippets/redirect-80.conf;
|
|
|
|
server {
|
|
include snippets/listen-443.conf;
|
|
server_name {{ debuginfod_domain }};
|
|
|
|
access_log /var/log/nginx/{{ debuginfod_domain }}/access.log reduced;
|
|
access_log /var/log/nginx/{{ debuginfod_domain }}/access.log.json json_reduced;
|
|
error_log /var/log/nginx/{{ debuginfod_domain }}/error.log;
|
|
|
|
acme_certificate letsencrypt;
|
|
ssl_certificate $acme_certificate;
|
|
ssl_certificate_key $acme_certificate_key;
|
|
|
|
root /srv/http/debuginfod;
|
|
index index.html;
|
|
|
|
location / {
|
|
try_files $uri $uri/ @debuginfod;
|
|
}
|
|
|
|
location = /packages {
|
|
default_type "text/plain";
|
|
}
|
|
|
|
location @debuginfod {
|
|
proxy_set_header X-Forwarded-For $remote_addr;
|
|
proxy_pass http://127.0.0.1:8002;
|
|
|
|
gzip_comp_level 1;
|
|
gzip_types application/octet-stream;
|
|
}
|
|
}
|