Self-host Mafl with Levelrail
A minimal homepage that lists your services as a tidy grid of links. It is configured from a single YAML file, and the starter file is created for you.
- Authorhywax
- LicenceMIT
- Memory128 MiB
- Services1
How to self-host Mafl
-
Pull the images
One image is pulled on your server.
Show images
hywax/mafl:v0.15.4
-
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
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
- Edit the config file in the deployment configs to list your own services, then redeploy.
Mafl requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Mafl. 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 Mafl docs page.
Deploy Mafl your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Mafl from the CLI
levelrail-cli templates deploy mafl --name my-mafl Deploy Mafl with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/mafl/deploy Mafl configuration
Mafl services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| mafl | hywax/mafl:v0.15.4 | 3000 | data -> /app/data/icons |
Mafl environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: data -> /app/data/icons
Mafl FAQ
How much memory does Mafl need?
The catalog lists about 128 MiB of memory for Mafl.
Does Mafl run on arm64?
For Mafl, arm64 support is not confirmed; amd64 is unknown.
What licence is Mafl under?
Mafl is licensed under MIT, which is permissive, with few conditions on reuse.
Does Mafl need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Mafl use?
Mafl listens on port 3000 inside the stack.
Where does Mafl keep its data?
In a named volume: data mounted at /app/data/icons.
Can I deploy Mafl 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 Mafl, 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 hywax/mafl:v0.15.4 is what you deploy there.