Related to #1564

SO not Wasp app users but Wasp framework users! Maybe we should say Wasp devs, not sure.

This is interesting use case. I think it falls under secret management. We have plans to make it easier to do this for .env files. But it could be used for other files also. I wonder what is the best practice though. They key.json -> I imagine it might be better to take its contents/value and just put it directly into .env.server, why woudln't that be the solution? Soudns a bit unusual to keep that file around. Is there a standardized way of dealing with that key.json file? What does Google Cloud recommend?

SO not Wasp app users but Wasp framework users!

Yes, this trips me up all the time. When I say users, I usually mean Wasp framework users, and for Wasp app users I say "Wasp app users."

When I hear "Wasp devs", I think about the three of us 😄

I don't know what to do, but we can agree on something and make it consistent.

As for the keys.json specifically - I have no idea what the best practice is (maybe it's indeed better to just use an env variable). That's what I told Connor to do in Discord.