Repository navigation
v0.14.5
Postgres and Supabase
- The gateway's record can live in Postgres, tested in CI on every change. Supabase's connection strings work as copied (
postgres://andpostgresql://). DB_SCHEMAkeeps every table in a schema of its own;DB_POOL_SIZE,DB_MAX_OVERFLOW,DB_POOL_RECYCLEfor small plans;DB_DISABLE_PREPARED=1for transaction poolers.squidbrake import-sqlite gateway.dbmoves an existing SQLite record into Postgres with its audit chain, and checks the chain after.deploy/supabase_setup.sqllocks a Supabase project down: its own schema, a login that isn't the superuser, nothing for the public API's roles, row level security on.- Setup, what to back up besides the database (keys and signing secrets stay out of it), and troubleshooting: docs/postgres-supabase.md.
- The Docker image includes the Postgres driver; with pip:
pip install "squidbrake[postgres]". - README: What is stored, plainly: a redacted copy of each action (by names and patterns), the hash-chained audit trail, the chains in progress. With Postgres, whoever runs that database holds it.
SQLite stays the default; nothing changes for an install that doesn't set DATABASE_URL.
Upgrade: run the install line again, or pipx upgrade squidbrake.
Install this version (0.14.5)
Windows (PowerShell):
$env:SQUIDBRAKE_VERSION="0.14.5"; irm https://pilots.squidbrake.com/install.ps1 | iexmacOS / Linux:
curl -fsSL https://pilots.squidbrake.com/install.sh | SQUIDBRAKE_VERSION=0.14.5 shWith pip: pip install squidbrake==0.14.5. Docker: docker pull ghcr.io/batrapulkit/squidbrake:0.14.5
Running the line again without SQUIDBRAKE_VERSION goes back to the newest. Every version:
https://github.com/batrapulkit/squidbrake/releases