Equipment/Kiosk: Difference between revisions
(needs updated for new kiosk machine) |
(ansible control, document current hardware) |
||
Line 1: | Line 1: | ||
{{EquipmentInfobox | {{EquipmentInfobox | ||
|name= | |name=Kiosk2 <!-- Name of the item. --> | ||
|image=DSC_0708.JPG <!-- Image of the item. Leave with placeholder image if none exists. --> | |image=DSC_0708.JPG <!-- Image of the item. Leave with placeholder image if none exists. --> | ||
|model= | |model=HP ProDesk 400 G2.5 SFF <!-- Model --> | ||
|category=Equipment <!-- Main category. Please leave alone to keep item in this category --> | |category=Equipment <!-- Main category. Please leave alone to keep item in this category --> | ||
|subcat=Systems <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one --> | |subcat=Systems <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one --> | ||
Line 21: | Line 21: | ||
It runs Chrome with the Chrome window displayed on the kiosk, it then goes to this [https://github.com/londonhackspace/hackspace-foundation-sites/tree/master/london.hackspace.org.uk/kiosk] section of the london hackspace website for the UI. | It runs Chrome with the Chrome window displayed on the kiosk, it then goes to this [https://github.com/londonhackspace/hackspace-foundation-sites/tree/master/london.hackspace.org.uk/kiosk] section of the london hackspace website for the UI. | ||
There is also some code that talks to the card reader and pastes any card UIDs found into a hidden field on the web page. | There is also some code that talks to the card reader and pastes any card UIDs found into a hidden field on the web page. [https://github.com/londonhackspace/cardscanner] | ||
The config for kiosk2 is under ansible control. Theoretically to rebuild in the event of failure is to bootstrap debian and then point ansible at it. | |||
If the kiosk gets restarted you'll need to click the mouse once on the chrome window for it to get focus (or be activated or brought to the foreground or something like that) before it will read cards. | If the kiosk gets restarted you'll need to click the mouse once on the chrome window for it to get focus (or be activated or brought to the foreground or something like that) before it will read cards. | ||
It also runs waspd from here: https://github.com/londonhackspace/wasp-label-printer to talk to the printer. | It also runs waspd as a systemd service, code from here: https://github.com/londonhackspace/wasp-label-printer to talk to the printer, which isn't a st | ||
andard cups-supported printer. | |||
Obsolete code that is not used here: https://github.com/londonhackspace/enrolment | Obsolete code that is not used here: https://github.com/londonhackspace/enrolment |
Revision as of 17:43, 23 October 2021
This is the machine next to the club Mate fridge that drives the Membership_Kiosk, It runs Debian.
It runs Chrome with the Chrome window displayed on the kiosk, it then goes to this [1] section of the london hackspace website for the UI.
There is also some code that talks to the card reader and pastes any card UIDs found into a hidden field on the web page. [2] The config for kiosk2 is under ansible control. Theoretically to rebuild in the event of failure is to bootstrap debian and then point ansible at it.
If the kiosk gets restarted you'll need to click the mouse once on the chrome window for it to get focus (or be activated or brought to the foreground or something like that) before it will read cards.
It also runs waspd as a systemd service, code from here: https://github.com/londonhackspace/wasp-label-printer to talk to the printer, which isn't a st andard cups-supported printer.
Obsolete code that is not used here: https://github.com/londonhackspace/enrolment
See also Equipment/WASP_WPL305E, Membership_Kiosk