Files
Mark HegrebergandChristian Heusel 410f59cb5a apply http_redirect role to our nginx
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>
2026-03-04 00:52:19 +01:00

24 lines
790 B
YAML

- name: Setup HTTP redirect
include_role:
name: http_redirect
vars:
domain: "{{ sources_domain }}"
- name: Set up nginx
template: src=nginx.d.conf.j2 dest=/etc/nginx/nginx.d/sources.conf owner=root group=root mode=0644
notify:
- Reload nginx
tags: ['nginx']
- name: Make nginx log dir
file: path=/var/log/nginx/{{ sources_domain }} state=directory owner=root group=root mode=0755
- name: Make sources dir
file: path={{ sources_dir }} state=directory owner=root group=root mode=0755
- name: Make symlink to repo sources
file: path={{ sources_dir }}/sources src=/srv/ftp/sources state=link owner=root group=root mode=0755
- name: Make symlink to other sources
file: path={{ sources_dir }}/other src=/srv/ftp/other state=link owner=root group=root mode=0755