Making chrome-uploader more optionally standalone

[AdrianLxM]

I think there should be an option "offline" that makes the programme not to connect to mongolab automatically. Explicit import/backfill could still be allowed.

I use the chrome-uploader as a standalone programme as it is the only programme for the Dexcom on linux and even though there is another 3rd-party semiofficial programme for Macintosh, I assume there also exist standalone users on this platform.

A) Even if no mongolab is configured in the options, it tries to connect to it. This happens with an invalid URL.

B) In some cases it might be good not to upload data even though mongolab is configured. Those cases might be: Bad/slow/interrupted (mobile) internet connection; importing from different sources before uploading to another.

C) For debugging purposes it might be good to have a Mongolab configured in the options and manually download/import from it once, but not to write anything back.

[altintx]

Absolutely agree. There are lots of assumptions all over that leading to a bad foundation. There's a secondary problem in that theoretically any Mongo database should function but that's assumptions it'll be Mongolab. Any suggestions how to fix? My gut is just fix as we go but I don't know if that's a valid answer.

One other kind of thing is @bewest is sort of interested in writing a better driver, I'm thinking the reports may wind up being NPM packages in their own right, and so the app-app may wind up being nothing but glue. Nothing wrong with that but does that lead to the problem being fixed?

[altintx]

Doing some fairly heavy refactoring in https://github.com/nightscout/chrome-uploader/tree/architecture

[altintx]

Mongo lab is playing more nice. It checks that APIKey is set before doing anything.

No progress on points B or C

[bewest]

Howdy, I needed a tool to dump and save all records to csv/zip file[s].
I decided to write an npm installable, browserifiable module just to deal with Dexcom protocol.
The input is a bidirectional stream object, output is a "fluent" api to request data from dexcom.

I'm a big fan of re-usable code, you can see how the pieces fit together a bit here:

• https://github.com/bewest/dexcom-uart - js fluent api for dexcom protocol
• https://github.com/bewest/serial-chromeify - trivial wrapper, exports a bidirectional stream implemented using chrome.serial.
• https://github.com/bewest/chrome-dexcom-memory - includes Makefile that shows how to browserify things to inject them into chrome app.

[altintx]

I'll try incorporating this in a new branch, hopefully later this week. Thanks!

[altintx]

New working branch bensdriver to contain this integration

[bewest]

Oh wow that's nifty!

A crazy idea might be using https://github.com/bewest/comlink2-uart to get cgm and pump history from Medtronic, api is pretty similar.

[altintx]

That's a good idea for numerous reasons. I'd starting working on getting bensdriver going but am having motivational issues because browserify. Everything else is require.js and a day of fighting with it left me not wanting to fight with it. Would probably go better if everything got rewritten as CJS and requirejs was simply abandoned.