Self-host Bugsink with Levelrail
A self-hosted, lightweight error tracking server with a Sentry-compatible SDK ingestion API.
- Memory512 MiB
- Archarm64
- Services2
How to self-host Bugsink
-
Pull the images
2 images are pulled on your server.
Show images
mysql:8.4bugsink/bugsink:latest
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
5 secrets are generated and stored encrypted, 4 settings are 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.
Bugsink requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8000 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (bugsink/bugsink:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Bugsink. 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 Bugsink docs page.
Deploy Bugsink your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Bugsink from the CLI
levelrail-cli templates deploy bugsink --name my-bugsink Deploy Bugsink with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/bugsink/deploy Bugsink configuration
Bugsink services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| mysql | mysql:8.4 | none | bugsink_mysql_data -> /var/lib/mysql |
| web | bugsink/bugsink:latest | 8000 | none |
Bugsink environment variables
| Variable | Service | Value |
|---|---|---|
| MYSQL_DATABASE | mysql | Preset by the template |
| MYSQL_PASSWORD | mysql | Generated at deploy |
| MYSQL_ROOT_PASSWORD | mysql | Generated at deploy |
| MYSQL_USER | mysql | Preset by the template |
| BASE_URL | web | Preset by the template |
| BEHIND_HTTPS_PROXY | web | Preset by the template |
| CREATE_SUPERUSER | web | Generated at deploy |
| DATABASE_URL | web | Generated at deploy |
Show all 9 variables
- SECRET_KEYwebGenerated at deploy
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: bugsink_mysql_data -> /var/lib/mysql
Bugsink FAQ
How much memory does Bugsink need?
The catalog lists about 512 MiB of memory for Bugsink across its 2 services.
Does Bugsink run on arm64?
For Bugsink, an arm64 image is published; amd64 is image published.
Does Bugsink need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Bugsink bundle?
The template includes MySQL, running as its own service.
Which ports does Bugsink use?
Bugsink listens on port 8000 inside the stack.
Where does Bugsink keep its data?
In a named volume: bugsink_mysql_data mounted at /var/lib/mysql.
Can I deploy Bugsink 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 bugsink for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image mysql:8.4, bugsink/bugsink:latest is what you deploy there.