Docker Container for TileBoard: "A simple yet highly configurable Dashboard for HomeAssistant"
This repository has been archived on 2021-06-21. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
akloeckner 0c95977e66 Add check for master changes
This can abort the whole pipeline, because releases also show up as a commit.
2021-05-10 09:35:10 +00:00
.drone.yml Add check for master changes 2021-05-10 09:35:10 +00:00
.gitignore Recreate container build and tagging 2021-03-20 18:28:40 +01:00
Dockerfile Add Download to Dockerfile for more transparency 2021-04-22 22:27:46 +02:00
Dockerfile.nightly Add nightly Dockerfile 2021-05-10 09:14:23 +00:00
README.md Add nightly build to README 2021-05-10 09:25:16 +00:00
build.sh Re-enable exit 2021-04-22 22:28:49 +02:00
check-master-for-changes.sh Add check for changes in master branch 2021-05-10 09:33:11 +00:00

README.md

TileBoard Docker-Container

Build Status Docker Pulls

This is a very basic Docker container for TileBoard, "a simple yet highly configurable Dashboard for HomeAssistant".

It contains the sources and starts a simple Python3 webserver to serve TileBoard at port 8000.

Contribute

You can open any new issues here. The builds are automated on changes of the official TileBoard repository.

Have a look at the Dockerfile.

Usage

You have to mount your config.js file into the /tileboard directory of the Docker container. You can see an example config.js file in the official repository.

Versions / Tags

Besides the latest version, you can listen to updates for a specific version:

  • fbrinker/tileboard (same as :latest)
  • fbrinker/tileboard:latest
  • fbrinker/tileboard:2
  • fbrinker/tileboard:2.2
  • fbrinker/tileboard:2.2.0

Additionally, there are nightly and dev builds as follows:

  • fbrinker/tileboard:nightly contains a nightly build of TileBoard's master branch. Use it to have the mode bleeding adge changes, which have not yet made it to a release version.
  • fbrinker/tileboard:dev bundles TileBoard's source code and runs yarn run dev inside the container. Use it to modify the source, check your changes into GitHub and propose a pull request to TileBoard. See the TileBoard contribution page for details.

Example

Here is an example, using Docker-Compose:

version: '3'
services:

  tileboard:
    image: fbrinker/tileboard
    volumes:
      - ./config.js:/tileboard/config.js
    ports:
      - "8234:8000"

After a docker-compose up -d, you can reach your TileBoard instance under http://[yourhost-or-ip]:8234.

Extended Example

I am using it in my docker-compose file like this, with my config.js, secrets and other customizations:

# Home Assistant TileBoard
tileboard:
  container_name: tileboard
  image: fbrinker/tileboard
  hostname: tileboard
  volumes:
    - ./tileboard/config/config.js:/tileboard/config.js
    - ./tileboard/config/secrets.js:/tileboard/includes/config/secrets.js
    - ./tileboard/config/pages:/tileboard/includes/pages
    - ./tileboard/styles/background.png:/tileboard/images/background.png
    - ./tileboard/styles/custom.css:/tileboard/styles/custom.css
  ports:
    - "8234:8000"
  restart: unless-stopped
  depends_on:
    - homeassistant

Note: You should never expose TileBoard to the web.