Overview
Using environments
Overview
Using environments
Learn how to use Environments for testing and authentication.
The DevXP engineering team hosts office hours every Thursday at 11 a.m. Pacific Time where we answer your questions live and help you get up and running with Flatfile. Join us!
EnvironmentsLearn more about Environments are isolated entities and are intended to be a safe place to create and test different configurations.
A development and production environment are created on default.
Environments have two guest authentication types:
magic_linksends your guests an email with a magic link to login.shared_linkmakes the Space url public, and is used with embedded Flatfile.
| isProd | Name | Description |
|---|---|---|
| false | development | Use this default environment, and it’s associated test API keys, as you build with Flatfile. |
| true | production | When you’re ready to launch, create a new environment and swap out your keys. |
The development environment does not count towards your paid credits.
Secret and publishable keys
All Accounts have two key types for each environment. Learn when to use each type of key:
| Type | Id | Description |
|---|---|---|
| Secret key | sk_23ghsyuyshs7dcrty | On the server-side: Store this securely in your server-side code. Don’t expose this key in an application. |
| Publishable key | pk_23ghsyuyshs7dcert | On the client-side: Can be publicly-accessible in your application’s client-side code. Use when embedding Flatfile. |