#Integrate web frameworks with Hosting |...
1 messages · Page 1 of 1 (latest)
@vivid stirrup Thanks for your reply.
So if I understand correctly, this is just feeding firebase the build / output directory information manually so it can build and run the project?
where does express.js come in here? Not understanding its dependency
Not quite; after enabling experimental framework support, it should pick up that you're in a Nuxt project and when you run a deploy, it'll build your Nuxt site using the default build command and deploy it to hosting/functions as needed. You don't need to worry about Express, it's effectively an implementation detail but that's what it's grouped under in the docs
And to answer your other question, this is done via Functions v2, so it's not direct cloud run access. Because it's functions I'd probably recommend an SSG approach instead of SSR. If you wanna do SSR, you're probably better off with a different solution than this particular Firebase solution (like a self-rollled container for cloud run)
https://cloud.google.com/run/docs/quickstarts/build-and-deploy/deploy-nodejs-service may be a good place to start for that
@vivid stirrup gotcha, thanks so much.
+1 for SSR support, would be great to one click run a full universal app (i assume many nuxt/nextjs teams would enjoy this as well)
without needing to manage cloud run (more fun to stay in firebase land than to have to cross-over to GCP ಠ‿ಠ
So you can do that in Firebase, but it probably won't perfom how you'd want because functions only run in one region. If you're ok with that limitation, try it out
V2 is powered by cloud run, fwiw
You just don't get all of the config options that you'd do with straight cloud run, so your mileage may vary depending on your app needs
so when page routes are called it will trigger the v2 functions for SSR?