Skip to content

Configuration schema

fireemu.toml is described by a JSON Schema. Download it from this site, or read it in the repository:

Fireemu reads both TOML (fireemu.toml) and JSON (fireemu.json); discovery loads the file in the current directory and refuses to start if both exist, unless you select one with --config.

Fireemu validates the file at startup, including rules the schema cannot express, and stops with an error on a value it does not accept.

Section What it configures Guide
schemaVersion Always 1
profile, productionExact Production or official-emulator behavior Profiles and productionExact
firebaseJson The firebase.json to read ports, rules, indexes and Functions from Configuration files
firestore Edition, API mode, indexes, limits, history Cloud Firestore
rules Firestore Security Rules source, and the denial log for Firestore and Storage Security Rules
auth Sign-in methods, password policy, MFA, tenants, providers, tokens, and whether the Firestore, Storage and Realtime Database Security Rules surfaces accept unsigned mock ID tokens (allowUnsignedIdTokens) Authentication
storage Storage Security Rules and stored-byte limit Cloud Storage
database What a Realtime Database instance without a rules file allows (defaultAccess); auth.allowUnsignedIdTokens decides, in both profiles, whether its rules accept @firebase/rules-unit-testing mock tokens Realtime Database
functions Codebase, runner, application clock, unserved triggers Cloud Functions
scheduler Time zone, catch-up and overlap of scheduled functions Time and scheduled functions
pubsub, eventarc Authentication and delivery settings Pub/Sub and Eventarc
appCheck Apps, debug tokens and enforcement App Check
daemon Ports, project, start time Time and scheduled functions
network Listening off loopback CI and containers