You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated: due to the limit of the Google Cloud for my region, so I will go with Cloud Functions first.
Regardless of the Cloud Run/Cloud Functions and what the network layer is, the logic is still the same.
Set up a new backend using Cloud Run and Cloud Functions.
When to use Cloud Run: for regular HTTP requests
When to use Cloud Functions: event-driven with Firebase Authentication, Firestore's event, etc.
Updated: due to the limit of the Google Cloud for my region, so I will go with Cloud Functions first.
Regardless of the Cloud Run/Cloud Functions and what the network layer is, the logic is still the same.
Set up a new backend using Cloud Run and Cloud Functions.
When to use Cloud Run: for regular HTTP requests
When to use Cloud Functions: event-driven with Firebase Authentication, Firestore's event, etc.
Using the current
api
workspace.Problems: Firebase functions still do not offer an official way to deal with the monorepo. Here is a good example to get started with: https://github.com/Hacksore/turborepo-firebase-example
References:
The text was updated successfully, but these errors were encountered: