eidorb

Assuming your deployment system can pass your base64-encoded git-crypt key in an environment variable named `GIT_CRYPT_KEY`, you could unlock as follows: ```bash # Unlock git-crypt. echo $GIT_CRYPT_KEY | base64 -d...

Including `Content-Length` in the `exclude_headers` parameter fixes this: ```python handler = Mangum( app, # Content-Length header is not allowed in Lambda@Edge responses. exclude_headers=["Content-Length"], ) ``` `exclude_headers` was introduced in #280.

Is the preferred approach to use the [datasette-redirect-forbidden](https://datasette.io/plugins/datasette-redirect-forbidden) plugin, and configure it as follows? ``` "datasette-redirect-forbidden": { "redirect_to": "/-/github-auth-start", } ```