SAVE/STICKY - Steps for adding new Database / Customer / ORG

[plinck]

When creating a new customer, there are many things that need to be done.

• Create firestore instance with cloud storage, firestore, functions etc
• Setup service account credentials on google cloud platform to only allow proper URLs to access instance and DB
• Assign common user ([email protected]) to owner of firebase app
• Init firebaseapp
• Setup all google services like maps, directions, etc
  --- maps javascript api
  --- directions API
  --- places API
  --- Maps IOS SDK
  --- distanceMatrix API
• Setup / associate google billing account
• Create firestore DB with collection (e.g. SAA) and doc (e.g. prod)
• Setup firestore rules - copy from another DB
• Create hidden .env files and scripts for using new ORG
  --- client/functions/.env-strava-config-ORG.json,
  --- client/functions/.serviceAccountKey-ORG.json
  --- client/.env-ORG
  --- client/.firebaserc-ORG
  --- client/scripts/fbSwitchToORG.sh
• GIve ORG a code (ATC, SAA)
• Get branding images in correct folder i.e. images/${ORG}/
• Seed users collection with admin
• Seed ATCMembers collection (does not NEED documents but collection must exist)
• Save key icons etc under ORG
• Create Strava Account. Strava needs to have a new client id and secret for every app. I have one for atc ([email protected]) and one for dev ([email protected]). Unfortunately you must have one for each firestore instance since strava cant handle sending to multiple from one account. SAA Strava id is [email protected]
• Setup Strava API at strava.com/api and ensure the callback domain is correct
• Run the Strava API subscription callback either from test strava page on site or Postman

[plinck]

[plinck]

[plinck]