Results of 1 - 3 of about 3 for listen (0.001 sec.)
- Reference 11905
- This page lists the functions, settings, and log types exposed by the quack extension . For a tour of the protocol, start with the Overview . Function Reference Server Management Function Description quack_serve(⟨listen_uri⟩, ...) Start a s
...erver on listen_uri , which defaults to quack:localhost when omitted. Localhost-only by default. Returns the listen URI, the listen URL, a...nd the authentication token. See the quack_serve parameters below. quack_stop(listen_uri) Stop the server listening on listen_uri . quack_server_list() List the servers running in this instance: listen URI a...le macro returning identity + runtime info for the current node. quack_serve Parameters Parameter Type Default Description listen_uri VARCHAR quack:localhost Positional. The Quack URI to listen on. allow_other_hostname BOOLEAN false Allow binding to a... - https://man.mtool.work/duckdb/2.0/quack/reference.html
- Quack Remote Protocol 8185
- The Quack extension turns a DuckDB instance into a server that other DuckDB instances (clients) can connect to over HTTP. This page covers the protocol at a glance and walks through basic usage on both sides of the wire. For the full list o
...that the session can see (in-memory tables, attached files, schemas) becomes reachable over the remote protocol. To start listening on localhost, run: {:.codebox-server} CALL quack_serve('quack:localhost'); The URI argument is optional: calling quack_...serve() without it also listens on quack:localhost . quack_serve returns the listen URI, the HTTP URL, and, when the default authentication function is i...ith -connect . See Command Line Arguments . By default the server refuses to bind anything other than a local hostname. To listen on an externally-reachable address, pass allow_other_hostname = true : {:.codebox-server} CALL quack_serve('quack:0.0.0.0:... - https://man.mtool.work/duckdb/2.0/quack/overview.html
- Securing Quack with a Reverse Proxy 7775
- 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
...P 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 interface looks as follows: # /etc/nginx/sites-enabled/quack.example.com server { listen 443 ssl http2;... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work