The server is a Node.js application providing a rendez-vous point for all displays to subscribe using a Websocket protocol as well as an administration page to manage all displays, group them and tell them which URL to display.
Server and receiver¶
The simpler way to get Dashkiosk is to use the Docker image:
$ docker run -d -p 8080:8080 \ -v /var/lib/dashkiosk/database:/database \ ghcr.io/vincentbernat/dashkiosk:latest
If you need Chromecast support, you need to use
$ docker run --net=host \ -v /var/lib/dashkiosk/database:/database \ -e "chromecast__enabled=1" \ -e "chromecast__receiver=http://<DOCKER_HOST_IP>:8081/receiver" \ -e "port=8081" \ ghcr.io/vincentbernat/dashkiosk:latest
Alternatively, you need to execute the following step:
Grab the latest tarball for Dashkiosk from GitHub.
Install Node.js and optionally npm. Currently, Dashkiosk works with Node.js 0.12.x or more recent. If the version available in your distribution is not up-to-date, have a look at how to install Node.js via the package manager before trying to build from the sources.
Unpack Dashkiosk in the directory of your choice and go into that directory.
Install the appropriate dependencies with the following commands:$ npm install
Build the final version of Dashkiosk with the following command:$ grunt
Upon success, you will get a
distdirectory that you can put on some server. It includes both the receiver and the server part. Then:$ cd dist && npm install --production
If you want to use the Android application, you still need to build it and install it. See Android application.
If you get an error while compiling mDNS extension on Linux, ensure
you have the appropriate development package for Avahi. Specifically,
on Debian, you need
Dashkiosk stores its data inside some database. By default, it uses SQLite. If you prefer to use another database, this is quite easy. We will use PostgreSQL but this should be easy to transpose to another database supported by Sequelize.js, the ORM used in Dashkiosk. The databases currently supported are:
Here are the steps:
Create a dedicated user inside your RDBMS. For PostgreSQL, this is done as the
postgresuser with the following command:$ createuser -P dashkiosk Enter password for new role: Enter it again: Shall the new role be a superuser? (y/n) n Shall the new role be allowed to create databases? (y/n) n Shall the new role be allowed to create more new roles? (y/n) n
Create an empty database. For PostgreSQL, this is also done as the
postgresuser:$ createdb -O dashkiosk dashkiosk
The database will be populated automatically when running Dashkiosk for the first time.
By default, displays are put in a group with a dashboard with cycling
images. You can add more images in
app/images/unassigned if you
want. Then, rebuild with
To upgrade, you can use the exact same instructions that you used for installation. You can choose to do an in-place upgrade if you want to:
$ npm install $ grunt
If you kept the default SQLite database, be sure to save it (it’s in
dist/db/) before upgrading and restore it after upgrade. The
dist/ directory where Dashkiosk is built is wiped out on