part 1: delete and fork your cgm-remote-monitor repository€¦ · 11. you will now see that your...

Upgrading to Latest cgm-remote-monitor “Brownie” Release.

Steps Overview:

1. Delete and refork your repository

2. Disconnect from GitHub in Azure

3. Set up deployment from source control in Azure

4. Verify connection strings in Azure

5. If you wish to incorporate Care Portal, refer to link on http://www.nightscout.info/wiki/labs

DETAILED STEPS

PART 1: Delete and Fork your cgm-remote-monitor Repository

1. Log into your account on https://github.com

2. Click on your account name on top right corner

3. Click on your Repositories Tab

4. Locate and click on your fork of ‘cgm-remote-monitor’

5. On the right side of page, click on ‘Settings’:

6. Scroll to bottom of Settings page, and click on ‘Delete this repository’

7. Confirm the deletion of your repository by typing the name of it. See below. Type in only what is after your

‘username/’

8. Go to https://github.com/nightscout and then locate and click on the original ‘cgm-remote-monitor’.

9. On the top right, click on ‘FORK’ to make a copy of the nightscout/cgm-remote-monitor in your repository

10. The fork will take a few moments to complete.

11. You will now see that your [username]/cgm-remote-monitor is in your repository.

PART 2: Azure – Disconnect and re-deploy Web site code

1. Log into Azure at https://manage.windowsazure.com

2. Click on ‘Web Sites’ on the left navigation bar

3. Click on your web site

4. Click on Dashboard if you aren’t already on that page.

5. Locate the ‘Quick Glance’ menu on the right side of the dashboard, and click on ‘Disconnect from GitHub’. If

you see ‘Set up deployment from source control’ then proceed to Step #8.

6. Click ‘Yes’ to agree to the disconnect.

7. It will show ‘Operation is currently running’ and wait for that to complete.

8. Back under the ‘Quick Glance’ menu, now click on ‘Set up deployment from source control’

9. On the ‘Where is your source code?’ prompt, select GitHub and click on the arrow on bottom right.

10. Since you were just logged into GitHub, the connection/authorization connection should occur without any

GitHub credential prompt, but if you are prompted, provide the necessary credentials to connect.

In the ‘Choose a repository to deploy’, select the ‘cgm-remote-monitor’ from the REPOSITORY NAME drop

down.

11. After selecting, the BRANCH TO DEPLOY should be ‘master’ and then click on the arrow to proceed.

12. Your GitHub repository will now be linked, and the deployment will begin.

13. When it’s done deploying, it will turn to a green ‘ACTIVE DEPLOYMENT’

14. Next we want to make sure you Connection Strings are still present in the configuration. From the top

navigation menu, click on ‘CONFIGURE’

15. Scroll down the Configure page, and look for the ‘Connection Strings’ section. Click on ‘Show Connection

Strings’

16. Verify that your connection strings still exist, and that they are correct. They shouldn’t have changed, but if they

are not present, you will need to reenter them.

17. Proceed to your website and test that it appears.

18. On the top right of the screen, click on the Settings icon (gear) and verify in the about section that you see

version 0.4.x (‘x’ will be the latest revision, ie. 0.4.2) You can customize your settings however you desire.

Enjoy!