tanshu
2ef044aa45
Reverts the explicit subnets: the pools were freed by deleting five networks, so the network role is back to its single idempotent task - ensure the network exists and Caddy is on it - and the Sites no longer declare a subnet. The deployment readme keeps the note that a new Site needs a config, and therefore a new tag, but no longer asks for a free /24. If the pools fill up again the failure is recognisable: 'all predefined address pools have been fully subnetted', and the choices are deleting stale networks or declaring a subnet per Site.
21 lines
524 B
YAML
21 lines
524 B
YAML
---
|
|
# Defaults shared by every Site. Each Site's own file is named by the `var_file`
|
|
# in ansible/hosts, and its slug is its inventory name.
|
|
|
|
# Which Site config inside the image to run, and which web address it serves.
|
|
site: '{{ inventory_hostname }}'
|
|
|
|
image_name: registry.tanshu.com/menu-admin
|
|
image_tag: "{{ tag | default('latest') }}"
|
|
|
|
app_uid: 1000
|
|
app_gid: 1000
|
|
|
|
caddy_container: caddy
|
|
caddyfile_path: /var/lib/caddy/conf/Caddyfile
|
|
|
|
caddy_snippet: |
|
|
{{ host }} {
|
|
reverse_proxy {{ docker_container }}:3000
|
|
}
|