Digital Signage/Displays: Difference between revisions

Jump to navigation Jump to search
m
 
(8 intermediate revisions by the same user not shown)
Line 3: Line 3:
= Prerequisites =
= Prerequisites =
You will need a few prerequisites before this will work:
You will need a few prerequisites before this will work:
* A TV/Monitor (preferable mounted) to display content
* A TV/Monitor (preferably mounted) to display content
* A RaspberryPi or similar SBC (I've also used LibreComputer LePotato SBC running Armbian)
* A RaspberryPi or similar SBC (I've also used LibreComputer LePotato SBC running Armbian)
* A webserver to serve up the content you want to show (preferably external to the SBC)
* A webserver to serve up the content you want to show (preferably external to the SBC)
=== Display 1 ===
=== Basic Display===
This is the most basic configuration you can use to turn a RaspberryPi/SBC into a digital sign/display that serves up a web page when started.
This is the most basic configuration you can use to turn a RaspberryPi/SBC into a digital sign/display that serves up a web page when started.
==== Software ====
==== Software ====
Line 62: Line 62:
</syntaxhighlight>
</syntaxhighlight>
===== Turn on autologin =====
===== Turn on autologin =====
1. Create the required directory with '''''mkdir /etc/systemd/system/getty@tty1.service.d'''''
1. Create the required directory with:
<syntaxhighlight lang="bash">
mkdir /etc/systemd/system/getty@tty1.service.d
</syntaxhighlight>


2. Create the '''''autologin.conf''''' file in /etc/systemd/system/getty@tty1.service.d and add the contents below.
2. Create the '''''autologin.conf''''' file in the newly created '''''/etc/systemd/system/getty@tty1.service.d''''' directory and add the contents below.


Note:  Change '''''kiosk''''' below to the username that will be used for autologin if you are using something different (root is not recommended)
Note:  Change '''''kiosk''''' below to the username that will be used for autologin if you are using something different (root is not recommended)
Line 79: Line 82:
</syntaxhighlight>
</syntaxhighlight>


Ensure this is enabled with '''''systemctl status getty@tty1''''':
Ensure this is enabled with:
<syntaxhighlight lang="bash">
systemctl status getty@tty1
</syntaxhighlight>


<syntaxhighlight lang="text">
<syntaxhighlight lang="text">
Line 95: Line 101:
             └─776 /sbin/agetty -o "-p -- \\u" --noclear - linux
             └─776 /sbin/agetty -o "-p -- \\u" --noclear - linux
</syntaxhighlight>
</syntaxhighlight>
Run the following command if the service isn't enabled:
<syntaxhighlight lang="bash">
systemctl enable getty@tty1
</syntaxhighlight>
===== Set kiosk user .profile =====
===== Set kiosk user .profile =====
Change /home/kiosk/.profile to the contents below:
Change '''''/home/kiosk/.profile''''' to the contents below:


<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
Line 146: Line 158:
#[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && startx -- -nocursor
#[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && startx -- -nocursor
</syntaxhighlight>
</syntaxhighlight>
==== First Time Startup ====
==== First Time Startup ====
Now restart the SBC and it should automatically login as your kiosk user and stop at the command prompt.
Now restart the SBC and it should automatically login as your kiosk user and stop at the command prompt.
===== Additional Configuration =====
===== Additional Configuration =====
If you need to do additional configuration for Chromium (install an autorefresh or other extension(s), change screen size, etc). then start the browser with
If you need to do additional configuration for Chromium (install an autorefresh or other extension(s), change screen size, etc). then start the browser with:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
startx
startx
Line 161: Line 174:


The SBC will boot up and launch Chromium to show the web page you specified.
The SBC will boot up and launch Chromium to show the web page you specified.
=== Display 2 ===
 
=== Display with Remote Management===
This builds off the Display 1 setup with some additional features:
This builds off the Display 1 setup with some additional features:
* VNC using NOVNC.  This allows remote control of the display via a web browser.
* VNC using NOVNC.  This allows remote control of the display via a web browser.
Line 312: Line 326:
You can manage the device by pointing a web browser at '''''https://<device IP>:6080'''''
You can manage the device by pointing a web browser at '''''https://<device IP>:6080'''''
* When prompted accept the invalid certificate
* When prompted accept the invalid certificate
* Login to NOVNC using the password you create using vncpasswd
* Login to NOVNC using the password you created using vncpasswd
 
= Miscellaneous =
Sometimes things happen and the display will "get stuck" or lose internet connectivity.  When this happens you have a few options:
# Setup a nightly reboot event via crontab or systemd timers
# Setup a watchdog to look for lost network connectivity and restart the system

Navigation menu