Docker Container for TileBoard: "A simple yet highly configurable Dashboard for HomeAssistant" https://hub.docker.com/r/fbrinker/tileboard
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Florian Brinker 7acbe3d55e Fix date handling for ISO8601 dates 5 months ago
.drone.yml feature: nightly and dev images (#5) 5 months ago
.gitignore Recreate container build and tagging 6 months ago
Dockerfile Add Download to Dockerfile for more transparency 5 months ago
Dockerfile.nightly feature: nightly and dev images (#5) 5 months ago
LICENSE.md Add license 5 months ago
README.md feature: nightly and dev images (#5) 5 months ago
build.sh Change "target" label to "docker" 5 months ago
check-master-for-changes.sh Fix date handling for ISO8601 dates 5 months ago

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 most bleeding edge changes, which have not made it into a release yet.
  • 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.