bro thanks alot I was deploying firebase app on firebase but that was not happening then i did on vercel it was showing issue of auth your video just helped me thank you
This is great but I don’t think you need environment variables all the config keys. Someone asked the same thing and Google dev said: “ So the apiKey in your configuration snippet just identifies your Firebase project on the Google servers, but does on its own not allow access to it yet. It is not a security risk for someone to know it. In fact, it is necessary for them to know it, in order for them to interact with your Firebase project. This same configuration data is also included in every iOS and Android app that uses Firebase as its backend.”
It's either .env keys(that Firebase requires a a chunk if in that order) or account_key.json script as per my knowledge as granting rights is needed(more troublesome to setup). If you would deploy directly in Firebase Hosting then no you don't need. If you use GCP(that owns Firebase) as well don't need to provide but troublesome setting it up in PaaS for deployment unlike with .env vars.
@@MozescodesThat’s right but typically .env is used to hide things that you want to have security for. In this case you’re hiding something which does not require hiding. None of the config items are a security risk so you don’t have to put them as Next env variables.
@@markw496 Most are not some are security risk understood it later when deploying through GCP and using Terraform(this is an old video). Or you want to expose everything?
@@Mozescodes No, if you look one of top devs that maintains firebase said this. Frank Puff. He stated that the config and even the API key doesn't pose a security risk. It's an actual stackoverflow question. I'm just letting you know that it's not required in this case, but security should still be taken for things which are meant to be hidden. I'm just saying putting them in NEXT variables is more work which is not required.
@@markw496 Ok thanks no one was asking you. I have on server side account_key.json file and on client side so your saying FIREBASE_API_KEY should be public? If you know better make a corresponding improvement video. You may not know but in corresponding Terraform video a lot more variables are public we learn as we go.
thanks a lot!
bro thanks alot I was deploying firebase app on firebase but that was not happening then i did on vercel it was showing issue of auth your video just helped me thank you
Thanks, i did depoly in vercel but my env name was incorrectly imported in vercel and after watching your video it worked.
Bro u saved my life!
Glad to be help out a fellow dev!
This is great but I don’t think you need environment variables all the config keys. Someone asked the same thing and Google dev said: “ So the apiKey in your configuration snippet just identifies your Firebase project on the Google servers, but does on its own not allow access to it yet. It is not a security risk for someone to know it. In fact, it is necessary for them to know it, in order for them to interact with your Firebase project. This same configuration data is also included in every iOS and Android app that uses Firebase as its backend.”
It's either .env keys(that Firebase requires a a chunk if in that order) or account_key.json script as per my knowledge as granting rights is needed(more troublesome to setup).
If you would deploy directly in Firebase Hosting then no you don't need. If you use GCP(that owns Firebase) as well don't need to provide but troublesome setting it up in PaaS for deployment unlike with .env vars.
@@MozescodesThat’s right but typically .env is used to hide things that you want to have security for. In this case you’re hiding something which does not require hiding. None of the config items are a security risk so you don’t have to put them as Next env variables.
@@markw496 Most are not some are security risk understood it later when deploying through GCP and using Terraform(this is an old video). Or you want to expose everything?
@@Mozescodes No, if you look one of top devs that maintains firebase said this. Frank Puff. He stated that the config and even the API key doesn't pose a security risk. It's an actual stackoverflow question. I'm just letting you know that it's not required in this case, but security should still be taken for things which are meant to be hidden. I'm just saying putting them in NEXT variables is more work which is not required.
@@markw496 Ok thanks no one was asking you. I have on server side account_key.json file and on client side so your saying FIREBASE_API_KEY should be public?
If you know better make a corresponding improvement video.
You may not know but in corresponding Terraform video a lot more variables are public we learn as we go.