Update Nightscout

Tip

You don’t need to follow these instructions if you use a hosted service.
Contact the vendor to learn more about possible updates.

See here which is the current released version before updating.

Step 1: Update your repository in GitHub

Select your current platform below:

Select your platform ->

Heroku, Railway, Northflank (GitHub)

- Click here to log in at GitHub: https://github.com/login.

Enter your username or email and your password. Click Sign in
Select your own cgm-remote-monitor project (not nightscout/cgm-remote-monitor)
Your repository will open. If you see This branch is xxx commits </br>behind nightscout:master you need to update.
Select Fetch upstream
Select Fetch and merge
After a moment, your repository should display This branch is up to date with nightscout:master

You have now updated your GitHub cgm-remote-monitor repository.

If you ran into trouble, you can redeploy the project.

Google Cloud, Docker (Azure, Northflank, Railway, Render)

You don’t need to update your GitHub repository.

Fly.io

You don’t need to update your GitHub repository if you deployed from https://github.com/nightscout/cgm-remote-monitor.

Step 2: Deploy

Select your platform ->

Google Cloud

Continue here

Heroku

Log in Heroku https://id.heroku.com/login
Select your app (hidden in yellow)
Click on Deploy
Verify Heroku is connected to GitHub, if not, clickConnect 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

Azure

Log into Azure : https://portal.azure.com/
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.

Fly.io

Follow these instructions to install flyctl on your computer. You also need to install git if you’re using a Windows computer.

Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.

Log in Fly.io:

flyctl auth login
Verify your Nightscout app name, use it to replace example-ns in the following lines.

flyctl app list
Verify your app current region (three letters code) and make sure it’s in the free tier.

flyctl app list
Navigate to the cgm-remote-monitor folder from which you deployed Nightscout on your computer. Verify it contains the fly.toml configuration file you used to deploy your site.
- If you don’t see this file, recover it:
  
  flyctl config save --app example-ns
If you migrated from Heroku using the wizard, or if you can’t find this folder on your computer, follow the next steps to recover your Fly.io configuration:
- Fork a copy of the Nightscout repository and change directory
  
  git clone https://github.com/nightscout/cgm-remote-monitor
  
  cd cgm-remote-monitor
- Download a default fly.toml configuration file
  
  flyctl config save --app example-ns
Update your Nightscout repository

git pull
Edit your fly.toml configuration and search this section:

[[services]]
  protocol = "tcp"
  internal_port = 8080
  processes = ["app"]

Change the internal port value to 1337, do not change anything else, do not remove the spaces before internal_port.

internal_port = 1337
Save the fly.toml file.
Deploy Nightscout:

flyctl launch
Wait until completion, you site should now be running the latest Nightscout version.

Updating existing machines in 'example-ns' with rolling strategy

-------
 ✔ Machine 1781944ae46438 [app] update succeeded
-------

Visit your newly deployed app at https://example-ns.fly.dev/

Downscale the app if you haven’t yet flyctl scale --app example-ns count 1

Railway Northflank Render (GitHub)

Once GitHub updated, your Nightscout should automatically deploy with the latest version.

Northflank (Docker)

- Log into Northflank: https://app.northflank.com/login

Select your Nightscout project
Select your Nightscout service
In Overview, Edit deployment
In the image path, check the image is nightscout/cgm-remote-monitor:latest (modify if necessary), then click Update & rollout restart
Your site will redeploy with the latest version.

Railway (Docker)

a) Open Railway and click login. Login with GitHub.

b) Select your Nightscout project.

c) Select your Docker service.

d) Click on Settings, disconnect the source image.

e) Select Connect image and type nightscout/cgm-remote-monitor:latest then press enter.

f) Go to the Deployment tab and from the three dots menu of the top deployment select Redeploy.

Your site will redeploy with the latest version.

Render (Docker)

Log into Render: https://dashboard.render.com/
Select your Nightscout project
Go to Settings and top right expand Manual Deploy, Select Deploy latest reference
Your site will redeploy with the updated Nightscout version