Self-host Statping-ng with Levelrail

A status page and uptime monitor for sites, APIs and TCP services with alerts.

  • Authorstatping-ng
  • LicenceGPL-3.0-only
  • Memory128 MiB
  • Services1

How to self-host Statping-ng

  1. Pull the images

    One image is pulled on your server.

    Show images
    • adamboutcher/statping-ng:v0.90.78
  2. Create the app

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

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 4 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.

After the first start

  • Sign in as admin with the generated password.

Statping-ng requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8080
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0-only, copyleft 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 Statping-ng. 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 Statping-ng docs page.

Deploy Statping-ng your way

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

Deploy Statping-ng from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain statping-ng=app.example.com.

levelrail-cli templates install statping-ng --name my-statping-ng

Deploy Statping-ng with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/statping-ng/install \
  -d '{
    "name": "my-statping-ng"
  }'

Statping-ng configuration

Statping-ng services

ServiceImagePortsVolumes
statping-ng adamboutcher/statping-ng:v0.90.78 8080 app -> /app

Statping-ng environment variables

VariableServiceValue
ADMIN_PASSWORD statping-ng Generated at deploy
ADMIN_USER statping-ng Preset by the template
DB_CONN statping-ng Preset by the template
DESCRIPTION statping-ng Preset by the template
NAME statping-ng Preset by the template

Ports and volumes

Ports
8080
Volumes
1 named mount: app -> /app

Statping-ng FAQ

How much memory does Statping-ng need?

The catalog lists about 128 MiB of memory for Statping-ng.

Does Statping-ng run on arm64?

For Statping-ng, arm64 support is not confirmed; amd64 is unknown.

What licence is Statping-ng under?

Statping-ng is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.

Does Statping-ng need configuration before it starts?

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

Which ports does Statping-ng use?

Statping-ng listens on port 8080 inside the stack.

Where does Statping-ng keep its data?

In a named volume: app mounted at /app.

Can I deploy Statping-ng 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 statping-ng for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image adamboutcher/statping-ng:v0.90.78 is what you deploy there.

levelrail-cli templates install statping-ng --name my-statping-ng