9 Commits

Author SHA1 Message Date
027a43ddbe
roles/caddy: use default for encode 2025-03-29 22:49:30 +03:00
22c16e1ed3
roles/caddy/templates: closer to supporting WordPress
I still wouldn't want to deploy WordPress on Caddy until it's more
obvious and standard to block paths that shouldn't be accessible.
It seems that this is still left as an exercise to the site admin.

This discussion has some tips, but it is four years old and hasn't
changed since I last looked.

See: https://caddy.community/t/using-caddy-to-harden-wordpress/13575
2025-03-29 22:09:37 +03:00
84db337fea
roles/caddy: smarter setting of document root 2025-03-29 19:33:02 +03:00
7b23f5f94f
roles/caddy: add missing tag 2025-03-29 19:16:03 +03:00
9830338be3
Use one default root prefix for nginx and caddy 2025-03-29 19:15:56 +03:00
e3eed26765
roles/caddy: update vhost template 2025-03-29 18:37:28 +03:00
06416a3b64
roles: run ansible-lint --write 2023-08-23 22:22:51 +03:00
c840ffe018
roles/caddy: improve vhost template
Support domain aliases that redirect to the main domain and allow
sites to say they are static sites where they only need a document
root.
2022-11-13 18:54:03 +03:00
4867d6da6a
Add basic caddy role 2022-11-02 22:29:30 +03:00