Self-host KitchenOwl with Levelrail
A shared grocery list, recipe and expense app for your household, with web and mobile clients.
- AuthorTomBursch
- LicenceAGPL-3.0-only
- Memory256 MiB
- Services1
How to self-host KitchenOwl
-
Pull the images
One image is pulled on your server.
Show images
tombursch/kitchenowl:v0.8.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 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 the first account on the web page, it becomes the admin.
KitchenOwl requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) 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 KitchenOwl. 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 KitchenOwl docs page.
Deploy KitchenOwl your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy KitchenOwl from the CLI
levelrail-cli templates install kitchenowl --name my-kitchenowl Deploy KitchenOwl with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/kitchenowl/install \
-d '{
"name": "my-kitchenowl"
}' KitchenOwl configuration
KitchenOwl services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| kitchenowl | tombursch/kitchenowl:v0.8.1 | 8080 | data -> /data |
KitchenOwl environment variables
| Variable | Service | Value |
|---|---|---|
| JWT_SECRET_KEY | kitchenowl | Generated at deploy |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: data -> /data
KitchenOwl FAQ
How much memory does KitchenOwl need?
The catalog lists about 256 MiB of memory for KitchenOwl.
Does KitchenOwl run on arm64?
For KitchenOwl, arm64 support is not confirmed; amd64 is unknown.
What licence is KitchenOwl under?
KitchenOwl is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does KitchenOwl need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does KitchenOwl use?
KitchenOwl listens on port 8080 inside the stack.
Where does KitchenOwl keep its data?
In a named volume: data mounted at /data.
Can I deploy KitchenOwl 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 kitchenowl for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image tombursch/kitchenowl:v0.8.1 is what you deploy there.