Multiple sites and support

Either by necessity or to support others, you might want to have access to multiple accounts without having to juggle between logins and passwords. Below are described some centralizing methods reducing the administrative burden.

Remote support and security

Giving username and passwords to someone in order to obtain help to fix Nightscout issues raises serious security issues. Malicious code can be added to your Nightscout project by ill-intentioned people. Always make sure the version deployed is a fork of the official project. After receiving help, good practice is to change your passwords and your API secret.

When possible prefer inviting collaborators (see below) and remove them once the issue is fixed.

Github

You need only one Github account since you can connect multiple web apps to the same GitHub account.

Using this strategy you only need to update one GitHub account when a new Nightscout version is released and you will be able to deploy it in all your web apps.

Hint

If you have several web apps connected to the same GitHub repository you must use the standard update method. Not redeploy (else you’ll break all the links to the repository).

Enable automatic deploys in Heroku

Automatic deploys will allow you to update automatically your Heroku apps when you update the GitHub repository: you will not need to login into Heroku and perform Manual Deploy, as soon as a new version will be merged into GitHub an automated deploy will trigger in all enabled Heroku apps.

To enable automatic deploy, log in Heroku and select your app, then Deploy. Verify GitHub and your cgm-remote-monitor app are connected.

Verify the master branch is selected and click Enable Automatic Deploys.

Your Heroku site will update automatically every time you update the GitHub repository.

Automatic deploys in Railway and Northflank

You don’t need to do anything as all your web apps will upgrade automatically when you upgrade GitHub.

Heroku

You can setup multiple Nightscout sites per Heroku account. You be charged the Eco/Basic plan fee for each app.

You can setup collaborators in Heroku to avoid having to switch accounts. First decide on which will be your main Heroku account. Then add the email address you used to register as collaborator to the other(s) one(s).

Log into your other Heroku account and select your app.

Select Access.

Click Add collaborator and enter the email address you used to create your main Heroku account.

You will now see it as a collaborator. Using the pen icon you can modify it or delete it.

Log in your main Heroku account. You will see the apps you are collaborating to in the same list than your primary app. You can now perform most tasks directly in that one Heroku account (deploys, change variables, …).

Atlas

You can invite another user in your organization in order to manage several organizations from the same Atlas account.

Log into your secondary Atlas account: that is the other account you want to administer from your first (main) Atlas account.

Top menu, click Access Manager and select Organization Access from the drop down menu

Click Invite Users

Enter the email address you used to create your main Atlas account.

Select Organization Owner then click Invite to Organization.

Warning

Make sure you enable Organization Owner for the invited user!

Log out of your secondary Atlas account and log in your main Atlas account.
Top left, from the drop down menu click the caret and select View all Organizations

In the left menu, click Invitations then click ACCEPT the invitation you performed from your secondary Atlas account.

Going back to all your organizations you can now see and administer both of them from this account. In the example below Nightscout is the main organization and My Org 2020-09-20 is a secondary organization.

Hint

You can rename your organizations from the top left cog (Settings) then clicking the pen icon.