Self-host Bytebase with Levelrail
A database schema change and migration tool with review workflows built in.
- Authorbytebase
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services1
How to self-host Bytebase
-
Pull the images
One image is pulled on your server.
Show images
bytebase/bytebase:3.9.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
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.
Bytebase requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Bytebase. 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 Bytebase docs page.
Deploy Bytebase your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Bytebase from the CLI
levelrail-cli templates deploy bytebase --name my-bytebase Deploy Bytebase with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/bytebase/deploy Bytebase configuration
Bytebase services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| bytebase | bytebase/bytebase:3.9.2 | 8080 | bytebase_data -> /var/opt/bytebase |
Bytebase environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: bytebase_data -> /var/opt/bytebase
Bytebase FAQ
How much memory does Bytebase need?
The catalog lists about 512 MiB of memory for Bytebase.
Does Bytebase run on arm64?
For Bytebase, an arm64 image is published; amd64 is image published.
What licence is Bytebase under?
Bytebase is licensed under MIT, which is permissive, with few conditions on reuse.
Does Bytebase need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Bytebase use?
Bytebase listens on port 8080 inside the stack.
Where does Bytebase keep its data?
In a named volume: bytebase_data mounted at /var/opt/bytebase.
Can I deploy Bytebase on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id bytebase for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image bytebase/bytebase:3.9.2 is what you deploy there.