Configuration
Every QueryProxy environment variable — query limits, execution, result storage, the application database and the queue.
Updated:
All configuration is environment variables (.env locally, container
environment in Docker). .env.example in the repository documents the full
set; this page explains the ones you’ll actually change.
QueryProxy settings
| Variable | Default | Meaning |
|---|---|---|
QUERYPROXY_SELECT_DEFAULT_LIMIT |
1000 |
LIMIT injected into SELECTs that have none |
QUERYPROXY_SELECT_HARD_LIMIT |
10000 |
Larger LIMITs are clamped down to this |
QUERYPROXY_EXECUTION_TIMEOUT |
300 |
Max seconds a single request may run on the worker |
QUERYPROXY_RESULT_DISK |
local |
Laravel filesystem disk for result files (s3 supported) |
QUERYPROXY_RESULT_TTL_DAYS |
30 |
Days before results:prune deletes stored results |
QUERYPROXY_SEED_DEMO |
false |
Docker only: seed the demo team on first boot |
Keep the worker’s
--timeouta bit aboveQUERYPROXY_EXECUTION_TIMEOUT(the compose file uses310vs300) so the job timeout fires first.
Application database
QueryProxy’s own data (users, teams, requests, audit log) lives in SQLite by default — zero configuration. For MySQL or PostgreSQL, set the standard Laravel variables:
DB_CONNECTION=pgsql # or mysql
DB_HOST=db
DB_PORT=5432
DB_DATABASE=queryproxy
DB_USERNAME=queryproxy
DB_PASSWORD=change-me
This is the application database — the databases you proxy are configured in the UI under Connections, per team, with encrypted credentials.
Queue
The queue is database-backed by default (no Redis required). To move it to Redis:
QUEUE_CONNECTION=redis
REDIS_HOST=redis
The worker command stays the same:
php artisan queue:work --queue=queries,default.
Result storage on S3
Set QUERYPROXY_RESULT_DISK=s3 and the standard AWS_* variables. Result
files are written as NDJSON, streamed — memory use stays flat regardless of
result size.
SQL Server targets
The default Docker image ships pdo_pgsql, pdo_mysql and pdo_sqlite. To
proxy Microsoft SQL Server databases, extend the Dockerfile with Microsoft’s
ODBC driver and the sqlsrv / pdo_sqlsrv PECL extensions (see the README’s
“SQL Server support” section for the exact steps).