This document presents several supported scenarios for using KioskForge. Actual samples are a work in progress.
This is the simplest case, the one that KioskForge was originally made for. With this scenario, you'll get a finished kiosk ready to deploy using a Raspberry Pi 4B or 5 with at least 2 gigabytes of RAM and your choice of storage medium.
Hint: The website to be displayed should support the default resolution that your (touch) screen supports.
Please read the Manual for instructions on installing KioskForge, Python, and Raspberry Pi Imager, and on using KioskForge with these tools. Expect to redeploy a few times until all settings are at their correct values.
When you want to display a remote website using your new kiosk, you have to focus primarily on these options:
| Name | Option name | Comment |
|---|---|---|
| Comment | comment |
A string describing the kiosk and its purpose (for your records). |
| Kiosk type | type |
This should be web to launch Chromium in X11. |
| Command | command |
The URL of the starting page of the website that you want the kiosk to browse. |
| Sound card | sound_card |
One of none, auto, jack,
hdmi1, or hdmi2. Jack requires an
amplifier! |
| Sound volume | sound_level |
The logarithmic audio volume from 0 through 100 (80 is
typically a good choice). |
| Mouse cursor | mouse |
This should be be set to auto to enable the mouse if no
touchscreen is present. |
| Idle timeout | idle_timeout |
This should be set to a non-zero number of seconds, say
300, between restarts 1. |
| Screen rotation | screen_rotation |
none = default, left = rotate left, flip = flip upside-down, right = rotate right. |
| CPU overclocking | cpu_boost |
This should probably be enabled (Pi 4B only) to make the browser faster. |
| Wi-Fi boost | wifi_boost |
This should probably be enabled (true) to load pages as
fast as possible. |
NOTE: The current method of reloading the starting page by gracefully terminating and restarting the web browser is far from optimal. A better solution may come up someday.
You still need to supply values for all the other options that are
described in the kiosk file (*.kiosk).
This case is very useful for displaying a static, local website without network access (except, perhaps, for upgrading the kiosk).
An example of this is a website that displays a set of images with titles, one at a time, and then, after a certain interval, moves on to the next image. Once the end is reached, the display restarts from the first image.
Hint: The website to be displayed should support the default resolution that your (touch) screen supports.
Hint: You may want to resize large images to a smaller size, such as Full HD (1920x1080), to not overload the Pi.
Please read the Manual for instructions on installing KioskForge, Python, and Raspberry Pi Imager, and on using KioskForge with these tools. Expect to redeploy a few times until all settings are correct.
When you want to display a local website using your new kiosk, you especially have to be aware of these options:
| Name | Option name | Comment |
|---|---|---|
| Comment | comment |
A description of the kiosk and its purpose (for your records). |
| Sound card | sound_card |
This should be set to none as pictures don't include
sound. |
| Mouse cursor | mouse |
This should be be set to auto to enable the mouse if no
touchscreen is present. |
| Idle timeout | idle_timeout |
This should be set to zero, as the user will not be able to navigate away from your site. |
| CPU overclocking | cpu_boost |
This could well be disabled (false) as displaying
images does not require much CPU. |
| Wi-Fi boost | wifi_boost |
This should probably be disabled (false) as local
websites require no LAN access. |
You still need to supply values for all the other options that are
described in the kiosk file (*.kiosk).
Many kiosks have touch screens. This section highlights the most important options related solely to screens and touchscreens.
Please read the Manual for instructions on installing KioskForge, Python, and Raspberry Pi Imager, and on using KioskForge with these tools. Expect to redeploy a few times until all settings are correct.
The important options to be aware of, when forging a kiosk with a touch screen, are these:
| Name | Option name | Comment |
|---|---|---|
| Mouse cursor | mouse |
This should be be set to auto to enable the mouse if no
touchscreen is present. |
| Screen Rotation | screen_rotation |
If the screen needs to be rotated, use a value other than
none. |
| Chromium Autoplay | chromium_autoplay |
If videos need to play immediately upon page load (no user interaction required). |
You still need to supply values for all the other options that are
described in the kiosk file (*.kiosk).
Rude customers may sabotage the kiosk (young people often do this); the restart of the browser resets such sabotage.↩︎