Cloud install

You can run Dashkiosk on a PaaS like Heroku or Dokku. The Chromecast support is unlikely to work in this case but the remaining functionalities should work without any problem. The following documentation is done using Heroku. The process should be quite similar with another provider.

We assume that you already have an account registered on Heroku. It comes with a free tier which should be sufficient to test Dashkiosk.

Deployment tool installation

The first step is to install the deployment tool. For Heroku, follow the install documentation.

Create the application

The next step is to create the Dashkiosk application. For that purpose, a modified buildpack needs to be used as Dashkiosk is using grunt to be built:

$ git clone
$ cd dashkiosk
$ heroku create
$ heroku config:set NPM_CONFIG_PRODUCTION=false

You can then push the application:

$ git push heroku master

If you want a custom branding, you have to use the following command:

$ heroku config:set branding=exoscale

Configure a database

By default, Dashkiosk will use an SQLite database. However, with a PaaS, this means that the database will be lost at each deployment. It is therefore more convenient to use a MySQL database:

$ heroku addons:create heroku-postgresql:hobby-dev
$ heroku pg:wait
$ heroku config -s | grep HEROKU_POSTGRESQL

The settings are available through environment variables. Unfortunately, Dashkiosk won’t use them. It is also possible to put them into a credential file but Dashkiosk won’t know how to use them either.

The easiest way is to arrange for those settings to be available as environment variables under the right name:

$ heroku config:set db__options__dialect=postgres
$ heroku config:set
$ heroku config:set db__options__port=6212
$ heroku config:set db__database=db982398
$ heroku config:set db__username=user3123
$ heroku config:set db__password=passkja83kd8

Deploy the application

The application can now be deployed:

$ git push heroku master

If you get a problem, use the log subcommand:

$ heroku logs --tail


Upgrading is just a matter of pulling new changes and pushing them to the PaaS:

$ git pull
$ git push heroku master