Step 1: Add a database connection
Create apgconsole.toml file with at least one connection:
pgconsole.toml
Step 2: Start
- Docker (Recommended)
- npx
- npm
If connecting to a database on your host machine, use
host.docker.internal instead of localhost in your config.http://localhost:9876 in your browser. You’ll see the SQL editor with the schema browser on the left.
Demo mode
If you run pgconsole without apgconsole.toml, it starts in demo mode with an embedded in-memory PostgreSQL database pre-loaded with sample data:
Demo mode data is ephemeral and resets on every restart. To connect to a real database, create a
pgconsole.toml as shown in Step 1.Docker Compose
Add pgconsole as a service alongside your existing PostgreSQL in Docker Compose:docker-compose.yml
http://localhost:9876 — pgconsole connects to your database and you can browse schemas, run queries, and edit data immediately.
Kubernetes
Deploy pgconsole as a Deployment with a ConfigMap for the configuration:pgconsole.yaml
http://localhost:9876 to access pgconsole.
To expose pgconsole externally with TLS, see Kubernetes Ingress and Kubernetes Gateway API.