Results of 1 - 2 of about 2 for caddy (0.001 sec.)
- Securing Quack with a Reverse Proxy 11228
- By default, the Quack server binds to localhost and speaks plain HTTP. See Security for the rationale behind these configurations. For any deployment beyond local-only, the recommended pattern is the same as for any other HTTP-based databas
...rom the client side too. This guide walks through three setups, in order of likely usefulness: A local TLS test setup with Caddy, so you can exercise the full HTTPS path on your machine. nginx + Let's Encrypt in production. Caddy + Let's Encrypt in pr...oduction. The two production setups are interchangeable. Pick whichever fits your operational stack. Local Test Setup with Caddy You can exercise the full HTTPS path on your own machine using Caddy. Caddy issues itself a certificate for localhost from...stalls the CA root into your system trust store, so DuckDB's HTTPS client trusts the cert without any extra config. 1. Run Caddy Save this Caddyfile : localhost:8443 { reverse_proxy 127.0.0.1:9494 { flush_interval -1 } request_body { max_size 256MB }... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
- Security 7485
- This page covers Quack's security posture end to end: what the server exposes, what stays local, the role of a TLS-terminating reverse proxy, and the authentication / authorization callbacks the server runs on every connection and every que
...so a properly fronted server "just works" from the client side too. See Securing Quack with a Reverse Proxy for nginx and Caddy recipes (production and local-test). Authentication and Authorization For every database call, there are two distinct deci... - https://man.mtool.work/duckdb/2.0/quack/security.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work