Self-host Kener with Levelrail
A status page and uptime monitoring tool built with SvelteKit.
- Authorrajnandan1
- LicenceMIT
- Memory256 MiB
- Services2
How to self-host Kener
-
Pull the images
2 images are pulled on your server.
Show images
rajnandan1/kener:4.2.1-alpineredis:7-alpine
-
Create the app
2 services start in a single Compose app, with 3 named volume mounts for your data, on port 3000.
-
Fill in the secrets
1 secret is generated and stored encrypted, 4 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.
Kener requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000
- 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 Kener. 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 Kener docs page.
Deploy Kener your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Kener from the CLI
levelrail-cli templates deploy kener --name my-kener Deploy Kener with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/kener/deploy Kener configuration
Kener services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| kener | rajnandan1/kener:4.2.1-alpine | 3000 | kener_data -> /app/databasekener_uploads -> /app/uploads |
| redis | redis:7-alpine | none | redis_data -> /data |
Kener environment variables
| Variable | Service | Value |
|---|---|---|
| DATABASE_URL | kener | Preset by the template |
| KENER_SECRET_KEY | kener | Generated at deploy |
| ORIGIN | kener | Preset by the template |
| REDIS_URL | kener | Preset by the template |
| TZ | kener | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 3 named mounts: kener_data -> /app/database, kener_uploads -> /app/uploads, redis_data -> /data
Kener FAQ
How much memory does Kener need?
The catalog lists about 256 MiB of memory for Kener across its 2 services.
Does Kener run on arm64?
For Kener, arm64 support is not confirmed; amd64 is unknown.
What licence is Kener under?
Kener is licensed under MIT, which is permissive, with few conditions on reuse.
Does Kener need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Kener bundle?
The template includes Redis, running as its own service.
Which ports does Kener use?
Kener listens on port 3000 inside the stack.
Where does Kener keep its data?
In named volumes: kener_data mounted at /app/database, kener_uploads mounted at /app/uploads and redis_data mounted at /data.
Can I deploy Kener 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 kener for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image rajnandan1/kener:4.2.1-alpine, redis:7-alpine is what you deploy there.