This merge updates the existing traefik and nos_social roles so that the resulting service fits the requirements outlined in #66 .
It modifies traefik to use cloudflare dns-challenges for it's certresolver, instead of a single-file http challenge. This allows for arbitrary wildcard domains. It also configures traefik to create certificates for {{ domain }} and *.{{ domain }}.
On the nos.social side, there are several updates to the docker compose:
adding a redis service, with a persistent docker volume
updating the routes to direct traffic to the api, webflow, or the traefik dashboard accordingly,
refining the rules and tasks to be more succinct.
The host rules in the docker compose are quite verbose. This has two advantages: a blunt clarity (hopefully), and an built-in priority. Traefik sets priority based on the length of the rule, so we check to see if the traffic should be handled by the api first before redirecting to the webflow site. I will likely revisit this though to see if i can say this more clearly and briefly.
dcadenas
commented
5 months ago
This merge updates the existing traefik and nos_social roles so that the resulting service fits the requirements outlined in #66 .
It modifies traefik to use cloudflare dns-challenges for it's certresolver, instead of a single-file http challenge. This allows for arbitrary wildcard domains. It also configures traefik to create certificates for
{{ domain }}and*.{{ domain }}.On the nos.social side, there are several updates to the docker compose:
The host rules in the docker compose are quite verbose. This has two advantages: a blunt clarity (hopefully), and an built-in priority. Traefik sets priority based on the length of the rule, so we check to see if the traffic should be handled by the api first before redirecting to the webflow site. I will likely revisit this though to see if i can say this more clearly and briefly.