You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://waffle.io/nightscout/cgm-remote-monitor)
8
+
[](https://waffle.io/nightscout/cgm-remote-monitor)
7
9
8
10
[](https://heroku.com/deploy)
9
11
10
-
This acts as a web-based CGM (Continuous Glucose Montinor) to allow
11
-
multiple caregivers to remotely view a patients glucose data in
12
-
realtime. The server reads a MongoDB which is intended to be data
12
+
This acts as a web-based CGM (Continuous Glucose Monitor) to allow
13
+
multiple caregivers to remotely view a patient's glucose data in
14
+
real time. The server reads a MongoDB which is intended to be data
13
15
from a physical CGM, where it sends new SGV (sensor glucose values) as
14
16
the data becomes available. The data is then displayed graphically
15
-
and blood glucose values are predicted 0.5 hours ahead using a
17
+
and blood glucose values are predicted 0.5 hours ahead using an
16
18
autoregressive second order model. Alarms are generated for high and
17
19
low values, which can be cleared by any watcher of the data.
18
20
@@ -32,23 +34,6 @@ Clone this repo then install dependencies into the root of the project:
32
34
$ npm install
33
35
```
34
36
35
-
### Vagrant install
36
-
37
-
Optionally, use [Vagrant](https://www.vagrantup.com/) with the
38
-
included `Vagrantfile` and `setup.sh` to install OS and node packages to
39
-
a virtual machine.
40
-
41
-
```bash
42
-
host$ vagrant up
43
-
host$ vagrant ssh
44
-
vm$ setup.sh
45
-
```
46
-
47
-
The setup script will install OS packages then run `npm install`.
48
-
49
-
The Vagrant VM serves to your host machine only on 192.168.33.10, you can access
50
-
the web interface on [http://192.168.33.10:1337](http://192.168.33.10:1337)
51
-
52
37
Usage
53
38
---------------
54
39
@@ -61,50 +46,104 @@ ready, just host your web app on your service of choice.
The easiest way to update your version of cgm-remote-monitor to our latest
55
+
recommended version is to use the [update my fork tool][update-fork]. It even
56
+
gives out stars if you are up to date.
57
+
58
+
### What is my mongo string?
59
+
60
+
Try the [what is my mongo string tool][mongostring] to get a good idea of your
61
+
mongo string. You can copy and paste the text in the gray box into your
62
+
`MONGO_CONNECTION` environment variable.
63
+
64
+
### Configure my uploader to match
65
+
66
+
Use the [autoconfigure tool][autoconfigure] to sync an uploader to your config.
67
+
64
68
65
69
### Environment
66
-
You can use the default null `database_configuration.json`
67
-
config if you set the following environment variables instead.
68
-
(Hosting providers often make this easy, and this allows you to avoid
69
-
editing anything.)
70
70
71
-
*`CUSTOMCONNSTR_mongo` - the mongo connection string, corresponds to
72
-
`DB.url`.
73
-
*`CUSTOMCONNSTR_mongo_collection` - the mongo collection to use,
74
-
corresponds to `DB.collection`.
71
+
`VARIABLE` (default) - description
72
+
73
+
#### Required
75
74
75
+
*`MONGO_CONNECTION` - Your mongo uri, for example: `mongodb://sally:sallypass@ds099999.mongolab.com:99999/nightscout`
76
+
77
+
#### Features/Labs
78
+
79
+
*`ENABLE` - Used to enable optional features, currently supports: `careportal`
80
+
*`API_SECRET` - A secret passphrase that must be at least 12 characters long, required to enable `POST` and `PUT`; also required for the Care Portal
81
+
*`BG_HIGH` (`260`) - must be set using mg/dl units; the high BG outside the target range that is considered urgent
82
+
*`BG_TARGET_TOP` (`180`) - must be set using mg/dl units; the top of the target range, also used to draw the line on the chart
83
+
*`BG_TARGET_BOTTOM` (`80`) - must be set using mg/dl units; the bottom of the target range, also used to draw the line on the chart
84
+
*`BG_LOW` (`55`) - must be set using mg/dl units; the low BG outside the target range that is considered urgent
85
+
*`ALARM_TYPES` (`simple` if any `BG_`* ENV's are set, otherwise `predict`) - currently 2 alarm types are supported, and can be used independently or combined. The `simple` alarm type only compares the current BG to `BG_` thresholds above, the `predict` alarm type uses highly tuned formula that forecasts where the BG is going based on it's trend. `predict`**DOES NOT** currently use any of the `BG_`* ENV's
86
+
*`PUSHOVER_API_TOKEN` - Used to enable pushover notifications for Care Portal treatments, this token is specific to the application you create from in [Pushover](https://pushover.net/)
87
+
*`PUSHOVER_USER_KEY` - Your Pushover user key, can be found in the top left of the [Pushover](https://pushover.net/) site
88
+
89
+
90
+
#### Core
91
+
92
+
*`DISPLAY_UNITS` (`mg/dl`) - Choices: `mg/dl` and `mmol`. Setting to `mmol` puts the entire server into `mmol` mode by default, no further settings needed.
93
+
*`MONGO_COLLECTION` (`entries`) - The collection used to store SGV, MBG, and CAL records from your CGM device
94
+
*`MONGO_TREATMENTS_COLLECTION` (`treatments`) -The collection used to store treatments entered in the Care Portal, see the `ENABLE` env var above
95
+
*`MONGO_DEVICESTATUS_COLLECTION`(`devicestatus`) - The collection used to store device status information such as uploader battery
96
+
*`PORT` (`1337`) - The port that the node.js application will listen on.
97
+
*`SSL_KEY` - Path to your ssl key file, so that ssl(https) can be enabled directly in node.js
98
+
*`SSL_CERT` - Path to your ssl cert file, so that ssl(https) can be enabled directly in node.js
99
+
*`SSL_CA` - Path to your ssl ca file, so that ssl(https) can be enabled directly in node.js
0 commit comments