website logo
โŒ˜K
Floodgate Documentation Portal
๐Ÿš€GETTING STARTED
Quick Start Tutorial
Basic Concepts
๐ŸšฉMANAGING FLAGS
Feature Flag Dashboard
Creating a Feature Flag
Environment Flag Dashboard
Environment Flag Settings
Feature Flag Kill Switch
Updating a Feature Flag
Deleting a Feature Flag
๐Ÿ–ฅ๏ธAPPLICATIONS
About Applications
Creating New Applications
Switching Applications
โ›…ENVIRONMENTS
About Environments
Creating New Environments
๐Ÿ’—MANAGING YOUR TEAM
Team Members Dashboard
Managing Team Member Permissions
Inviting Team Members
โš™๏ธADMINISTRATION
Managing Subscriptions
Usage
๐Ÿ”ŒINTEGRATIONS
Microsoft Teams
Slack
๐Ÿ› ๏ธDEVELOPMENT
The User Object
โœ”๏ธSDKs
Floodgate SDK Overview
.NET SDK Documentation
Java SDK Documentation
PHP SDK Documentation
Node.js SDK Documentation
JavaScript SDK Documentation
Docs powered byย archbeeย 
3min

About Environments

Environments allow you to organize your application into separate units, each unit having its own copy of a feature flag. An environment allows you to manage the state of your flags throughout the development lifecycle. Most of the time your environments in Floodgate will be the same as the environments in your infrastructure that your application is delivered to. For example, Development, QA and Production. You can even create individual environments for each developer in your team allowing them to work independently when necessary. You can create as many environments as you need in your applications, though the number is limited to the subscription plan you are currently on.

Getting Started

When you signed up for Floodgate an application was created for you along with 2 environments, Production and Test. Each environment is created with a unique key called the SDK Key. This key is what allows the Floodgate SDKs to communicate with the correct configuration data on the Floodgate servers.

As your application is deployed between environments, the SDK Key the application uses will change. This means the flag configuration your application is using can be different for each environment.

Important

Your SDK Key should not be hard coded in your application and should be loaded in at runtime from environment variables for example.

You can switch between environments in your application by clicking on the environment name from the main navigation on the left.

Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Creating New Environments
Docs powered byย archbeeย 
TABLE OF CONTENTS
Getting Started
Important