Every time we change something at the schema, we either need to manually migrate the database or nuke the db. Find a way to make that automated.

There are some hardcoded URLs in the server, such as the address of the server itself, or the default website. That should be fixed, by having some sort of configuration view, or dynamically determining the URLs

The admin panel is wide open now. We should fix that.

Instead of downloading the client separately, it should be generated on the server. Even better if it were to be auto-installed, thinking of something along the lines of curl http://signman/client_install | bash (yes, I know, not so nice, but we gotta start somewhere)

All my displays run Amrbian on an OrangePi. I should build an Armbian Image with all that we need...

Details: https://docs.armbian.com/Developer-Guide_Build-Preparation/

The URL view is confusing if you don't use speaking urls. Add a mandatory unique description field and use that in the sign/url view instead of the URL

https://clevertap.com/blog/using-raspberry-pi-to-build-a-commercial-grade-wall-information-dashboard/

How to setup a client?

• Requirements
• Best practices

The client restarts the browser every time its cron job is run. That shouldn't be necessary, or should at least be made optional

This is getting somewhere, should we make a website?

Standard Templates like https://blackrockdigital.github.io/startbootstrap-new-age/ or https://blackrockdigital.github.io/startbootstrap-creative/ as a start, and just drop in a bit of content.