mirror of
https://gitlab.archlinux.org/archlinux/infrastructure.git
synced 2026-09-19 16:41:12 +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>
21 lines
593 B
Django/Jinja
21 lines
593 B
Django/Jinja
include snippets/redirect-80.conf;
|
|
|
|
server {
|
|
include snippets/listen-443.conf;
|
|
server_name {{ bumpbuddy_domain }};
|
|
|
|
access_log /var/log/nginx/{{ bumpbuddy_domain }}/access.log main;
|
|
access_log /var/log/nginx/{{ bumpbuddy_domain }}/access.log.json json_main;
|
|
error_log /var/log/nginx/{{ bumpbuddy_domain }}/error.log;
|
|
|
|
acme_certificate letsencrypt;
|
|
ssl_certificate $acme_certificate;
|
|
ssl_certificate_key $acme_certificate_key;
|
|
|
|
root /opt/bumpbuddy/web;
|
|
|
|
location = /data.json {
|
|
alias /opt/bumpbuddy/data/data.json;
|
|
}
|
|
}
|