Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
Encore
Encore is the Backend Development Platform purpose-built to help you create event-driven and distributed systems.
-
koboscout
Koboscout is a web application that displays a simple chart of your latest Continuous Glucose Monitoring (CGM) on an e-reader, such as a Kobo device. It is a way of making glucose readings 'ambient' - quietly present in your environment without actively clamouring for attention.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
glucoscape
Glucoscape is a small application that helps visualize Continuous Glucose Monitoring (CGM) data quickly and intuitively. It provides a heatmap representation of time spent below range, in range, and above range, allowing for easy identification of glucose patterns.
-
nightscout-widget-electron
An Electron widget application to show on a desktop blood glucose value is getting from Nightscout API
There's a good list of frameworks here:
https://github.com/mingrammer/go-web-framework-stars?tab=rea...
But you won't find anything that's anywhere near as comprehensive and batteries-included as Rails or Django.
A good alternative to writing your own echo server and debugging requests one route at a time is requestbin, which will gladly take any requests you throw at it, log them, and optionally return a response of your choice.
Lots of different implementations and hosts: https://duckduckgo.com/?q=requestbin
Slightly related, but I've also been working on and off for a few years on my own Type 1 Diabetes management solution (https://github.com/algao1/iv3).
I haven't had time to work on it recently, but it uses ntfy (https://ntfy.sh/) to send alerts and such.
I was thinking of eventually incorporating some kind of automatic remedial solution eventually to help keep my glucose in range, but haven't had any time to look into it yet.
Slightly related, but I've also been working on and off for a few years on my own Type 1 Diabetes management solution (https://github.com/algao1/iv3).
I haven't had time to work on it recently, but it uses ntfy (https://ntfy.sh/) to send alerts and such.
I was thinking of eventually incorporating some kind of automatic remedial solution eventually to help keep my glucose in range, but haven't had any time to look into it yet.
Many years ago, I went a similar route and built a small T1D monitoring stack from scratch for myself. It even pretended to be a Dexcom Follow client so I could get CGM from Dexcom in near real-time. When Dexcom eventually changed their internal APIs and broke my data ingestion, I decided to finally give Nightscout a shot. I've never looked back since.
As I see it, the big advantage of Nightscout is that it is a de facto standard interface, with many integrations already existing. And it's easy to build add-on apps on top of its API. I've built about four myself [0], [1] and there is a big community of users and developers building other things such as [2], [3], [4]...
Even though Nightscout is a little bit messy and requires MongoDB, it's surprisingly easy to self-host. I'm using the stock docker-compose file from the main repo with only minor modifications. I run it on a $6/mo VPS. As an alternative, there are two or three hosted Nightscout services costing little more than that.
I highly recommend you to consider going this "standard" Nightscout route because it can save you work (and worries) in the future, and you get to connect with the community around it. In my experience, going all alone from the start was not worth it.
[0] https://github.com/vitawasalreadytaken/koboscout