Self-host Miniflux with Levelrail
A minimalist, fast RSS/Atom feed reader with no bloat and a keyboard-driven UI.
- Authorminiflux
- LicenceApache-2.0
- Memory256 MiB
- Archarm64
- Services2
How to self-host Miniflux
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpineghcr.io/miniflux/miniflux:2.2.4
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 3 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.
Miniflux requirements
- Memory
- About 256 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
- Apache-2.0, 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 Miniflux. 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 Miniflux docs page.
Deploy Miniflux your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Miniflux from the CLI
levelrail-cli templates deploy miniflux --name my-miniflux Deploy Miniflux with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/miniflux/deploy Miniflux configuration
Miniflux services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | miniflux_db_data -> /var/lib/postgresql/data |
| miniflux | ghcr.io/miniflux/miniflux:2.2.4 | 8080 | none |
Miniflux environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| ADMIN_PASSWORD | miniflux | Generated at deploy |
| ADMIN_USERNAME | miniflux | Generated at deploy |
| DATABASE_URL | miniflux | Generated at deploy |
| RUN_MIGRATIONS | miniflux | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: miniflux_db_data -> /var/lib/postgresql/data
Miniflux FAQ
How much memory does Miniflux need?
The catalog lists about 256 MiB of memory for Miniflux across its 2 services.
Does Miniflux run on arm64?
For Miniflux, an arm64 image is published; amd64 is image published.
What licence is Miniflux under?
Miniflux is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Miniflux need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Miniflux bundle?
The template includes Postgres, running as its own service.
Which ports does Miniflux use?
Miniflux listens on port 8080 inside the stack.
Where does Miniflux keep its data?
In a named volume: miniflux_db_data mounted at /var/lib/postgresql/data.
Can I deploy Miniflux 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 miniflux for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, ghcr.io/miniflux/miniflux:2.2.4 is what you deploy there.