Self-host Gotify with Levelrail

Verified

A simple push notification server with a REST API and web UI, for sending messages to your devices.

  • AuthorgotifyVerified by Levelrail
  • LicenceMIT
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host Gotify

  1. Pull the images

    One image is pulled on your server.

    Show images
    • gotify/server:2.6.1
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Gotify requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
80
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.6.1. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 80 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 Gotify. 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 Gotify docs page.

Deploy Gotify your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Gotify from the CLI

levelrail-cli templates deploy gotify --name my-gotify

Deploy Gotify with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/gotify/deploy

Gotify configuration

Gotify services

ServiceImagePortsVolumes
gotify gotify/server:2.6.1 80 gotify_data -> /app/data

Gotify environment variables

VariableServiceValue
GOTIFY_DEFAULTUSER_NAME gotify Preset by the template
GOTIFY_DEFAULTUSER_PASS gotify Generated at deploy
TZ gotify Preset by the template

Ports and volumes

Ports
80
Volumes
1 named mount: gotify_data -> /app/data

Gotify FAQ

How much memory does Gotify need?

The catalog lists about 128 MiB of memory for Gotify.

Does Gotify run on arm64?

For Gotify, arm64 is tested; amd64 is image published.

What licence is Gotify under?

Gotify is licensed under MIT, which is permissive, with few conditions on reuse.

Does Gotify need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does Gotify use?

Gotify listens on port 80 inside the stack.

Where does Gotify keep its data?

In a named volume: gotify_data mounted at /app/data.

Can I deploy Gotify 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 gotify for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image gotify/server:2.6.1 is what you deploy there.

levelrail-cli templates deploy gotify --name my-gotify