Self-host Notifiarr with Levelrail
Client for the Notifiarr service that relays notifications and syncs profiles for your media apps. The install form carries notifiarr.conf as an editable file and asks for your API key.
- AuthorNotifiarr
- LicenceMIT
- Memory128 MiB
- Services1
Needs setup: set its settings before the first start.
How to self-host Notifiarr
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/notifiarr/notifiarr:v0.10.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5454.
-
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
- Create an account on notifiarr.com, copy your API key into the install form, then open the address to add your apps.
Notifiarr requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 5454
- 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 Notifiarr. 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 Notifiarr docs page.
Deploy Notifiarr your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Notifiarr from the CLI
levelrail-cli templates install notifiarr --name my-notifiarr --env NOTIFIARR_API_KEY=VALUE Deploy Notifiarr with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/notifiarr/install \
-d '{
"name": "my-notifiarr",
"env": { "NOTIFIARR_API_KEY": "VALUE" }
}' Notifiarr configuration
Notifiarr services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| notifiarr | ghcr.io/notifiarr/notifiarr:v0.10.0 | 5454 | config -> /config |
Notifiarr environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 5454
- Volumes
- 1 named mount: config -> /config
Notifiarr FAQ
How much memory does Notifiarr need?
The catalog lists about 128 MiB of memory for Notifiarr.
Does Notifiarr run on arm64?
For Notifiarr, arm64 support is not confirmed; amd64 is unknown.
What licence is Notifiarr under?
Notifiarr is licensed under MIT, which is permissive, with few conditions on reuse.
Does Notifiarr need configuration before it starts?
Yes. Notifiarr has required settings.
Which ports does Notifiarr use?
Notifiarr listens on port 5454 inside the stack.
Where does Notifiarr keep its data?
In a named volume: config mounted at /config.
Can I deploy Notifiarr 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 Notifiarr, 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 ghcr.io/notifiarr/notifiarr:v0.10.0 is what you deploy there.