Documentation Index
Fetch the complete documentation index at: https://mintlify.com/felixdotgo/querybox/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before installing QueryBox, ensure you have the following tools installed on your system:Go 1.26+
Go 1.26+
Wails v3
Wails v3
Wails v3 is the desktop framework powering QueryBox. Install the CLI:For detailed installation instructions, visit the Wails v3 installation guide.
Node.js 18+
Node.js 18+
Task (Build Automation)
Task (Build Automation)
Task is used for build automation. Install via:See taskfile.dev/installation for more options.
- Go
- npm
- Homebrew (macOS)
Protocol Buffers (Optional)
Protocol Buffers (Optional)
Only required if you plan to modify
.proto files. For most users, this is not needed.Install protoc
Download from grpc.io/docs/protoc-installationRecommended version: libprotoc 29.6
Platform-Specific Requirements
- Windows
- macOS
- Linux
Windows Requirements
Install WebView2
Wails v3 requires Microsoft Edge WebView2 Runtime, which is pre-installed on Windows 11 and recent Windows 10 updates.If needed, download from Microsoft’s WebView2 page.
Windows Defender may flag the built executable. This is common for unsigned applications. You can add an exception or sign your builds.
Building from Source
Build the Plugins
QueryBox’s database drivers are standalone executables that need to be built separately:This builds all plugins (MySQL, PostgreSQL, SQLite, Redis, ArangoDB) and places them in
bin/plugins/.The build process automatically detects your OS and architecture. Binaries are placed in
bin/plugins/ with .exe extension on Windows.Cross-compile plugins for other platforms
Cross-compile plugins for other platforms
Override the target platform using standard Go environment variables:
Build QueryBox
Build the production executable:The application will be built to the
bin/ directory:- Windows:
bin/querybox.exe - macOS:
bin/QueryBox.app - Linux:
bin/querybox
Build options
Build options
Wails supports various build flags:See
wails3 build --help for all options.Development Mode
For development with hot-reload:In development mode, plugins are loaded from
bin/plugins/. If you modify plugin code, rebuild with task build:plugins and the running app will detect the changes within 2 seconds (after clicking the Rescan button in the Plugins window).Plugin Installation Directory
At runtime, QueryBox manages plugins in two locations:Bundled Plugins
Plugins in
bin/plugins/ are bundled with the application. These are the built-in database drivers.User Plugins
On first launch, QueryBox copies bundled plugins to a user-writable directory:
- Windows:
%APPDATA%\querybox\plugins - macOS:
~/Library/Application Support/querybox/plugins - Linux:
$XDG_CONFIG_HOME/querybox/plugins(or~/.config/querybox/plugins)
- Add custom database drivers
- Override built-in plugins
- Keep plugins across application updates
Verifying Installation
Once installed, verify QueryBox is working correctly:Check Plugin Discovery
- From the main window menu, open Plugins window
- You should see all built-in plugins listed:
- MySQL
- PostgreSQL
- SQLite
- Redis
- ArangoDB
If all plugins are discovered and test connections work, your installation is complete!
Troubleshooting
Plugins not discovered
Plugins not discovered
Symptoms: Plugins window is empty or missing expected driversSolutions:
- Verify plugins were built:
ls bin/plugins/should show executables - Check file permissions: plugins must be executable (
chmod +x bin/plugins/*on Linux/macOS) - Click Rescan button in Plugins window
- Check logs for plugin probe failures (View → Developer → Toggle Developer Tools)
Build fails on Windows
Build fails on Windows
Common causes:
- Missing Visual Studio Build Tools
- WebView2 Runtime not installed
- Antivirus blocking build output
- Install Visual Studio 2019+ or Build Tools for Visual Studio
- Download WebView2 Runtime from Microsoft
- Add
bin/directory to antivirus exclusions
Permission denied on macOS
Permission denied on macOS
Symptoms: “QueryBox.app is damaged and can’t be opened”Solution:Or go to System Preferences → Security & Privacy and allow the app.
WebKitGTK errors on Linux
WebKitGTK errors on Linux
Symptoms: Application won’t start or crashes immediatelySolution:
Ensure WebKitGTK 4.0 development libraries are installed:
Next Steps
Quick Start Guide
Connect to your first database and run queries
Plugin Development
Learn to create custom database drivers