Currently the following is how this recipe deploys:
/deploy: triggers webhookd to re-build the site, includes publicly viewable logs
We by default should tuck that /deploy path behind an HTTP Basic Auth.
Currently the following is how this recipe deploys:
> /deploy: triggers webhookd to re-build the site, includes publicly viewable logs
We by default should tuck that `/deploy` path behind an HTTP Basic Auth.
I could merge https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/branch/main/compose.auth.yml into the default `compose.yml`? The result is that it'll be required to `secret generate` before you deploy, which is an extra step. If all good, can do that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently the following is how this recipe deploys:
We by default should tuck that
/deploypath behind an HTTP Basic Auth.I could merge https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/branch/main/compose.auth.yml into the default
compose.yml? The result is that it'll be required tosecret generatebefore you deploy, which is an extra step. If all good, can do that.