Self-host SilverBullet with Levelrail
VerifiedA programmable, Markdown-based notes app you can extend with your own scripts and queries.
- Authorsilverbulletmd
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host SilverBullet
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/silverbulletmd/silverbullet:2.11.1
-
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, 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.
SilverBullet requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Verified. Verified on arm64 with image tag 2.11.1. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 3000 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 SilverBullet. 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 SilverBullet docs page.
Deploy SilverBullet your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy SilverBullet from the CLI
levelrail-cli templates deploy silverbullet --name my-silverbullet Deploy SilverBullet with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/silverbullet/deploy SilverBullet configuration
SilverBullet services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| silverbullet | ghcr.io/silverbulletmd/silverbullet:2.11.1 | 3000 | silverbullet_space -> /space |
SilverBullet environment variables
| Variable | Service | Value |
|---|---|---|
| SB_USER | silverbullet | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: silverbullet_space -> /space
SilverBullet FAQ
How much memory does SilverBullet need?
The catalog lists about 256 MiB of memory for SilverBullet.
Does SilverBullet run on arm64?
For SilverBullet, arm64 is tested; amd64 is image published.
What licence is SilverBullet under?
SilverBullet is licensed under MIT, which is permissive, with few conditions on reuse.
Does SilverBullet need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does SilverBullet use?
SilverBullet listens on port 3000 inside the stack.
Where does SilverBullet keep its data?
In a named volume: silverbullet_space mounted at /space.
Can I deploy SilverBullet 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 silverbullet for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/silverbulletmd/silverbullet:2.11.1 is what you deploy there.