Environments allow you to manage your splits throughout your development lifecycle — from local development to staging and production.
When you first create your account, your Default workspace will be provided with two environments. By default, these two environments are named Staging and Production. Each environment is automatically set up with its own API keys. These API keys are used to connect the Split SDK to a specific environment.
Each split that you create has its own set of targeting rules in each environment making it easy to define different targeting rules in your staging and production environments. This allows you to quickly change the targeting rules for a specific split for quality testing on your staging environment with confidence that the Split is not enabled for users on your production environments.
You can manage your environments for each workspace from your Admin settings. Here, you can add new environments or edit existing.
The environments section provides you and your team insights into the splits configured in each environment. Teams can now easily toggle between any environment via the environments dropdown.
Navigate to the environments icon to quickly see the status of each split in a given environment and a log of split changes to quickly see any modifications made by your team. Summary statistics and sorting provide an easy starting point to find the splits you and your team are managing.
When you first create your account, you're provided with two environments. By default, these two environments are named Staging and Production.
To manage your environments, go to the workspaces tab in your Admin Settings page. There, you can select the workspace that you want to edit environments for.
A. You can quickly rename environments to match your deployment process as well update their permissions.
B. You can add additional environments by clicking Add Environment.
Splits start their life on one developer's machine. A developer should be able to set up a split on their development machine without the SDK requiring network connectivity. We call this the Localhost environment.
This special environment does not show up in the web console, because by definition that requires network connectivity. To configure your SDK for this mode, refer to your language SDK guide.