Self-host Homebox with Levelrail
A home inventory and organization system for tracking what you own and where it is.
- Authorsysadminsmedia
- LicenceAGPL-3.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host Homebox
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/sysadminsmedia/homebox:0.11.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 7745.
-
Fill in the secrets
1 setting is 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.
Homebox requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 7745
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) 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 7745 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Homebox. 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 Homebox docs page.
Deploy Homebox your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Homebox from the CLI
levelrail-cli templates deploy homebox --name my-homebox Deploy Homebox with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/homebox/deploy Homebox configuration
Homebox services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| homebox | ghcr.io/sysadminsmedia/homebox:0.11.1 | 7745 | homebox_data -> /data |
Homebox environment variables
| Variable | Service | Value |
|---|---|---|
| HBOX_OPTIONS_ALLOW_REGISTRATION | homebox | Preset by the template |
Ports and volumes
- Ports
- 7745
- Volumes
- 1 named mount: homebox_data -> /data
Homebox FAQ
How much memory does Homebox need?
The catalog lists about 256 MiB of memory for Homebox.
Does Homebox run on arm64?
For Homebox, an arm64 image is published; amd64 is image published.
What licence is Homebox under?
Homebox is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Homebox need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Homebox use?
Homebox listens on port 7745 inside the stack.
Where does Homebox keep its data?
In a named volume: homebox_data mounted at /data.
Can I deploy Homebox 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 homebox for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/sysadminsmedia/homebox:0.11.1 is what you deploy there.