Downgrading your Nightscout version⌁
There is usually no good reason to downgrade Nightscout unless being instructed to do so.
Roll back can be really useful in case of mistakes and when awaiting bug fixes in minor releases.
You can only roll back to a version that was previously deployed to your Heroku app.
Roll back Heroku⌁
Heroku keeps history of variables modifications and previous deploys so that you can return to a previous state easily in the cases of a configuration mistake or a bad deploy (like a bugged version). When rolling back to a previous deploy keep in mind all variables modified in the mean time will return to the value they had at that time.
Since the database is external to Heroku, it will not be impacted by a roll back.
- Log into Heroku.
- Select your Nightscout app and go to
- You will see a list of events called
Activity Feedand some indicated as possible roll-back points. Identify the last good situation and select
Roll back to here
- Identify and eventually write down the values of the variables that were changed in the meantime (arrows in the picture below) before selecting
Upon completion your Heroku will be returned to the state it was at the selected rollback point.
You can use it like this or upgrade to the latest released version later on.
- If you change your mind later you can rollback prior to your rollback and return to the starting point.
Deploy an old release⌁
Experienced users only - not recommended
Deploying an archived release of Nightscout if it's not present in your Heroku activity list is more complex and involves installing Git on your computer.
Clone it locally (navigate to the folder where you'll want it saved locally before cloning). Replace YOUR-USERNAME by your GitHub user name.
git clone https://github.com/YOUR-USERNAME/cgm-remote-monitor
First identify the commit matching the release you want to use, look into the released versions.
Then create a branch out of this commit (replace BRANCH by the branch name you want and indicate the COMMIT matching the one you need, in the case above b627d31):
git checkout -b BRANCH COMMIT
Push this new branch to your repository
git push --set-upstream origin BRANCH
You can now deploy it in Heroku selecting it in the drop down menu.