nightscout-widget-electron
koboscout
nightscout-widget-electron | koboscout | |
---|---|---|
1 | 1 | |
30 | 8 | |
- | - | |
9.0 | 3.3 | |
5 months ago | 6 months ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nightscout-widget-electron
koboscout
-
How I keep myself Alive using Golang
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