Results of 1 - 4 of about 4 for nginx (0.001 sec.)
- Securing Quack with a Reverse Proxy 12371
- 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
...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 production. The two production setups are interchangeable. Pick wh...succeeds, your traffic just went out as TLS to Caddy, got terminated, and was forwarded as plain HTTP to Quack on :9494 . Nginx + Let's Encrypt We expect this to be the most common choice. A minimal site for a Quack server listening on the loopback i...nterface looks as follows: # /etc/nginx/sites-enabled/quack.example.com server { listen 443 ssl http2; server_name quack.example.com; ssl_certificate /etc/letsenc... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
- Deploying Quack 8746
- This page collects deployment recipes for running a public-facing Quack server. Today there is one recipe (AWS EC2), we will introduce more over time. On AWS EC2 The fastest way to get a public-facing Quack server is the one-click AWS Cloud
...template maintained alongside the extension. It provisions a small EC2 instance running DuckDB, the quack extension behind nginx and Let's Encrypt TLS. As its output, it surfaces the per-instance token and connection URI. One-Click Launch Open the Lau...n AWS::EC2::Instance from a public AMI (per-region map baked into the template) running DuckDB, the quack extension behind nginx and the Let's Encrypt TLS. An AWS::EC2::SecurityGroup opening ports 80 (ACME challenge) and 443 (HTTPS). An AWS::CloudForm... - https://man.mtool.work/duckdb/2.0/quack/setup/deployment.html
- Quack on WebAssembly 8062
- CloudFormation Stack We provide an example template for initializing a CloudFormation stack, based on pre-baked public AMI, based on Ubuntu, which will: via DuckDB, install and load Quack, create a randomized token, and do quack_serve on th
...e 0.0.0.0:1294 port. setup via nginx a proxy between 0.0.0.0:1294 and the incoming :443 port obtain a valid TLS certificate via Let's Encrypt All together, thi... - https://man.mtool.work/duckdb/2.0/quack/setup/quack_wasm.html
- Security 7766
- 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
...y default, 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 dis... - https://man.mtool.work/duckdb/2.0/quack/security.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work