Environments

• Hostnames: A hostname identifies a domain (e.g., cdn.example.com) through which your site will be served.
• Origins: An origin configuration defines how our service will communicate with your web servers.
• Rules: A rule determines how requests for a specific environment will be processed.
• Experiments: Randomized experimentation process wherein two or more versions of a variable are shown to different segments of website visitors at the same time to determine which version leaves the maximum impact and drives business metrics.
• Core Web Vitals: Review and analyze performance metrics collected through the measurement of actual Chrome users.
• Caching: By default, deploying to an environment also clears that environment’s cached content. You may manually purge content from the Caching page, the Edgio CLI, or our REST API.
• Environment Variables: An environment variable is a placeholder for sensitive information (e.g., API keys and passwords) that should not be checked into source control.
• Traffic (Analytics): Contains real-time statistics for this environment’s traffic. You may also view a breakdown of traffic by specific routes.
• Real-Time Log Delivery: Delivers log data in near real-time to a variety of destinations.
• User Activity: Contains an audit trail of changes to this environment (e.g., changes to your configuration and deployments).
• Edge Insights: Gain historical and near real-time insights into threat profiles, performance, and CDN usage.
• Traffic Splitting: Create rules to split traffic between multiple origins to conduct A/B testing or implement blue/green deployments.

• By default, Edgio automatically creates an environment upon creating a property. The name of this environment varies according to whether the property was created for use with the Edgio Console or our CLI.
  • Edgio Console: production
  • CLI: default
• You may create additional environments for your property.
  One use for this capability is to set up your environments to match your software development workflow.
  For example, you could create a development, testing, and staging environment to allow your team members to collaborate at every stage of your software development life cycle.
  If you used our Github automation workflow to create a property, then we will create environments for you. You do not need to create additional environments.
• Applying changes to an environment requires a deployment.
• Deployments to your environments are versioned. This allows you to quickly roll back your environment’s configuration to a known working version.

Creating an Environment #

1. Load the Environments page.
   1. From the Edgio Console, select the desired private space or organization.
   2. Select the desired property.
   3. From the left-hand pane, click Environments.
2. Click + New Environment.

   

3. In the Name option, specify a name for this environment. This name may consist of lowercase characters, numbers, dashes (-), and underscores (_).
4. Optional. Copy environment variables, A/B testing configuration, and notes from another environment by selecting it from the Copy settings from environment option.
5. Determine deployment permissions through the Restrict Editors to read-only access option.
   • Mark this option to prevent Editors from configuring or deploying to this environment.
   • Clear this option to allow Editors to configure and deploy to this environment.
   Regardless of this option, deploy tokens, Maintainers, and Admins are always allowed to configure or deploy to this environment.
6. Determine whether this environment will be tagged as production through the Make this my production environment option.

   

7. Click Create.

Environment Variables #

• System-defined: Edgio automatically defines the following variables within each environment:
  • NODE_ENV: By default, this variable is set to production. Override this default value by creating a variable called NODE_ENV and setting it to the desired value.
  • EDGIO_ENVIRONMENT_NAME: This read-only variable is set during deployment to the name of the environment (e.g., production) being deployed.
• Custom: Create custom variables for sensitive information (e.g., API keys and passwords) that should be excluded from source control.

Managing Environment Variables #

• Applying environment variable changes requires a deployment.
• Once an environment variable has been marked as secret, you cannot unset the Keep this value a secret option for that environment variable.
• The value assigned to a secret environment variable is masked using asterisks and it is never revealed. However, you may set it to a different value.

1. Load the Environment Variables page.
   1. From the Edgio Console, select the desired private space or organization.
   2. Select the desired property.
   3. From the left-hand pane, select the desired environment from under the Environments section.
   4. From the left-hand pane, select Environment Variables.
2. Click + Add an Environment Variable.
3. In the Key option, type a name for this environment variable.
4. In the Value option, assign a value to this environment variable.
5. If this environment variable contains sensitive information that should not be revealed to other team members, then you should mark the Keep this value a secret option. Otherwise, this option should be cleared.
6. Click Add variable.

1. Load the Environment Variables page.
   1. From the Edgio Console, select the desired private space or organization.
   2. Select the desired property.
   3. From the left-hand pane, select the desired environment from under the Environments section.
   4. From the left-hand pane, select Environment Variables.
2. Click on the desired environment variable.
3. Modify the environment variable’s name, value, or both.
4. Click Apply.

1. Load the Environment Variables page.
   1. From the Edgio Console, select the desired private space or organization.
   2. Select the desired property.
   3. From the left-hand pane, select the desired environment from under the Environments section.
   4. From the left-hand pane, select Environment Variables.
2. Click on the

   

   icon next to the desired environment variable.
3. When prompted, click Remove Variable to confirm the permenant deletion of that environment variable.

Accessing Environment Variables #

Build Time #

Runtime #

1// edgio.config.js
2const defaultHostname = 'origin.my-site.com'
3
4module.exports = {
5  backends: {
6    origin: {
7      domainOrIp: process.env.HOST || defaultHostname, // Falling back to defaultHostname is needed during the initial
8      hostHeader: process.env.HOST || defaultHostname, // deployment of your site, when an environment is not yet configured.
9    },
10  },
11}

dotenv #

1// edgio.config.js
2require('dotenv').config()

Production Environment #

1. From the Edgio Console, select the desired private space or organization.
2. Select the desired property.
3. From the left-hand pane, select Environments.
4. Find the desired environment and click its

   

   icon. After which, click Make this my production environment.
5. CDN-as-Code: When prompted, confirm the redeployment of the environment that was previously marked as production and the newly tagged environment by clicking Make “ENVIRONMENT NAME” my production environment.

Deleting an Environment #

1. Load the Environments page.
   1. From the Edgio Console, select the desired private space or organization.
   2. Select the desired property.
   3. From the left-hand pane, select the desired environment from under the Environments section.
2. Click the

   

   icon next to the desired environment and then click Delete.
3. When prompted, click Remove Environment to confirm the permenant deletion of that environment.