Deploy another version
If you need to return to the previous Nightscout version, or in rare occasions, like testing a specific fix or a feature that is not released yet (i.e. not in the
master branch), you might need to deploy another branch like
dev in the example below.
Do not deploy
dev or a branch other than
master unless directed to do so (except if you know why you are doing so).
Step 1: Update your repository in GitHub
Skip this step if you’re using Azure.
Click here to log in at GitHub: https://github.com/login.
Enter your username or email and your password. Click
Select your own
Your repository will open.
In the branch drop down menu (normally showing
Fetch upstreamto update it, then
Fetch and merge
After a moment, your repository should display
This branch is up to date with nightscout:dev
If you ran into trouble, try to Redeploy (and this is mandatory if you don’t see
Step 2: Deploy
Select your platform below:
Log in Heroku https://id.heroku.com/login
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.
Open Railway and click
login. Login with GitHub.
If you only see
masterin the list you need to redeploy taking care to select all branches and not only
devselected Railway will deploy automatically.
Log into Northflank: https://app.northflank.com/login
Your site will redeploy with the selected branch
Log into Azure : https://portal.azure.com/
In the left menu select Deployment Center, in Full Image Name and Tag change the version to:
nightscout/cgm-remote-monitor:latest_dev(example for dev) Or whichever version (change
filter tagfind the version) in the list.
nightscout/cgm-remote-monitor:14.2.6(example for 14.2.6)
a) Open a Web Terminal, and type:
git clone https://github.com/nightscout/cgm-remote-monitor
b) Update your local fork
git config pull.rebase true
git pull origin dev
c) Deploy the changes (replace yourappname by the actual name of your fly.io Nightscout app).
flyctl deploy -a yourappname
Deploy will take some time and should complete with the message
Visit your newly deployed app at https://yourappname.fly.dev
d) Don’t forget to downscale the app!
flyctl scale count 1
Check your profile time zone is correct. You’re done!
How to return to the
If things don’t go as expected you can simply redeploy your
master branch performing the same steps and using
master instead of
When the dev branch gets merged into release, just follow the classic update method.