Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
querypie-cli
Query QueryPie databases from the terminal with webview authentication.
Quick Start
Installation
Linux / macOS:
|
Windows (PowerShell):
powershell -c "irm https://raw.githubusercontent.com/sudosubin/querypie-cli/main/scripts/install.ps1 | iex"
The installer downloads the matching binary from GitHub Releases, verifies its checksum, and installs it (Linux/macOS: ~/.local/bin, Windows: %LOCALAPPDATA%\querypie-cli\bin). Set QUERYPIE_VERSION to pin a release or QUERYPIE_INSTALL_DIR to change the location:
| QUERYPIE_VERSION=v0.1.1
Or install with Cargo:
Build from source:
querypie uses a WebView for login: Linux needs WebKitGTK (libwebkit2gtk-4.1) at runtime, and Windows needs the Edge WebView2 Runtime (preinstalled on current Windows).
Commands
| Command | Purpose |
|---|---|
auth login |
Open the QueryPie WebView login |
auth logout |
Clear the WebView profile for a host |
auth status |
Show login status |
completion <shell> |
Generate shell completions |
connection list |
List available QueryPie connections |
database list |
List databases for a connection |
query <sql> |
Run SQL through QueryPie |
schema list |
List schemas for a database |
session clear |
Clear cached database sessions |
session list |
List cached database sessions |
table ddl <table> |
Show QueryPie table DDL |
table describe <table> |
Show QueryPie table structure |
table list |
List tables |
Examples
Use --output json for machine-readable output.
Authentication
- Login uses a dedicated Tauri WebView.
- httpOnly QueryPie cookies stay in the WebView cookie store.
- Access token refresh runs automatically in the background.
- If refresh fails for a previously authenticated host, commands open the login WebView and continue after login.
- If no login exists, commands exit with an auth error.
Configuration
Default path:
~/.config/querypie-cli/config.json
Example:
CLI flags override config values.
Shell Completions
Generate completions for your shell:
Completions can query your logged-in QueryPie host for connection, engine, database, schema, and table candidates. If authentication or network access is unavailable, dynamic candidates are skipped silently.
Output
--color auto|always|never: control ANSI color (autocolors terminal output unlessNO_COLORis set)--limit <N>: maximum query rows to fetch, defaults to1000and must be at least1--no-truncate: do not shorten long table cells--output json: raw JSON output--output text: default human-readable outputQUERYPIE_NO_TRUNCATE=1: disable truncation globally
NULL values are rendered distinctly in colored text output. JSON output never includes ANSI escape sequences.
Text query output reports (N rows, limit reached) when the result reaches the configured row limit. JSON query output includes limit and limit_reached fields alongside columns and rows.
How It Works
auth loginopens QueryPie in a Tauri WebView.- The CLI reads httpOnly cookies through the same WebView profile.
- API calls use QueryPie's gRPC-Web endpoints.
- Expired access tokens are refreshed through the WebView cookie store.
- Database sessions are cached under
~/.cache/querypie-cli.
Troubleshooting
Check auth:
Clear cached database sessions:
Development
License
MIT, see LICENSE.