Self-host Flame with Levelrail
A self-hosted start page with an app launcher, bookmarks, and Docker label integration.
- Authorpawelmalak
- LicenceMIT
- Memory128 MiB
- Services1
How to self-host Flame
-
Pull the images
One image is pulled on your server.
Show images
pawelmalak/flame:2.3.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5005.
-
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.
Flame requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 not available
- Ports
- 5005
- 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 5005 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 Flame. 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 Flame docs page.
Deploy Flame your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Flame from the CLI
levelrail-cli templates deploy flame --name my-flame Deploy Flame with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/flame/deploy Flame configuration
Flame services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| flame | pawelmalak/flame:2.3.1 | 5005 | flame_data -> /app/data |
Flame environment variables
| Variable | Service | Value |
|---|---|---|
| PASSWORD | flame | Generated at deploy |
Ports and volumes
- Ports
- 5005
- Volumes
- 1 named mount: flame_data -> /app/data
Flame FAQ
How much memory does Flame need?
The catalog lists about 128 MiB of memory for Flame.
Does Flame run on arm64?
For Flame, amd64 only, no arm64 image; amd64 is image published.
What licence is Flame under?
Flame is licensed under MIT, which is permissive, with few conditions on reuse.
Does Flame need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Flame use?
Flame listens on port 5005 inside the stack.
Where does Flame keep its data?
In a named volume: flame_data mounted at /app/data.
Can I deploy Flame 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 Flame, 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 pawelmalak/flame:2.3.1 is what you deploy there.