11 A dead simple static <strong>HOM</strong>epage for your serv<strong>ER</strong> to keep your services on hand, from a simple <code>yaml</code> configuration file.
16 <a href="https://homer-demo.netlify.app">Demo</a>
18 <a href="https://gitter.im/homer-dashboard/community">Chat</a>
20 <a href="#getting-started">Getting started</a>
24 <a href="https://opensource.org/licenses/Apache-2.0"><img
25 alt="License: Apache 2"
26 src="https://img.shields.io/badge/License-Apache%202.0-blue.svg"></a>
27 <a href="https://gitter.im/homer-dashboard/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge"><img
29 src="https://badges.gitter.im/homer-dashboard/community.svg"></a>
30 <a href="https://github.com/bastienwirtz/homer/releases/latest/download/homer.zip"><img
31 alt="Download homer static build"
32 src="https://img.shields.io/badge/Download-homer.zip-orange"></a>
33 <a href="https://github.com/awesome-selfhosted/awesome-selfhosted"><img
35 src="https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg"></a>
39 <img src="docs/images/screenshot.png" width="100%">
44 - [Features](#features)
45 - [Getting started](#getting-started)
46 - [Configuration](https://bastienwirtz.github.io/homer/configuration)
47 - [Custom services](https://bastienwirtz.github.io/homer/custom_services)
48 - [Tips & tricks](https://bastienwirtz.github.io/homer/tips_and_tricks)
49 - [Development](https://bastienwirtz.github.io/homer/development)
50 - [Troubleshooting](https://bastienwirtz.github.io/homer/troubleshooting)
54 - [yaml](http://yaml.org/) file configuration
59 - Offline health check
61 - `/` Start searching.
62 - `Escape` Stop searching.
63 - `Enter` Open the first matching result (respects the bookmark's `_target` property).
64 - `Alt`/`Option` + `Enter` Open the first matching result in a new tab.
70 The fastest and recommended way to get your Homer instance up and running is
71 with Docker. The Docker image comes with a web server built-in so that all you
72 need to worry about is your config file.
74 Internally, the Docker image looks for the assets in the `/www/assets` directory
75 so you can bind a volume from your host machine to that directory in order to
76 modify and persist the configuration files. The web server serves the dashboard
77 on port 8080, but using a port binding will let you expose that to whatever
78 external port you like.
87 -v </your/local/assets>:/www/assets \
92 Use `UID` and/or `GID` env var to change the assets owner:
97 -v </your/local/assets>:/www/assets \
98 -e "UID=1000" -e "GID=1000" \
105 It is recommended to use docker-compose to manage your Docker containers, and
106 below you can find a simple compose yaml file. Copy the contents into a
107 `docker-compose.yaml` and modify the volume binding to your desired directory to
116 - /your/local/assets:/www/assets
125 cd /path/to/docker-compose.yml
129 Use `UID` and/or `GID` env var to change the assets owner:
137 - /your/local/assets:/www/assets
146 ### Shipping your own web server
148 #### Prebuilt release tarball
150 Download and extract the latest release (`homer.zip`) from the [release page]
151 (https://github.com/bastienwirtz/homer/releases), rename the
152 `assets/config.yml.dist` file to `assets/config.yml`, and put it behind a web
156 wget https://github.com/bastienwirtz/homer/releases/latest/download/homer.zip
159 cp assets/config.yml.dist assets/config.yml
160 npx serve # or python -m http.server 8010 or apache, nginx ...
163 #### Building from source
166 # Using yarn (recommended)
175 Then your dashboard is ready to use in the `/dist` directory.