Barazo Docker Compose templates for self-hosting barazo.forum

fix(caddy): add docs.barazo.forum site block (#68)

The docs site was deployed to /var/www/docs.barazo.forum/ via CI but
Caddy was never configured to serve it, causing TLS handshake failures.
Add a static file server block and bind-mount the directory into the
Caddy container.

authored by

Guido X Jansen and committed by
GitHub
72f480a1 0dba53a5

+13
+12
Caddyfile
··· 12 12 admin off 13 13 } 14 14 15 + # --------------------------------------------------------------------------- 16 + # Documentation site (static export served from /var/www/docs.barazo.forum/) 17 + # --------------------------------------------------------------------------- 18 + docs.barazo.forum { 19 + header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" 20 + 21 + root * /var/www/docs.barazo.forum 22 + file_server 23 + 24 + try_files {path} {path}index.html /404.html 25 + } 26 + 15 27 {$COMMUNITY_DOMAIN} { 16 28 # HSTS -- enforce HTTPS for all future requests (2 years, preload-eligible) 17 29 header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
+1
docker-compose.yml
··· 187 187 - ./Caddyfile:/etc/caddy/Caddyfile:ro 188 188 - caddydata:/data 189 189 - caddyconfig:/config 190 + - /var/www/docs.barazo.forum:/var/www/docs.barazo.forum:ro 190 191 networks: 191 192 - frontend 192 193 depends_on: