This document describes making a self hosted nightscout instance, with SSL encryption and certificate with Let's Encrypt.
Make a fresh instance of Ubuntu 16.04.1 LTS as a VM or on a physical machine Download from http://www.ubuntu.com/download/server/thank-you?version=16.04.1&architecture=amd64
VIrtual machine host options :
| • Setup IFTTT account | |
| • Connect to Maker channel and note secret key | |
| • Create if recipe | |
| o if Maker 'Receive a web request' | |
| • The Event Name doesn't matter, just make note of it. I suggest avoiding spaces as I've seen them cause problems in the past. | |
| o then Maker 'Make a web request' | |
| • URL: https://mynightscout.com/api/v1/treatments.json | |
| • Method: POST | |
| • Content type: application/json | |
| • Body: { "enteredBy": "Maker", "eventType": "Temporary Target", "reason": "Eating Soon", "targetTop": 80, "targetBottom": 80, "duration": 60} |
| # Install UbiLinux | |
| Follow the instructions on https://learn.sparkfun.com/tutorials/loading-debian-ubilinux-on-the-edison and then continue here. | |
| # Initial Setup | |
| Log in as edison/edison via serial console | |
| su - | |
| echo FIXME-thehostname-you-want > /etc/hostname |
| SHELL=/bin/bash | |
| PATH=/home/bewest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games | |
| */5 * * * * (cd ~/Documents/foo && openaps do-everything) 2>&1 | logger -t openaps-loop |
| launchctl unload -w -S Aqua /System/Library/LaunchAgents/gpg.agent.daemon.plist | |
| launchctl load -w -S Aqua /System/Library/LaunchAgents/gpg.agent.daemon.plist |
| FROM debian:latest | |
| RUN apt-get update | |
| RUN apt-get install -y git npm | |
| # make sure nodejs binary is available as node | |
| RUN cd /usr/bin && ln -s nodejs node | |
| COPY . /src |
| So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
| Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
| * Off the top of my head * | |
| 1. Fork their repo on Github | |
| 2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
| git remote add my-fork git@github...my-fork.git |
