Results of 1 - 10 of about 12 for deployment (0.002 sec.)
- Deploy 14592
- Overview Deploying DuckDB-Wasm means serving its components so that the browser can fetch and instantiate them. This page describes each component a deployment needs to serve, how the worker and WebAssembly variants relate, how extensions a
...re served and mirrored, and the security considerations involved. A DuckDB-Wasm deployment needs to access the following components: Main Library Component. Distributed as TypeScript and compiled to JavaScript cod...embly file and instantiated by the browser. For further details, see below. DuckDB Extensions. Any relevant extensions the deployment loads. For further details, see below. Main Library Component This component is distributed as TypeScript or CommonJS Java...der to work. The exact steps depend on your setup; see the examples in the repository . For instance, the shell.duckdb.org deployment transpiles the main library together with the shell code (the first approach above), while the bare-browser example shows... - https://man.mtool.work/duckdb/2.0/clients/wasm/deploying_duckdb_wasm.html
- Reference 8950
- 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
...em. Setting Type Default Description whoami_name VARCHAR (empty) Human-readable node name. whoami_provider VARCHAR (empty) Deployment provider ( ec2 , docker , local , ...). whoami_hostname VARCHAR (empty) Network hostname / public address. whoami_region V...ARCHAR (empty) Deployment region. whoami_started_at VARCHAR (empty) Node start time (ISO 8601 timestamp). Anchors uptime . whoami_meta VARCHAR {} Pr... - https://man.mtool.work/duckdb/2.0/quack/reference.html
- Deploying Quack 8755
- 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
... - https://man.mtool.work/duckdb/2.0/quack/setup/deployment.html
- Quack on WebAssembly 8755
- 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
...ate-url https://duckdb-quack-ami.s3.us-east-1.amazonaws.com/quack.yaml \ --region us-east-2 Wait approx. 2 minutes for the deployment to complete (this command is blocking): aws cloudformation wait stack-create-complete \ --stack-name my-quack-demo \ --reg... - https://man.mtool.work/duckdb/2.0/quack/setup/quack_wasm.html
- DuckDB Wasm Client 8401
- Installation To use the DuckDB Wasm client, visit the duckdb-wasm GitHub repository . The latest stable version of the DuckDB WebAssembly client is 2.0.0. DuckDB-Wasm is a version of DuckDB that has been compiled to WebAssembly , the portab
...xtensions — how extension loading differs from native DuckDB and which extensions are available. Deploy — the components a deployment serves and the security considerations involved. Troubleshoot — common issues and their workarounds, including CORS errors... - https://man.mtool.work/duckdb/2.0/clients/wasm/overview.html
- Securing Quack with a Reverse Proxy 8401
- 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
... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
- PostgreSQL Extension Connection Pool 8207
- PostgreSQL server spawns a backend process for every incoming client connection. This model leads to the two following points with the postgres extension that can cause performance problems: opening a new connection is relatively expensive
...cer ) then opening a new connections only causes a new networking socket to be opened, not a full backend process. Thus in deployment environments with connection proxies it may be better to set the idle timeout to a lower value (using pg_pool_idle_timeout... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/connection_pool.html
- Python 8207
- The DuckDB Python package has its own repository at duckdb/duckdb-python and uses nanobind 3 to create Python bindings with DuckDB. Prerequisites This guide assumes: You have a full clone of the DuckDB Python package source, including its g
...t can be configured for C++ debugging of the Python extension: CMake Profile Configuration In Settings → Build, Execution, Deployment → CMake , create a Debug profile: Name: Debug Build type: Debug Generator: Ninja CMake Options: text -DCMAKE_PREFIX_PATH=$... - https://man.mtool.work/duckdb/2.0/dev/building/python.html
- Catalogs 8030
- The iceberg extension supports attaching Iceberg REST Catalogs. Attaching a catalog is required for writing to Iceberg . Before attaching an Iceberg REST Catalog, you must install the iceberg extension by following the instructions located
...⟨lakekeeper_irc_url⟩', SECRET '⟨lakekeeper_secret⟩' ); SeaweedFS SeaweedFS table buckets provide both halves of an Iceberg deployment: the embedded Iceberg REST Catalog serves the table metadata, and the table bucket stores the table data as Parquet files... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/catalogs.html
- Migrating to DuckDB 2.0 8030
- DuckDB 2.0.0 is packed with new features and performance improvements, including query optimization and asynchronous I/O. It also ships a small set of breaking changes, most notably a new default storage format, which DuckDB versions before
...2.0.0 cannot read, and the next step of the lambda syntax transition. This page provides guidance on migrating existing deployments to DuckDB 2.0.0. Before You Migrate Before migrating to DuckDB 2.0.0, assess whether your workload is mission-critical. F...oad. This lets you test DuckDB 2.0.0 in an environment outside of your production system before switching over. For simple deployments, migrating is straightforward. Complex deployments, especially those that run many DuckDB processes, require more care. W...ings). See the storage page for migration strategy and more information: https://duckdb.org/internals/storage Warning In a deployment with many DuckDB processes running different versions, a database file created by a v2.0.0 process is unreadable by the re... - https://man.mtool.work/duckdb/2.0/operations_manual/migration.html
DuckDB 2.0 Documentation / man.mtool.work