# Self-host Homer

> A dead simple static start page for your services, configured with a single YAML file.

- Page: https://levelrail.com/templates/homer/
- JSON: https://levelrail.com/templates/homer.json
- Category: Dashboard
- Licence: Apache-2.0 (Permissive license)
- Source: https://github.com/bastienwirtz/homer
- Upstream docs: https://github.com/bastienwirtz/homer/blob/main/docs/configuration.md

## Requirements
- Memory: about 128 MiB
- amd64: published, arm64: tested
- Needs configuration before start: no
- Pinned image tag: v24.05.1

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| homer | b4bz/homer | v24.05.1 | 8080 | homer_assets -> /www/assets |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| homer | INIT_ASSETS | preset |

## Deploy

### CLI

```bash
levelrail-cli templates deploy homer --name my-homer
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/homer/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## Questions

### 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.

Self-host Homer, Homer docker compose file, deploy Homer on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
