kago VS mosquitto

The closest I’ve seen is https://github.com/kamalshkeir/kago it’s not only building the restful part but also the ORM using Go generics to match día go behavior. It even supports migrations

Feel free to join our discussions https://github.com/kamalshkeir/kago/discussions/7

exactly, chi is a very good router, but still not fit my use cases, so i make my own, that handle extra things i needed to have in my framework https://github.com/kamalshkeir/kago

i hate gin , donno echo very well, but i found that going from stdlib to build a small framework will give you very good experience, and the framework will be adapted to your need, feel free to check kago , a framework like django, very easy to get started with kago

Hello all, It may seem weird , but i will explain. KaGo is my new golang web framework, i deployed a website using it : kamalshkeir.dev , i tried my best to make this framework very secure, but i'm not an expert, that's why i think about this challenge for hacker gophers :p, to be able to find more vulnerabilities before people start using it. I give you all permissions to hack this website, so please feel free to tested like if it was you own website. Thank you all in advance

handle migration from struct , so detect when remove or add field to struct https://github.com/kamalshkeir/kago

https://github.com/kamalshkeir/kago , check the dependencies, you will see that everything is used, you can easily benchmark against gorm and against the standard library for example to compare performance , i have some benchmarks in the readme too

few days ago, i have maid a new portfolio/blog using my framework KaGo. I like to always run my small projects on vps and deploye them from scratch on ubuntu or centos, let's say to not forget my good practices. Long story short, i have never deployed an application using only the binary and systemd with a domain name and ssl, i have always used apache and nginx as proxy behind my app. Look at it now https://kamalshkeir.dev😁😁😁 , my gopher portdolio running listenandserveTLS with letsencrypt certificate, no proxy, no static files no templates , only the binary 9Mb running with systemd on the server. That's not all, my go app was using nothing from the power of my vps , less than 10% , so i said why i don't try grafana, prometheus, loki ..., all these good stuff. And that's why i'm so happy, i have finally the dashboard i have looking for, grafana dashboard , prometheus scraping all metrics from my go application, promtail and loki getting me the logs to the dashboard, node exporter showing me metrics for my linux system, and postgres exporter for my database, all in one place. i you want to look at it, you can 😁 , this is the link to grafana https://kamalshkeir.dev:9999 username: test password: testadmin

https://github.com/kamalshkeir/kago is pretty much like django, 2 min to get up and running

mosquitto_transport, an experiment of writing SObjectizer-based wrapper around mosquitto library;

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.