ripdb

A custom DuckDB extension repository. Install ripdb directly from this URL.

Install

$ duckdb -unsigned
INSTALL ripdb FROM 'PAGE_BASE_URL';
LOAD ripdb;

Custom-repository extensions are unsigned. Start DuckDB with the -unsigned CLI flag — that's the only supported way to enable unsigned-extension support. SET allow_unsigned_extensions = true; from a running session is rejected with "Cannot change allow_unsigned_extensions setting while database is running."

Currently published

osx_arm64 linux_amd64

Additional platforms (osx_amd64, linux_arm64, wasm_*, windows_*) are supported by the build system but not currently published. They'll reappear here once enabled in the CI matrix.

URL layout

Each build is published under the path DuckDB expects for a custom repository:

<base>/<duckdb_version>/<platform>/ripdb.duckdb_extension.gz

See manifest.json for the exact set of builds available on this instance.

Verify before installing

DuckDB builds the full URL itself from your client's version and platform. You can sanity-check that the right build is published — no DuckDB session needed:

# 1) Your DuckDB version
duckdb -csv -noheader -c "SELECT library_version FROM pragma_version()"
# → v1.5.2

# 2) Your platform
duckdb -csv -noheader -c "PRAGMA platform"
# → osx_arm64

# 3) Is a build published for that (version, platform) pair?
curl -I "PAGE_BASE_URL/v1.5.2/osx_arm64/ripdb.duckdb_extension.gz"
# → HTTP/2 200 means INSTALL will succeed
# → HTTP/2 404 means that cell isn't published yet — run the workflow
#   with your DuckDB version as input.