Function Store
  • Home
  • Getting started
    • Introduction
    • Installing a function
    • Reconfiguring a function
    • Uninstalling a function
    • FAQs
  • Reference
    • Requirements
      • Assign Roles
        • User permissions
      • Link a Billing account to your project
      • Enable the APIs
    • Projects
      • How to add a project
      • How to set up a project
    • Functions
      • Benefits
      • Use cases
      • Authentication when installing
      • Runtime configuration
      • Deploying with a ZIP file
    • Policies
      • How to add a Policy
      • How to remove a Policy
    • Authentication
      • Users
      • Roles
      • Permissions
    • Secrets
      • Creating a Secret
      • Using a Secret
      • Changing the value for a Secret
      • Deactivating a Secret
  • developers
    • Overview
    • Getting Started
    • Set up
    • Workspaces
      • Create a workspace
      • Workspace boilerplate
      • Node engines
    • Writing Functions
      • Function Anatomy
      • Configuration file
      • Function Triggers
      • Environment Variables
        • Type "text"
        • Type "number"
        • Type "email"
        • Type "url"
        • Type "json"
        • Type "boolean"
        • Type "select"
        • Type "multiselect"
        • Type "firestoreDocumentPath"
        • Type "firestoreCollectionPath"
        • Type "color"
      • Documentation
    • Push/Update your functions in the cloud
    • Continuous Integration
    • Publish functions in the Marketplace
    • Emulators
      • Initialize emulators in your workspace
      • Environment variables
      • Starting emulators
      • Testing your functions in the emulator
      • Importing existing data into local emulators
        • Exporting data from Cloud Firestore to local emulator
        • Exporting user accounts from Firebase to local emulator
    • Visual Studio Code Extension
      • Installing the extension
      • Extension UI
      • Functions list
      • Creating and editing functions
      • Emulators
      • Extension settings
      • Troubleshooting
        • "Command not found" error when executing a command
  • Billing
    • Understanding Billing
  • Security
    • Security
  • Resources
    • Events and Triggers
    • Best Practices
      • How to log events in functions?
    • Document your Functions
    • Editorial guidelines
    • Our Processes
      • Use Cases Analysis
  • Use cases
    • Custom Stripe Checkout
Powered by GitBook
On this page

Was this helpful?

  1. developers
  2. Emulators

Environment variables

How to set up the function execution environment.

PreviousInitialize emulators in your workspaceNextStarting emulators

Last updated 3 years ago

Was this helpful?

The environment variables of the functions are managed with .

In order to make your function environment variables available through process.env, create a .env file inside the emulator folder and add variables on new lines in the form of NAME=VALUE. For example:

Assuming we have a function containing the following function.config.json:

{
    "name": "helloWorld",
       "description": "Http function that responds with Hello World!",
    "tags": [ "demo", "first-function"],
       "trigger": {
        "provider": "https",
        "event": "request"
    },
    "env": [{
        "name": "SOME_VAR",
        "description": "Check the implementation in main.js to see how we use the environment variable while coding."
    }, {
        "name": "ANOTHER_VAR",
        "description": "Check the implementation in main.js to see how we use the environment variable while coding."
    }]
}

The content of your .env file must be:

SOME_VAR=Some value
ANOTHER_VAR=Some value for another var

dotenv