* skeleton code
* publishing
* Activating remote override
* Fix event types refresh, and fix custom duration
* Don't create treatment record; loop will
* Additional override details for treatment tooltip
* Pass client from careportal
* attempt at moving endpoint to api/v2
* Add bodyParser to v2/notifications
* Remove notifications api from v1
* Remove unused var
* Better error handling and reporting
* Add documentation for new loop plugin vars
* Handle indefinite duration overrides
* Move label of indeterminate duration override to now line when start is offscreen
* test
* Use separate representation for indefinite duration treatments
* fix display for finite duration treatments
* Fix re-use of elements when treatment ordering changes
* Handle more rect transition() updates
* Add check for LOOP_DEVELOPER_TEAM_ID
* Support configuration of aps-environment via environment variable.
* Fix expiration date math; was essentially preventing retries
`/api-docs/` seems to be the correct path for the swagger UI.
- change `/api-docs.html` reference to `/api-docs/`
- also change `/api-docs` to `/api-docs/` as it is more exact
* add support for different color prediction lines
* changed quotation marks to better fit guidelines
* corrected and standardized variable names
* added support for colored ACOB prediction and changed default prediction line colors
* added default colour for 'Values' prediction
* HIDE_CLOCK_CLOSEBUTTON setting to hide the button altogether (set to TRUE or ON to hide buttons altogether)
* Fix CSS for toolbar positioning in the main view
* Fix documentation on the clock URLs and add mention of the setting
I've changed the explanation for the `INSECURE_USE_HTTP` environment variable.
The old first line describing this setting in just one sentence was wrong and the next line basically suggested turning this security feature off in situations where it's not needed.
In the nightscout code you check if either the connection is secure by itself or if the X-Forwarded-Proto header is set (which it should be by default in all major reverse proxy applications).
It should be unnecessary to change that setting even in a reverse proxy environment.
* Change incompatible module and fix a memory leak in the process
* Fix fonts, allow websocket
* Oops fix a brainfart with using the hostname
* Don't inlude null hostname
* Update the shrinkwrap
* Instantiate new cache if new instance of profile code is created. Calculate IOB with three digit precision to keep tests happy (and this is roughly the precision we're operating at anyway).
* - implement @jweismann suggestions https://github.com/nightscout/cgm-remote-monitor/pull/4449#issuecomment-469868508
- add frameAncestors, baseUri and formAction protection
* update README and run doctoc
* fix reportOnly
* add objectSrc
* Use modern CSS loading
* Change CSS to use the "official" async loading across the board (which hopefully plays nicer with CSP)
* first release candiate for 0.11.2 with Minimed EU Server and Guardian Connect integration
- integrates https://github.com/mddub/minimed-connect-to-nightscout/pull/11 into Nightscout
* bump node 10 LTS version
* increase logging, fix /swagger.yaml
* fix typo
* set version to rc2, update mongodb to 3.2.2
* add SECURE_CSP_REPORT_ONLY (default false).
* npm update and revert to requiring Node versions without security issues.
* small doc fix to comments on Node versions
* Update README.md
* * Fixes authentication dialog UI on Mobile Safari
* Improves app cache busting, so after deploy the app is guaranteed to notice it has to reload content
* Small fix to Finnish language related to auth UI
Pete SchwambandSulka Haro
p5nbTgip0randSulka Haro
John WestonandSulka Haro
Alexandre ViauandSulka Haro
inventor96
Erin879andPieterGit
Benedikt BauerandGitHub
PieterGit
Jason Calabrese
TanjaandSulka Haro
Dave ColeandPieterGit
renegadeandyandGitHub
Jeremy Cunningham
jweismann