Local webserver to host kiosk content #2
Description
I think a good architecture would be nginx running a simple html/css/js webserver on the local docker-host box as a landing page, similar to the 3d printer landing page we have currently.
This could be loaded with kiosk.somkeit.org.uk internally (and externally if appropriate via existing reverse proxy and optional existing authentication) and would be the home page for the kiosk.
Content would then either be directly served from that webserver or linked from there (wiki, members etc) Would be worth putting some effort into preventing caching of credentials or at least warnings, so no one leaves it logged in, but this isn't a requirement given this doesn't seem to be a problem with other space PC's.
Will need to review if we simply restructure the existing nginx container for 3d printing and change the URL or add this in addition and link to it. This will largely be driven by the complexities of DNS and reverse proxy. Also do we want a user experience of 3dprinter.somakeit.org.uk and kiosk.somakeit.org.uk or migrate 3d printer to a page within kiosk that can be bookmarked on the 3d printer PC just as easily, given I expect very few people are using it at present.