psonnera
commented
3 years ago Github: a single account is enough PS> Completely agree
Heroku: Adding control over multiple NS sites from the same Heroku login PS> many were already thinking about it and if the 1000 free dynos are per app that would make sense
Heroku: Use "Automatic deploy of master" (must use "pull request for updating for this to work, not the "delete fork" procedure) PS> Now that we won't have Azure users anymore (hopefully) it might be an idea. I don't believe deploying is the worst for users. Most stumble on Github upgrade...
MongoDB Atlas: Adding control over multiple NS databases from the same Atlas login
PS> This need to be digged as there were worries it would create a data flow not covered by the M0 plan, might be possible too
bjornoleh
sulkaharo
While migrating our NS sites to Atlas, I documented some steps to simplify the management of multiple NS sites. I didn't want to mention this earlier, as there have been more than enough to deal with regarding the migration process.
Perhaps we could now consider adding these steps to a separate page in http://nightscout.github.io/?
The hints are given in the order of usefulness. Number 1. - 3. are easy, and could be considered mandatory when managing multiple NS sites. Number 4 is the most effort, and probably not very useful to most.
(and a hint about Reverting to a previous deploy in Heroku, which is useful, but slightly off topic)
I have the required screenshots, but haven't edited out the usernames etc yet. @psonnera , what are you using to edit screenshots? It could be good to do it consistently throughout the documentation.
Managing multiple Nightscout sites: Hints to reduce the administrative burden -but it will take a few clicks now to set it up:
Github: You need only one Github account!
Then, the Github part of the update Nightscout will only have to be done once. (must use "pull request for updating for this to work, not the "delete fork" procedure)
(make it even clearer in http://nightscout.github.io/nightscout/new_user/#step-1-create-a-github-account that only one account is needed for multiple NS sites).
Heroku https://dashboard.heroku.com/apps
Log into the Heroku account that you wish to administer from another account (let’s call the other account the “master Heroku account”). Select the “App” you want to access from the master account. Click Access Click Add collaborator Enter the email address which is used with the master Heroku account Click Save changes
You will receive an email, but no actions are needed. Log out of the current account Log into your “master Heroku account” All “Apps” (NS-instances) will be available after login. Select either one to do what you need to do.
Automatic deploy of Nightscout Master: Click Deploy
Scroll down to Deployment method – Check that your Github account is connected Scroll down to Automatic deploys Click Enable Automatic Deploys
Do this for each Nightscout instance in Heroku. Now, all your NS sites will be updated to the latest Master as soon as you perform a “Pull request” in Github.
To update NS, please follow the instructions from within the NS site Click Check for Updates and follow the instructions. There is a mention about how to proceed with “Enable Automatic Deploys” turned on. You will only have to do this for one of the NS-sites, the others will be updated simultaneously if you followed the steps above.
(Reverting to a previous deploy:) Should you ever regret updating your NS, it is easy to revert to any previous version. Click Activity Find your previous deploy in the list Click “Roll back to here” This goes for any changes made to the Heroku Config variables as well.
MongoDB Atlas After having migrated your NS databases to MongoDB Atlas (or set up a new NS site with Atlas), these few steps will let you manage all your databases from one login.
https://account.mongodb.com/account/login Log into the Atlas account that you wish to administer from another account (let’s call the other account the “master Atlas account”). ORGANIZATION: Click Access Manager Click Invite Users
Enter the email address of the “master Atlas account” Select access permissions: Organization Owner Click Invite to Organization
The invited account will be listed in the Access Manager
Log out of the current Atlas user, and into the “master Atlas account”. You should never have to log into the other accounts again. Check the email which is used for the “master Atlas account”, look for “Invitation to MongoDB Cloud”, and click “Accept Invite”.
You will be prompted to log into your “master Atlas account” to accept the invite. Click your name in the upper left-hand corner You will find all your organizations here. Select either one.
Optional: To rename the organization, klick the gear icon next to the selected name Edit the Organization Name by clicking the pen icon