There are two ways to do it. The Firebase team members that I’ve talked to recommend using different Firebase projects and pointing to the different projects in your client code.
I personally prefer to use one project and prefix my paths with /development, /test or /production. The risk to doing everything within one project is that you have to be careful not to blow away your prod data by running a .set() function on the root of your db… or making any other sort of mistake that can break prod.
The upside to keeping it all in one project is that it’s easier to keep things consistent between environments, and there’s less overhead in managing extra projects and their service account keys.
It really comes down to separation vs ease of use. I go for ease of use… but it’s hard to recommend that, because separation is much safer.
