Firebase — web app configuration
firebase/web · version 1
envs add firebase/web
This declares the keys below in your catalog and sets none of them. A template is a schema for keys; it never carries a value.
| Key | Needed | Kind | Notes |
|---|---|---|---|
FIREBASE_API_KEY |
required | config | Firebase says keys restricted to Firebase services do not need to be treated as secrets and are safe to include in code or configuration, because unlike most API keys they do not control access to backend resources. Security Rules do that.. where to get it |
FIREBASE_AUTH_DOMAIN |
required | config | Where sign-in happens. Part of the same configuration object Firebase says may be embedded.. where to get it |
FIREBASE_PROJECT_ID |
required | config | Which project. Same configuration object.. where to get it |
FIREBASE_STORAGE_BUCKET |
optional | config | Which storage bucket. Same configuration object.. where to get it |
FIREBASE_MESSAGING_SENDER_ID |
optional | config | For cloud messaging. Same configuration object.. where to get it |
FIREBASE_APP_ID |
optional | config | Which app within the project. Same configuration object. All these names are convention: Firebase documents object properties, and a framework decides its own prefix for reaching the browser.. where to get it |