Mako VS mosquitto

https://www.makotemplates.org/ are also nice in that they have a return functionality which lets you exit templates early, which is nicer than big if/else statements in Jinja

At least in Python, that's kinda what https://www.makotemplates.org is. Although if you're just using a subset of PHP suitable for templating, it's not really clear to me what benefit there is to PHP syntax versus, say, Jinja2 syntax.

Mako already exists - https://www.makotemplates.org/. Nothing says you can't use the same name, but it will mean you won't be able to publish to pypi and your searchability will be bad

Mako is also a fairly popular python template library.

https://www.makotemplates.org/

My current tech stack is: Python3 with Mako and CherryPy. NGINX as a reverse proxy

References: Felipe Flop’s website https://www.filipeflop.com/blog/controle-monitoramento-iot-nodemcu-e-mqtt/ accessed on 01/27/2018. Eclipse server for MQTT Broker https://iot.eclipse.org/ accessed on 01/27/2018. Mosquitto https://mosquitto.org/ accessed on 01/27/2018. Cloud MQTT https://www.cloudmqtt.com/ accessed on 01/27/2018. DuckDNS https://www.duckdns.org/ accessed on 01/27/2018. Proftpd http://www.proftpd.org/ accessed on 01/27/2018. Filezilla https://filezilla-project.org/ accessed on 01/27/2018. Fritzing https://fritzing.org/ accessed on 05/25/2022. Appendices:

This is a perfect use case for MQTT, e.g. this library for ESP boards. Create a broker on the network (e.g. a Raspberry Pi running Mosquitto, and have all the ESP boards subscribe to a topic. When you want to play a sound, publish a message to the topic, and all of the ESPs should see it very quickly. You don't need to synchronize clocks any more because it's simply based on the timing of publishing a message.

While working on a personal project Komponist, I was due to update Mosquitto MQTT Broker due to a CVE and found some interesting changes that will impact me in the future when it comes to configuring the Broker. This post provides a solution to make the Broker compatible with future versions using new and less visited concepts in Docker Compose v2, namely:

Optional: Mosquitto, an open-source message broker that implements the MQTT protocol; this tutorial uses the public test server

I think he means implementation of MQTT protocol, like https://mosquitto.org/

Could MQTT work for you? You'd need a broker like Mosquitto, and then any of a number of MQTT clients.

MQTT is a message broker that's used commonly in IoT (internet of things). This is from all of one week's experience, so take it with a grain of salt, but it's a publisher/subscriber model where each device defines some channels (like openevse/wh openevse/amp etc) and then publishes its stats to an MQTT broker like Mosquitto. Then other services (I've tried it with HomeAssistant and openHAB) pull in the values to store them, drive automations, etc. OpenEVSE also subscribes to input channels that can control it, so I've seen people set up things like 'only allow the charger to run when my pool heater is not running'.