kiosk-browser

Generic kiosk-mode browser.

Build & Install

1. Install NodeJS and Yarn.
2. Install native package dependencies with make install.
3. Build a Debian/Ubuntu package with make build.
4. Install it with sudo dpkg -i dist/kiosk-browser_*.deb.
5. Run with the URL you want to visit as a CLI argument (e.g. kiosk-browser https://example.com/) or with an environment variable (e.g. KIOSK_BROWSER_URL=https://example.com/ kiosk-browser).

Kiosk Page API

Web pages loaded by kiosk-browser have an extra API accessible via the global kiosk object.

kiosk.saveAs(): Promise<FileWriter | undefined>

Presents a file save dialog to the user and, if a file is chosen, resolves to an object with write(data) and end() methods, similar to fs.WriteStream from NodeJS. To use this API, the requesting origin must be allowed to write to disk.

File Access APIs

To access the file system, a host must be granted access with --add-file-perm [HOST:]PATH[:ACCESS]. For example, --add-file-perm localhost:**/*:rw grants localhost read-write access anywhere. Access modifiers: rw (default, read-write), ro (read-only), and wo (write-only). Note that the order permissions are added is important. If you add a permission that says access to /media/**/* is read-only first, then another that says /media/usb-stick/**/* is read-write, access to /media/usb-stick/file.txt will be read-only because the first permission matches the path. To fix this, reverse the order.

Debugging

First, check the command-line help:

$ kiosk-browser --help

If something isn't working as you'd expect it to, try running with debug logging:

$ DEBUG=kiosk-browser:* kiosk-browser https://example.com/

Development

If you're working on a bug fix or feature for kiosk-browser, here's how to build and run it in development:

1. Install NodeJS and Yarn.
2. Install native package dependencies with make install.
3. Run with yarn start. Changes will not automatically be picked up, so just Ctrl-C the yarn start and run it again.

Kiosk browser has a number of command line arguments you can use if you want the permissions and print config to mimic production while also having access to devtools. You probably want to run kiosk-browser locally with the following command:

DEBUG=kiosk-browser:* DISPLAY=:0 KIOSK_BROWSER_ALLOW_DEVTOOLS=true KIOSK_BROWSER_URL=http://localhost:3000/ KIOSK_BROWSER_FILE_PERMISSIONS='o=http://localhost:3000,p=/**/*,rw' yarn start

License

GPL-3.0