When working with demo Firebase projects, your apps and code interact withĮmulators only. Project IDs for demo projects have the demo- prefix. These projects are usually accessed via codelabs or Interact with the live resource (database instance, storageĪ demo Firebase project has no real Firebase configuration and When working with real Firebase projects, you can run emulators for anyįor any products you are not emulating, your apps and code will Real projects have live resources, like database instances, storageīuckets, functions, or any other resource you set up for that Firebase Local Emulator Suite supports emulation of real Firebase projects andĪ real Firebase project is one you created and configured (most likely Guidance on setting and managing project IDs, see the Installation and configuration guide. Multiple project IDs in use, though you can override this behavior. In fact, by default, the Local Emulator Suite will warn on detecting Running instances of a particular emulator can communicate correctly in allĬases. Invocations, so the Emulator Suite UI, different product emulators, and all Note: It's generally a good practice to use one project ID for all emulator To select the project to use, before you start the emulators, in the CLI runįirebase use in your working directory. The Firebase Local Emulator Suite emulates products for a single Firebase project. The Local Emulator Suite and review its CLI commands. You understand the overall Firebase Local Emulator Suite workflow, Before connecting your app to the Cloud Firestore emulator, make sure that

Run 8 train simulator demo