what if workers had a web server?

[CamDavidsonPilon]

• start to replace pios commands with API endpoints -> pios no longer SSHs, just sends API requests.
• can have access to local calibrations, plugins
• API:
  • GET ??: returns which jobs are running
  • GET ??: which plugins are installed
  • PATCH ??: replaces monitor run callback.
• start of change towards #232
• lighttpd + flask again.
  • same port as main ui (look in config.ini)
• maybe a ui with very basic information for debugging?
  • config.ini?
  • read-only view of JobManager database?
• how do pumps, leds get updated quickly? This can be decided later.

Changes required to workers

• [ ] install lighttpd
• [ ] install all the other ui python libs (list needed)
• [ ] install services

[CamDavidsonPilon]

This makes me want to merge the images: the python requirements are nearly the same, same folder for www, lots of similar services. However, no MQTT, no db app, no mqtt-to-db, chrony, okay yea no merge yet.

[CamDavidsonPilon]

It is a good idea to restrict hitting the worker api unless your leader. We can do this with lighttpd confs (and env variables).

[CamDavidsonPilon]

Basically the goal of this first is to remove any instances of ssh-ing from the leader to workers, replaced with web request to their servers.