Self-host DbGate with Levelrail
A web database client for SQL and NoSQL databases with a generated login and a data volume. Sign in as admin with the generated password, then add connections to other services here.
- Authordbgate
- LicenceGPL-3.0-only
- Memory256 MiB
- Services1
How to self-host DbGate
-
Pull the images
One image is pulled on your server.
Show images
dbgate/dbgate:7.3.4-alpine
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Sign in as admin with the generated password from the app secrets, then add a connection to a database in this project.
DbGate requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-only, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then DbGate. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the DbGate docs page.
Deploy DbGate your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy DbGate from the CLI
levelrail-cli templates deploy dbgate --name my-dbgate Deploy DbGate with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/dbgate/deploy DbGate configuration
DbGate services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| dbgate | dbgate/dbgate:7.3.4-alpine | 3000 | dbgate_data -> /root/.dbgate |
DbGate environment variables
| Variable | Service | Value |
|---|---|---|
| LOGIN | dbgate | Preset by the template |
| PASSWORD | dbgate | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: dbgate_data -> /root/.dbgate
DbGate FAQ
How much memory does DbGate need?
The catalog lists about 256 MiB of memory for DbGate.
Does DbGate run on arm64?
For DbGate, arm64 support is not confirmed; amd64 is unknown.
What licence is DbGate under?
DbGate is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does DbGate need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does DbGate use?
DbGate listens on port 3000 inside the stack.
Where does DbGate keep its data?
In a named volume: dbgate_data mounted at /root/.dbgate.
Can I deploy DbGate on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for DbGate, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image dbgate/dbgate:7.3.4-alpine is what you deploy there.