1
1
mirror of https://gitlab.archlinux.org/archlinux/infrastructure.git synced 2026-03-07 06:41:39 +01:00
infrastructure/roles/proxy_test/tasks/main.yml
Kristian Klausen 0991324392
Switch to nginx native ACME[1] where it makes sense
It provides a better UX compared to certbot and is one less moving part.

The switch is done where it is possible and sensible. That is basically
all the places where nginx is the sole user of the certificate.

Certificates using the DNS-01 challenge (e.g. geo mirrors) or which are
used with stream (e.g. rsync over TLS) still require certbot as it is
currently not supported in the native integration[2][3].

[1] https://blog.nginx.org/blog/native-support-for-acme-protocol
[2] https://github.com/nginx/nginx-acme/issues/11
[3] https://github.com/nginx/nginx-acme/issues/13
2025-12-23 19:46:18 +01:00

12 lines
417 B
YAML

- name: Copy static page
copy: src=index.html dest=/srv/http/test owner=root group=root mode=0644 directory_mode=0755
- name: Make nginx log dir
file: path=/var/log/nginx/{{ public_domain }} state=directory owner=root group=root mode=0755
- name: Set up nginx
template: src=nginx.d.conf.j2 dest=/etc/nginx/nginx.d/proxy_test.conf owner=root group=root mode=0644
notify:
- Reload nginx
tags: ['nginx']