Self-host Baby Buddy with Levelrail
Track sleep, feeding, diaper changes, and growth for a baby or toddler, with charts and timers.
- Authorbabybuddy
- LicenceBSD-2-Clause
- Memory256 MiB
- Archarm64
- Services1
How to self-host Baby Buddy
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/babybuddy:latest
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
3 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.
Baby Buddy requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- BSD-2-Clause, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8000 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (lscr.io/linuxserver/babybuddy:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Baby Buddy. 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 Baby Buddy docs page.
Deploy Baby Buddy your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Baby Buddy from the CLI
levelrail-cli templates deploy babybuddy --name my-babybuddy Deploy Baby Buddy with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/babybuddy/deploy Baby Buddy configuration
Baby Buddy services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| babybuddy | lscr.io/linuxserver/babybuddy:latest | 8000 | babybuddy_config -> /config |
Baby Buddy environment variables
| Variable | Service | Value |
|---|---|---|
| CSRF_TRUSTED_ORIGINS | babybuddy | Preset by the template |
| PGID | babybuddy | Preset by the template |
| PUID | babybuddy | Preset by the template |
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: babybuddy_config -> /config
Baby Buddy FAQ
How much memory does Baby Buddy need?
The catalog lists about 256 MiB of memory for Baby Buddy.
Does Baby Buddy run on arm64?
For Baby Buddy, an arm64 image is published; amd64 is image published.
What licence is Baby Buddy under?
Baby Buddy is licensed under BSD-2-Clause, which is permissive, with few conditions on reuse.
Does Baby Buddy need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Baby Buddy use?
Baby Buddy listens on port 8000 inside the stack.
Where does Baby Buddy keep its data?
In a named volume: babybuddy_config mounted at /config.
Can I deploy Baby Buddy 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 babybuddy for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/babybuddy:latest is what you deploy there.