Skip to content

Updating Your Site to the Latest Version


See here which is the current released version before updating.


If you prefer to follow a video, have a look here.

Step 1: Update your repository in GitHub

  • You an skip this step if you use Azure

  • Update your current cgm-remote-monitor fork.

  • If you have the latest version in GitHub
    If using Heroku: proceed to Step 2: Deploy
    If using Railway: your site should be up to date and you're done. If it's not, reconnect GitHub.

  • If something went wrong continue below.

Use the update script

  • Note your GitHub username (hidden below in yellow).
  • Scroll down until you see the Nightscout logo.

  • Click Update your site

  • Enter your GitHub username and click Check for updates

  • If an update is available click Continue updating at GitHub
  • Make sure you see GitHub user located! else check your username.
  • If you know an update is available but you see Repo is Up to date, try the alternative method: redeploy.

  • A pop-up will open, just click OK (you can read the contents if you want, but this is explained below, so just click OK)

  • Now comes the tricky part.

Don't try to update cgm-remote-monitor with your own project!

Make sure the left hand side repository is yours (name hidden in yellow) and the right hand side is nightscout/cgm-remote-monitor.

Click Create pull request.

  • A pull request opens. Last chance to check the left hand side repository is yours (name hidden in yellow) and right hand side is nightscout/cgm-remote-monitor, write a comment in the field (example Update or whatever you like)

  • Scroll down and click Create pull request

  • Scroll all the way down (it might be far away) and click Merge pull request

  • Click Confirm merge

  • A new line will appear in the pull requests log showing merge succeeded

  • Your GitHub repository will show you're one commit ahead of the released version


  • You have successfully updated your GitHub repository, now let's deploy it in Heroku Step 2 below.


  • You have successfully updated your GitHub repository.
    You also have completed updating Nightscout as Railway or Northflank will automatically deploy this new version for you.
    If it's not updated with Railway, reconnect GitHub.
    If something went wrong scroll down and try to redeploy.

Step 2: Deploy in Heroku

Skip if you don't use Heroku.


Salesforce recommends two-factor-authentication for more Heroku security, starting Feb 2022.
For an overview of possible methods see here.

  • Select your app (hidden in yellow)

  • Click on Deploy

  • Verify Heroku is connected to GitHub, if not, click Connect to GitHub

  • If Heroku is not connected to GitHub, scroll down and click Connect to GitHub, if a popup window opens and requires authorization, click Authorize Heroku

  • Verify your app cgm-remote-monitor is connected to GitHub

  • If it isn't, In Connect to GitHub, type cgm-remote-monitor and click Search then click Connect

  • If you have trouble connecting your app, click Disconnect and reconnect it as shown above

  • Scroll down to the bottom of the page, select the master branch and click Deploy Branch

  • Build will start and information will scroll in the log window. Do not leave the page, do not interfere and wait for completion. It might take more than 10 minutes. Interrupting the process will lead to a broken site and you'll need to restart deployment.

  • Wait until the deploy process completes and click View (if nothing happens click Manage App then upper right Open App)

  • Your site will open and should be at the latest version.
  • Check your profile time zone is correct. You're done!

If you ran into trouble, try the Redeploy method

Step 2: Deploy in Azure

Skip if you don't use Azure.

  • Log into Azure :
  • Select your App service, your Nightscout site name (you should see it in recent resources)

  • If you didn't find it, it will show in App Services

  • In the left menu select Deployment Center and change Continuous Deployment to On.

  • Click Save (or Discard if you don't want to update).
    Your site will redeploy with the latest cgm-remote-monitor version.
    Expect a few minutes before it comes back online.

  • You can leave Continuous Deployment On if you want upgrades to happen automatically, or turn it back to Off (and save) to control upgrades manually yourself.

Step 2: Deploy in

Site maintainability

Make sure you have a local fork of cgm-remote-monitor and the current fly.toml before continuing.
If you don't, first perform these operations.

a) Open a PowerShell (Windows) or a terminal (OSX/Linux), and type:

cd cgm-remote-monitor

b) Update your local fork

git pull origin master

c) Deploy the changes.

Type the command:

flyctl deploy

Deploy will take some time and should complete with the message 1 desired, 1 placed, 1 healthy, 0 unhealthy [health checks: 1 total, 1 passing].

Back to top