Skip to main content
Classic

Manage Application

Learn how to manage an application in your Section account.

Create application​

Follow the steps below to create an application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, click Create application and then follow the provided steps.
note

Creating an application can take a few minutes to complete once submitted.

Delete​

Follow the steps below to delete an application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to delete.
  4. In the top subnavigation bar, click Delete Application.
  5. Enter the application name and click Delete application.
caution

Ensure all traffic has been migrated before deleting an application.

Create environment​

Follow the steps below to split an application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to create an environment in.
  4. In the top subnavigation bar, click Create Environment.
  5. Enter the new environment name and hostname and then click Create.

Delete​

Environments cannot be deleted at this time.

Quick config​

Follow the steps below to quickly configure modules for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to quickly configure.
  4. In the top navigation bar, select the environment you want to quickly configure (e.g. Production).
  5. In the left sidebar, click Quick Config.
  6. In the top subnavigation bar, click the module you want to quickly configure. This can be done for the following modules:

Advanced config​

Follow the steps below to configure your environment:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to configure.
  4. In the top navigation bar, select the environment you want to configure (e.g. Production).
  5. In the left sidebar, click Advanced Config.
  6. Configure the environment with Git either fully from a command line interface (CLI) or partially through the web user interface.
note

The configuration of an environment is controlled by the associated Git repository hosted by Section. Clone, commit, and push changes to the Git repository for your environment in the same way as any other Git repository, for example:

git clone https://aperture.section.io/account/1/application/1/www.example.com.git
...
cd www.example.com
touch README.md
git add .
git commit -m "Add README.md"
git push
tip

Clone with HTTPS by using section-token as the username and an API token as the password instead of the username and password of your Section user, for example:

git clone https://aperture.section.io/account/1/application/1/www.example.com.git
Cloning into 'www.example.com'...
Username for 'https://aperture.section.io': section-token
Password for 'https://section-token@aperture.section.io': <api_token>

Clear cache​

Follow the steps below to clear the cache for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to clear the cache for.
  4. In the top navigation bar, select the environment you want to clear the cache for (e.g. Production).
  5. In the left sidebar, click Clear Cache.
  6. In the top subnavigation bar, click the module you want to clear the cache for. This can be done for the following modules:
note

Clearing the cache takes under 200ms for all locations to be cleared.

caution

Clearing the cache can temporarily increase traffic sent to the origin.

IP restrictions​

Follow the steps below to set up request restrictions by IP address for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to set up request restrictions for.
  4. In the top navigation bar, select the environment you want to set up request restrictions for (e.g. Production).
  5. In the left sidebar, click IP Restrictions.
  6. Add, edit, or delete IP addresses and/or CIDR blocks and then click Save.
note

IP restrictions are added to the first layer of an environment's proxy stack (edge proxy).

tip

IP restrictions can also be set in the section.config.json file.

Origins​

Follow the steps below to set up the origin(s) for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to set up the origin(s) for.
  4. In the top navigation bar, select the environment you want to set up the origin(s) for (e.g. Production).
  5. In the left sidebar, click Origins.
  6. Add, edit, or delete origin configurations and then click Save changes.
note

Alternate origins require the section-origin request header to be set in the proxy stack. The value must be the alternate origin name.

Alternate origins that are removed or renamed can continue to honor the old name, in addition to the new configuration. The old definitions will only be removed as old Egress Pods are eventually replaced.

tip

Origins can also be set in the section.config.json file.

Monitoring​

Follow the steps below to view real-time monitoring for your application and all of its environments:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to view real-time monitoring for.
  4. In the left sidebar, click Monitoring.
  5. In the top subnavigation bar, click the type of monitoring you want to view.
tip

Check out the related Grafana and Graphite documentation to get started with customizing your monitoring dashboards.

HTTP logs​

Follow the steps below to view real-time HTTP logs for your application and all of its environments:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to view real-time HTTP logs for.
  4. In the left sidebar, click HTTP Logs.
note

HTTP logs are only accessible for the last seven days. Submit a support request if you are interested in shipping these logs to your own HTTP endpoint.

tip

Check out the related Kibana documentation to get started with analyzing and visualizing your HTTP logs.

Deployment logs​

Follow the steps below to view real-time deployment logs for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to view real-time deployment logs for.
  4. In the top navigation bar, select the environment you want to view real-time deployment logs for (e.g. Production).
  5. In the left sidebar, click Deployment Logs.
note

Deployments are triggered by changes made to your environment (e.g. advanced config). The deployment time will vary depending on the change made and modules in your environment.

DNS​

Follow the steps below to set up the DNS for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to set up the DNS for.
  4. In the top navigation bar, select the environment you want to set up the DNS for (e.g. Production).
  5. In the left sidebar, click DNS.
  6. Add and delete environment domains, create a new hosted DNS zone, or temporarily pause traffic from going through Section.

HTTPS​

Follow the steps below to set up the SSL/TLS certificate(s) for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to set up the SSL/TLS certificate(s) for.
  4. In the top navigation bar, select the environment you want to set up the SSL/TLS certificate(s) for (e.g. Production).
  5. In the left sidebar, click HTTPS.
  6. Set up the SSL/TLS certificate(s) for the environment domain(s) in your application either through an automatically generated Let's Encrypt certificate or by uploading a custom certificate.
note

Let's Encrypt certificates are automatically renewed and cannot be used for wildcard domains. Please note Let's Encrypt imposes rate limits that you must follow.

Outage pages​

Follow the steps below to set up outage pages for an environment in your application:

  1. Log in to your Section account.

  2. In the left sidebar, click Account and Billing.

  3. In the applications list, find and click the application you want to set up outage pages for.

  4. In the top navigation bar, select the environment you want to set up outage pages for (e.g. Production).

    Create outage page​

    1. In the advanced config, create an outage_pages directory in the root directory of the environment repository.

    2. In the outage_pages directory, add your outage pages in HTML format with the .html extension, for example:

      .
      ├── custom_errors
      │   └── 500.html.sample
      ├── local.config.json.sample
      ├── outage_pages
      │   ├── maintenance.html
      │   └── sale.html
      └── section.config.json
      caution

      Outage pages cannot contain resources hosted within the environment that the outage page will be engaged on.

    Engage outage page​

    1. In the left sidebar, click Outage Pages.

    2. In the outage pages list, select a page and then click Engage.

      note

      Engaged outage pages are displayed for all environment domains.

    Disengage outage page​

    1. In the left sidebar, click Outage Pages.
    2. In the outage pages list, click Disengage.

Custom error pages​

Follow the steps below to set up custom error pages for an environment in your application:

  1. Log in to your Section account.

  2. In the left sidebar, click Account and Billing.

  3. In the applications list, find and click the application you want to set up custom error pages for.

  4. In the top navigation bar, select the environment you want to set up custom error pages for (e.g. Production).

  5. In the advanced config, go to (or create) the custom_errors directory in the root directory of the environment repository.

  6. In the custom_errors directory, add your custom error pages in HTML format with the .html file extension and the status code it represents as the file name, for example:

    .
    ├── custom_errors
    │   ├── 403.html
    │   ├── 404.html
    │   ├── 500.html
    │   ├── 502.html
    │   ├── 503.html
    │   └── 504.html
    ├── local.config.json.sample
    ├── outage_pages
    │   ├── maintenance.html
    │   └── sale.html
    └── section.config.json
    note

    Custom error pages can only be created for valid nginx status codes between 300 and 599 (excluding 499). Pages for the 502 and 504 status codes will also be applied to 522 and 524.

Whitelist origin requests​

Follow the steps below to whitelist origin requests for an environment in your application:

  1. Log in to your Section account.
  2. In the left sidebar, click Account and Billing.
  3. In the applications list, find and click the application you want to whitelist origin requests for.
  4. In the top navigation bar, select the environment you want to whitelist origin requests for (e.g. Production).
  5. In the advanced config, use one of the following modules to add a secret request header to whitelist on the origin:
note

Submit a support request if you are interested in whitelisting origin requests by IP address.