firebase-tools VS action-hosting-deploy

And it seems to deploy on first try, but then I got a loop error. Turns out after posting a bug, and getting sent to GitHub, this is a known issue when deploying to Cloud Functions. The fix is to edit your server.ts file, and don't use the process.env['PORT'] variable, as it apparently is already in use.

See issue.

No, just JS. Have you tried this?

In this example, I am using NX monorepo. I have my Angular Universal as one application and cloud functions as another application. If you don’t use NX or even some time has passed since publishing this blog post, you may want to visit Integrate web frameworks with Hosting from Firebase, however, there is an existing issue on Unable to detect the web framework in use when using angular app within nx monorepo.

Support for Sveltekit SSR has been added https://github.com/firebase/firebase-tools/issues/5158

// https://github.com/firebase/firebase-tools/issues/1532 if (admin.apps.length === 0) { admin.initializeApp() } export const deleteAllUserJobs = functions.https.onCall(async (context: functions.https.CallableRequest) => { const uid = context.auth?.uid if (uid === undefined) { throw new functions.https.HttpsError("unauthenticated", "You need to be authenticated to perform this action") } const firestore = admin.firestore() const collectionRef = firestore.collection(`/users/${uid}/jobs`) const collection = await collectionRef.get() logger.debug(`Deleting ${collection.docs.length} docs at "/users/${uid}/jobs"`) // transaction version await firestore.runTransaction(async (transaction) => { for (const doc of collection.docs) { transaction.delete(firestore.doc(`/users/${uid}/jobs/${doc.id}`)) } }) logger.debug(`Deleted ${collection.docs.length} docs at "/users/${uid}/jobs"`) return {"success": true} })

This should be supported via our built-in NextJS support https://firebase.google.com/docs/hosting/frameworks/nextjs if you have troubles with this functionality, please file a bug over on github https://github.com/firebase/firebase-tools

Now that app directory is stable, we support it. Keep an eye on the firebase-tools changelog, we've actively working on things. https://github.com/firebase/firebase-tools/releases

The Firebase CLI, check out the release notes

Could they not have their own FB to develop against? Does every dev need to use just yours? If that is the case, then you'd need to use https://support.google.com/firebase/answer/7000272?hl=en also, it looks to be possible to include Firebase in your GitHub for them to pull from https://firebase.google.com/docs/hosting/github-integration

Github Actions is the way to go for this: https://firebase.google.com/docs/hosting/github-integration

Whenever a Pull Request is created we need to be able to quickly checkout the changes. Reading code diff is great, but sometimes you just need to tinker with the new version, test it on mobile, different browsers and OS. Cloud services are perfect for this case, they allow you to deploy the code temporarily and access it with a link from any device. We chose Firebase to host it for us and a Github action posts a link to the deployment as a comment in the Pull Request. It works like a charm and speeds up code reviews a lot. Read this article to set it up on your repository!

Lambdas and firebase on the GCP stack for CRUD apps.

One nice thing about firebase -> each PR deploys to its own preview channel[1].

Downside: Very JS heavy. I write lambdas in python though.

[1] https://firebase.google.com/docs/hosting/github-integration

Google Firebase has a pretty straightforward guide to setting up auto-deploy from Github, which you can take a look at here: https://firebase.google.com/docs/hosting/github-integration

What is the easiest way for setting up CI/CD from GH for Firebase functions? Maybe something like this for hosting, but only for functions?

Note: you can find more info about the used steps actions here actions/checkout@v2 and here FirebaseExtended/action-hosting-deploy@v0