-
Using Cloud Functions v2 where possible (other than Firestore triggers)
-
Reviews:
first
-
Rework around how CI is structured and implemented.
Now using more Docker Compose, also within CI (e.g. Cypress).
- Realtime Database removed; observability will use callables for transport
-
CI: Optimized so that tests are only run in the test scripts. Deploy scripts check from Cloud Storage whether such tests have passed.
- Speeds up and simplifies CI/CD.
- Manual deployment done so that Cloud Functions always deployed to the "default GCP resource location" (aka
locationId
). This is what Cloud Firestore also uses. - Wrote a section on regions.
- Revising the READMEs.
- Rearranged the way
packages/app
uses the backend- now all backend details in
packages/backend
; also for the instance used for front-end development
- now all backend details in
- Backend CI runs work, again
- Updating to
firebase-jest-testing
0.0.5-alpha.1 - Using Docker Compose healthchecks and
depends_on:
withcondition:
- means we don't need
dc-tools/n-user
any more!! 🪒
- means we don't need
- Abandoning Node.js 14 (no longer testing with it in CI)
- Bumped Firebase Emulators to 10.0.1; the image now uses npm8
- Backend CI testing using Docker Compose
- with
npm
running the tests
- with
- Using Docker Compose for handling concurrency in testing.
- Going back to
firebase@9.0.0-beta.2
, to fix #56
-
LOTS of changes!
- backend testing now stable (all tests pass); uses
firebase-jest-testing
- backend testing now stable (all tests pass); uses
-
Deployment works.