Self-host Gotify on a VPS
A simple push notification server with a REST API and web UI, for sending messages to your devices.
levelrail-cli templates deploy gotify --name my-gotifySpecification
- Status
- Verified on arm64 with image tag 2.6.1
- Category
- Communication
- Services
- gotify
- Ports
- 80
- Volumes
- 1
- Memory
- about 128 MiB
- arm64
- tested
- amd64
- image published
- Settings to fill in
- none
- License
- Permissive license, MIT
About Gotify
A simple push notification server with a REST API and web UI, for sending messages to your devices. Runs as a single container from the server image, listening on port 80; data is kept in named volumes.
What it deploys
Gotify runs as one service in a single Compose app, listening on port 80, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| gotify | gotify/server | 2.6.1 | 80 | gotify_data -> /app/data |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Verified. Verified on arm64 with image tag 2.6.1. Verified means our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 80 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 1 secret is generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| gotify | GOTIFY_DEFAULTUSER_NAME | Preset by the template |
| gotify | GOTIFY_DEFAULTUSER_PASS | Generated at deploy |
| gotify | TZ | Preset by the template |
Install Gotify on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get gotify -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy gotify --name my-gotify
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Gotify.
Docs and upstream
More in Communication
- FreeScoutA free, self-hosted help desk and shared mailbox, a lighter alternative to Zendesk or Help Scout.
- Element WebThe Element Matrix web client, served as static files and pointed at the homeserver you choose, for example the Matrix Synapse template. AGPL-3.0 licensed client. No account lives here, sign in or register on your homeserver.
- ejabberdRobust, scalable XMPP chat and messaging server from ProcessOne. Runs with the default configuration and stores its database on a volume.
- ListmonkA self-hosted newsletter and mailing list manager with a fast, dependency-light core.
- LiveKitOpen-source WebRTC server for real-time audio, video and data, with an API for rooms and tokens. The install form carries livekit.yaml as an editable file and generates the API key and secret.
- Mail server (mox, experimental)Experimental. Needs APP_EXPERIMENTAL=mail on the control plane: without it this template is hidden and cannot be installed. Install with the MAIL_FIRST_DOMAIN setting (templates install mail-mox --env MAIL_FIRST_DOMAIN=example.com). MAIL_HOSTNAME (the FQDN other servers connect to) defaults to mail. that domain and MAIL_ADMIN_EMAIL to postmaster@ that domain. Ports 25, 465, 587 and 993 are published on the host with a private bind by default. After install, open them with the CLI command mail ports open --confirm (or Open mail ports on the Mail page): that makes only those four ports public and allows them in the host firewall, then set up DNS. Webmail and the account UI are on port 8025 (private, no admin pages). The admin API and metrics are never published; never make them public. TLS: the first start makes a self-signed certificate (valid for localhost only, made by mox itself) so the server comes up with no manual steps. Replace it before sending real mail: put your certificate and key in the config volume and set MAIL_TLS_CERT_FILE and MAIL_TLS_KEY_FILE (paths under /mox/config, for example certs/cur.pem and certs/cur.key). Existing files at those paths are never overwritten. A changed certificate needs a container restart. Relay mode: set MAIL_SMARTHOST_HOST (and port, user, password) to send through a provider. Changing it needs a restart. The admin password is the generated secret SERVICE_PASSWORD_MAILADMIN. Back up the config and data volumes together. Deliverability depends on reverse DNS, SPF, DKIM and a clean IP; see the mail template guide. Licence: MIT.