Self-host Homer with Levelrail
VerifiedA dead simple static start page for your services, configured with a single YAML file.
- Authorbastienwirtz
- LicenceApache-2.0
- Memory128 MiB
- Archarm64
- Services1
How to self-host Homer
-
Pull the images
One image is pulled on your server.
Show images
b4bz/homer:v24.05.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 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.
Homer requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Verified. Verified on arm64 with image tag v24.05.1. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 8080 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 Homer. 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 Homer docs page.
Deploy Homer your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Homer from the CLI
levelrail-cli templates deploy homer --name my-homer Deploy Homer with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/homer/deploy Homer configuration
Homer services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| homer | b4bz/homer:v24.05.1 | 8080 | homer_assets -> /www/assets |
Homer environment variables
| Variable | Service | Value |
|---|---|---|
| INIT_ASSETS | homer | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: homer_assets -> /www/assets
Homer FAQ
How much memory does Homer need?
The catalog lists about 128 MiB of memory for Homer.
Does Homer run on arm64?
For Homer, arm64 is tested; amd64 is image published.
What licence is Homer under?
Homer is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Homer need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Homer use?
Homer listens on port 8080 inside the stack.
Where does Homer keep its data?
In a named volume: homer_assets mounted at /www/assets.
Can I deploy Homer on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Homer, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image b4bz/homer:v24.05.1 is what you deploy there.