3 The fastest and recommended way to get your Homer instance up and running is
4 with Docker. The Docker image comes with a web server built-in so that all you
5 need to worry about is your config file.
7 Internally, the Docker image looks for the assets in the `/www/assets` directory
8 so you can bind a volume from your host machine to that directory in order to
9 modify and persist the configuration files. The web server serves the dashboard
10 on port 8080, but using a port binding will let you expose that to whatever
11 external port you like.
20 -v </your/local/assets>:/www/assets \
25 Use `UID` and/or `GID` env var to change the assets owner:
30 -v </your/local/assets>:/www/assets \
31 -e "UID=1000" -e "GID=1000" \
38 It is recommended to use docker-compose to manage your Docker containers, and
39 below you can find a simple compose yaml file. Copy the contents into a
40 `docker-compose.yaml` and modify the volume binding to your desired directory to
49 - /your/local/assets:/www/assets
58 cd /path/to/docker-compose.yml
62 Use `UID` and/or `GID` env var to change the assets owner:
70 - /your/local/assets:/www/assets
79 ## Shipping your own web server
81 ### Prebuilt release tarball
83 Download and extract the latest release (`homer.zip`) from the [release page](https://github.com/bastienwirtz/homer/releases), rename the `assets/config.yml.dist` file to `assets/config.yml`, and put it behind a web server.
86 wget https://github.com/bastienwirtz/homer/releases/latest/download/homer.zip
89 cp assets/config.yml.dist assets/config.yml
90 npx serve # or python -m http.server 8010 or apache, nginx ...
93 ### Building from source
96 # Using yarn (recommended)
105 Then your dashboard is ready to use in the `/dist` directory.