35 results found
-
5 votes
-
Trusted headers for client IP address via Firebase Hosting
Context: from a backend running on Cloud Run/Cloud Functions, how to determine client IP address, when you need to TRUST it for IP-address based access restrictions.
You can normally find the real client IP as the first entry in the X-Forwarded-For header, but you cannot trust it.
If you are using Cloud Run (or Cloud Functions gen 2), then as far as I can tell the Cloud Run orchestrator always sits as a proxy in front of your container. This means you can trust the last entry in X-Forwarded-For as this is the client IP seen by Cloud Run itself.…
3 votes -
4 votes
-
X-User-Country header when proxying to Google Cloud Run
App Engine and Cloud Functions send X-AppEngine-Country to app servers, which is useful for serving regional content to users.
Google Cloud Run doesn't receive the same headers. GCR can receive this header through load balancer custom headers (https://cloud.google.com/load-balancing/docs/https/custom-headers), but it'd be great if it were supported through Firebase Hosting directly without any extra configurations.
3 votes -
3 votes
-
Support deployment of Nuxt 3 projects to Hosting
Currently, support for Web Frameworks (Beta) only supports Next.js and Angular: https://firebase.google.com/docs/hosting/frameworks/frameworks-overview. Nuxt is labeled as 'Soon' at https://github.com/FirebaseExtended/firebase-framework-tools
I just wanted to cast my vote for Nuxt 3 support and try out the new portal :) Thanks!
3 votes -
Remix support
Have out of the box support for Remix framework implementing SSR which also work with the Emulators.
3 votes -
The Firebase target apply command has also to update the firebase.json with the target name!
The Firebase target apply command has also to update the firebase.json with the target name!
3 votes -
3 votes
-
View custom domain setup DNS configurations
After a Custom Domain is set up on a site, there's no way to view what the correct DNS records should be.
2 votes -
2 votes
-
Enable deployments that don't delete previous artifacts
Have an option to deploy and keep previous deployment artifacts instead of deleting them.
Even better would be an option for this with a TTL on previous deployment artifacts (that haven't been updated or re-deployed in subsequent deployments).
2 votes -
2 votes
-
CI & CD for deployments
Git based CI & CD auto deployments would really be a game changer, it can be integrated to things like cloud run and enable this. Half the time I use tools like vercel and netlify because of lack of auto deployments in firebase
1 vote -
Add ability to set release version.
Right now we can not control version. After deploy version at api looks like this:
"sites/<site_name>/versions/2e65a07a8886cdb4"I want to be able to provide my own string (git hashtag, semver, etc). It requires to match source code and deployed version. The version should be shown at UI and we should be able to rollback based on this version. During deploy with the same version CLI should throw error.
1 vote
- Don't see your idea?