CAVEAT April 6, 2023 - These instructions only include the setup for the Firestore side of our instances, and not the Supabase side. I would generally discourage trying to spin up your own instance unless you’re very familiar with Supabase and Firebase and NextJS.

Setup work

• [x] Create a new Firebase project in the UI, from [email protected]

  • [x] Provision Cloud Firestore
  • [x] Provision Firebase Auth
    • [x] Enable Google login
    • [x] Add subdomain to Google Auth
  • [x] Set payment plan to Blaze (pay as you go)
    • Seems to have some problem - we’re at the cap for number of projects under a single billing plan…
    • Okay, downgraded the old project supersync. But good to watch out for in the future
  • [x] Add yourself as a project owner
  • [x] Register the web app in Firebase
    • From the Firebase Project settings page, scroll down to Your apps and create a web app.

• [x] Create thereomone git branch

  • [x] Copy over security rules into firestore.rules
  • [ ] Send out a GitHub PR
  • [x] Copy over a config file in /common/envs
  • [x] Copy in Firebase credentials
  • [x] Import config file in /common/envs/constants.ts
  • [x] Create /functions/.env with NEXT_PUBLIC_FIREBASE_ENV=SUPERSYNC

• Deploy Firebase config

  • [x] $ firebase use mantic-markets to select the main project

  • [x] firebase firestore:indexes > firestore.indexes.json to copy indexes

  • [x] Copy secrets (Mailgun & Stripe keys) from main project

    • [x] firebase functions:secrets:access MAILGUN_KEY
    • [x] firebase functions:secrets:access STRIPE_APIKEY
    • [x] firebase functions:secrets:access STRIPE_WEBHOOKSECRET

  • [x] $ firebase use <PROJECT_ID> to select the new Firebase project

  • Set the secrets on the new project:

    • [x] firebase functions:secrets:set MAILGUN_KEY
      • [x] You’ll be prompted to enable Secret Manager API; enable it and try again
    • [x] firebase functions:secrets:set STRIPE_APIKEY
    • [x] firebase functions:secrets:set STRIPE_WEBHOOKSECRET

  • [ ] $ firebase deploy to deploy:

    • Cloud functions
    • Security rules
    • Indexes

    Note: this will take a while. Also, it may fail the first couple times due to slow permission propagation, just rerun firebase deploy

  • [ ] Copy over the functionEndpoints into the new config file

• Get it working locally

  • [x] Add a startup script to package.json
  • [ ] Run it locally
  • [ ] Sign in with your account
  • [ ] Whitelist your account as an admin in the Firestore security rules
  • [ ] $ firebase deploy --only firestore:rules to redeploy security rules

• Set up subdomain theoremone.manifold.markets :

  • [x] Create a subdomain in Vercel
  • [x] Point to theoremone git branch
  • [ ] Add an environment variable to the right database (NAME: NEXT_PUBLIC_FIREBASE_ENV; VALUE: THEOREMONE)

  August 21, 2022 Extra steps for auth

  • [x] Have to enable https://console.cloud.google.com/apis/library/iamcredentials.googleapis.com?project=atlas4 (change path for the newest project)
  • [x] Have to add “Service Account Token Creator”
    • From this Firebase doc link
    • This was what seemed to work

October 12, 2022

• Secret keys must be in upper snake case…
  • Nope, that was a typo
• new secret: API_SECRET

October 17, 2022

• Stuck on deploying functions:

  • firebase deploy --only functions gives:
  • Error: An unexpected error has occurred.
    • Same error on firebase functions:delete createmarket
  • Checking firebase-debug.log
    • TypeError: Cannot read properties of undefined (reading 'service')
    • Upgraded to latest firebase-tools, same problem
    • Seems to be this: https://github.com/firebase/firebase-tools/issues/4800
    • So deleting from here: https://console.cloud.google.com/functions/list?project=alvea-manifold

• Okay now: something else is broken

  

  • So cors broken?

    • https://console.cloud.google.com/run/detail/us-central1/createuser/yaml/view?project=alvea-manifold
    • Entire YAML
    • Doesn’t seem to have CORS passed in…

  • Or is it Uncaught (in promise) FirebaseError: Missing or insufficient permissions.

    • Copied over new rules, didn’t seem to help…
    • WHAT PERMISSIONS ARE MISSING

  • Or is it: something in the auth pipeline is broken

    

    • Hm, the equivalent ones on Prod aren’t authenticated!!
    • Okay done here:

    

• NOT_FOUND:

Overall: Fk cloud functions, let’s move to Vercel

• Pros