Комментарии:
I read about that, firebase cloud functions takes yours .env in execution time and not when compiling time. So be careful if u want to put there yours firebase-admin sdk credentials, it wont work :( but for others vars it is fire!
Ответитьdoesn't work now
ОтветитьCan't you just git ignore your .env files instead of using secret manager?
ОтветитьThe only odd thing is that you need to have all .env files on the root of your project, I like to keep them on a separate folder to be more organized but looks like thats not possible right now :/
ОтветитьThis was a lifesaver!!!
ОтветитьCan anyone tell me where are those icons from? theme?
ОтветитьThanks for sharing!
ОтветитьMore videos about firebase please.
Ответитьlmaoo firebase is trolling with their pattern. They only introduced .env files now ? RIP
Ответитьgood one Jeff.
ОтветитьYou might want to think about franchising your channel or hiring someone to do the same thing on a different topic but with the same format. Things like ML, Cybersecurity, HPC, and so on. The format is obviously the secret sauce, but the topics you cover are what you feel most comfortable with, i.e. frontend development. Time to scale! :)
ОтветитьI have been using it since it's in beta
ОтветитьAnybody know what file icons he has? I want.
ОтветитьYou should talk about CQRS and Event Sourcing :)
ОтветитьWas this a thing in nextjs or am trippin'?
ОтветитьSuper important
ОтветитьWhat a coincidence, currently working with cloud functions
Ответитьhello
Ответить1'000'000$ hint: Use Doppler, it will change your life 😉
ОтветитьDoes this channel have any specific purpose, or just more videos from you?
ОтветитьAt this point I put fireship on my CV
ОтветитьRecently Integrated secret manager in my company's tech 😇
ОтветитьLaravel already had this a billion years ago.
Ответитьyesterday you have 20k subs
today is 39.5k
Love your new channel 🥰
AWS Lambdas have something very similar in a yaml format for a while now.
ОтветитьLittle me, who thought fireship owns firebase
Ответитьi might like this channel more than your main one
ОтветитьDo never commit a .env file
ОтветитьAwesome video
Ответитьthis channel will hit 100k soon
Ответитьyummy my hero
ОтветитьYuck, Firebase
ОтветитьReact and next js you gotta prefix every var
ОтветитьYou sound like fireship
ОтветитьRails has it better with an encrypted production file. Then all the server needs is the key. This way is weird with .env for dev and Secret Manager for prod.
ОтветитьThe main issue here is that secret manager is expensive. The previous way was free and really good. Now Google found a way to monetize even using env files.
ОтветитьLove your "Hi mom"s you always include your videos :)
ОтветитьYou should make one about AWS too
ОтветитьBeen a while since you didn't do a firebase video. Glad to see you back to the sources ! (and thanks for the pro-tip too)
ОтветитьJust dont use nosql dbs
ОтветитьJust for reference, if you're in Microsoft land, you can store secrets in azure keyvault
ОтветитьThis new way seems a little bit cleaner. And you don't forget where they are😅
ОтветитьMORE
ОтветитьFireship is as great as always the main channel was!!! 😁
ОтветитьStoked for this channel!
Ответитьsince when is the terminal developer non friendly
ОтветитьI don't use firebase nor cloud functions so I've always used .env files for my projects. Just add it to the .gitignore and it won't be committed. If I need one in a repo without sensitive information I make a .env.example with empty values for the sensitive fields.
Ответить