From c9108590aa344f52a2cdacac82a87179ce801d39 Mon Sep 17 00:00:00 2001 From: AnouckColson <113913013+AnouckColson@users.noreply.github.com> Date: Mon, 11 Sep 2023 10:29:40 +0200 Subject: [PATCH] Revert "Preview environments update" (#3426) * Revert "Preview environments update" This reverts commit e685d7b0c6791e2ff042d7174b50bb3dfc80d8fb. * Revert links * Fix conflict and correct mistake --- sites/platform/.yaml | 9 +- sites/platform/src/add-services/_index.md | 2 +- sites/platform/src/add-services/mongodb.md | 2 +- .../platform/src/add-services/mysql/_index.md | 2 +- sites/platform/src/add-services/postgresql.md | 2 +- .../src/administration/pricing/_index.md | 16 ++-- sites/platform/src/administration/users.md | 2 +- .../web/configure-environment.md | 2 +- .../platform/src/create-apps/app-reference.md | 14 +-- .../hooks/vary-hooks-by-environment.md | 2 +- .../src/create-apps/source-operations.md | 2 +- .../architecture/development.md | 16 ++-- sites/platform/src/define-routes/_index.md | 8 +- sites/platform/src/development/email.md | 2 +- .../src/development/sanitize-db/_index.md | 2 +- .../src/development/sanitize-db/mariadb.md | 4 +- .../sanitize-db/postgresql-symfony.md | 8 +- .../src/development/sanitize-db/postgresql.md | 6 +- .../platform/src/development/troubleshoot.md | 2 +- .../development/variables/set-variables.md | 2 +- sites/platform/src/domains/steps/_index.md | 2 +- ...ts.md => custom-non-production-domains.md} | 87 ++++++++++--------- sites/platform/src/domains/steps/tls.md | 4 +- sites/platform/src/environments/_index.md | 8 +- sites/platform/src/environments/backup.md | 2 +- .../src/environments/http-access-control.md | 2 +- .../environments/search-engine-visibility.md | 4 +- .../src/get-started/add-data/branch.md | 6 +- .../src/get-started/add-data/merge.md | 6 +- .../src/guides/django/deploy/next-steps.md | 2 +- .../src/guides/gatsby/headless/drupal.md | 2 +- .../guides/symfony/environment-variables.md | 6 +- sites/platform/src/guides/symfony/faq.md | 2 +- .../src/integrations/activity/reference.md | 2 +- sites/platform/src/languages/nodejs/debug.md | 2 +- sites/platform/src/languages/python/_index.md | 2 +- sites/platform/src/languages/ruby.md | 2 +- .../src/learn/overview/build-deploy.md | 4 +- sites/platform/src/other/glossary.md | 23 +---- sites/platform/src/security/backups.md | 4 +- .../guides/gatsby/headless-plansize.md | 4 +- 41 files changed, 129 insertions(+), 152 deletions(-) rename sites/platform/src/domains/steps/{custom-domains-preview-environments.md => custom-non-production-domains.md} (66%) diff --git a/sites/platform/.yaml b/sites/platform/.yaml index 3e5b811c9f..5f9cd72374 100644 --- a/sites/platform/.yaml +++ b/sites/platform/.yaml @@ -167,7 +167,6 @@ elixir: - '1.10' - '1.9' supported: - - '1.15' - '1.14' - '1.13' - '1.12' @@ -574,18 +573,18 @@ opensearch: runtime: false type: opensearch versions: - deprecated: - - '1.2' - - '1.1' + deprecated: [] supported: - '2' - - '1' + - '1.2' + - '1.1' legacy: - '1.1' versions-dedicated-gen-2: deprecated: [] supported: - '2.5' + - '2.4' - '1.2' versions-dedicated-gen-3: deprecated: [] diff --git a/sites/platform/src/add-services/_index.md b/sites/platform/src/add-services/_index.md index 9cadd70471..848e22313a 100644 --- a/sites/platform/src/add-services/_index.md +++ b/sites/platform/src/add-services/_index.md @@ -85,7 +85,7 @@ By default, {{< vendor/name >}} allocates CPU and memory resources to each conta Some services are optimized for high CPU load, some for high memory load. If your plan is sufficiently large for bigger containers, you can increase the size of your service container. -Note that service containers in preview environments are always set to size `S`. +Note that service containers in development environments are always set to size `S`. ### 2. Connect the service diff --git a/sites/platform/src/add-services/mongodb.md b/sites/platform/src/add-services/mongodb.md index 638aa88686..5edb7582a6 100644 --- a/sites/platform/src/add-services/mongodb.md +++ b/sites/platform/src/add-services/mongodb.md @@ -43,7 +43,7 @@ and are no longer receiving security updates from upstream. Downgrades of MongoDB aren't supported. MongoDB updates its own data files to a new version automatically but can't downgrade them. -If you want to experiment with a later version without committing to it use, a preview environment. +If you want to experiment with a later version without committing to it use a non-production environment. {{< /note >}} diff --git a/sites/platform/src/add-services/mysql/_index.md b/sites/platform/src/add-services/mysql/_index.md index c3d22cbb9a..acb6624ae7 100644 --- a/sites/platform/src/add-services/mysql/_index.md +++ b/sites/platform/src/add-services/mysql/_index.md @@ -456,7 +456,7 @@ If not, make a backup or do a database export before importing. ## Sanitizing data To ensure people who review code changes can't access personally identifiable information stored in your database, -[sanitize your preview environments](../../development/sanitize-db/mariadb.md). +[sanitize your development environments](../../development/sanitize-db/mariadb.md). ## Replication diff --git a/sites/platform/src/add-services/postgresql.md b/sites/platform/src/add-services/postgresql.md index cbb0b810f2..7ecd48b2da 100644 --- a/sites/platform/src/add-services/postgresql.md +++ b/sites/platform/src/add-services/postgresql.md @@ -189,7 +189,7 @@ Taking a backup or a database export before doing so is strongly recommended. ## Sanitizing data To ensure people who review code changes can't access personally identifiable information stored in your database, -[sanitize your preview environments](../development/sanitize-db/postgresql.md). +[sanitize your development environments](../development/sanitize-db/postgresql.md). ## Multiple databases diff --git a/sites/platform/src/administration/pricing/_index.md b/sites/platform/src/administration/pricing/_index.md index 06a7de3c6b..fe3f6823d7 100644 --- a/sites/platform/src/administration/pricing/_index.md +++ b/sites/platform/src/administration/pricing/_index.md @@ -40,17 +40,15 @@ choose [another plan](../pricing/_index.md) to go live. Production environments are the live environments available to your users. Each Production plan has one Production environment that can be mapped to a [custom domain name](../../domains/steps/_index.md). -The Production environment has more resources than the project's preview environments. +The Production environment has more resources than the project's development environments. See the main [pricing page](https://platform.sh/pricing) for the resources available per plan for Production environments. -### Preview environments +### Development environments -Preview environments can't use the same custom domain as a production environment. -Instead, you can set up specific [custom domains for each of your preview environments](../../domains/steps/custom-domains-preview-environments.md). +Development environments can't be mapped to [custom domain names](../../domains/steps/_index.md). +Their resources are separate from Production environments. -Preview environments use resources that are separate from production environments. - -App containers on preview environments default to a size of {{< partial "plans/default-dev-env-size" >}}. +App containers on development environments default to a size of {{< partial "plans/default-dev-env-size" >}}. If you have the [manage plans permission](../users.md#organization-permissions), you can increase the size to match your production environment. To do so, follow these steps: @@ -83,9 +81,9 @@ you're billed around 1/3 of the current price for a full month. You can add the following extras: * Users -- for an additional fee per user, except at certain [agency levels](#agencies). -* Environments -- extra preview environments can be added in multiples of 3. +* Environments -- extra staging/development environments can be added in multiples of 3. * Storage -- extra storage can be added for a fee per 5 GB per environment. - So if you have added 3 additional environments for a total of 6 preview environments, + So if you have added 3 additional environments for a total of 6 development environments, the fee is multiplied by 6. To ensure environments are available on demand, the fee applies to all environments you have added even if you aren't currently actively using them. diff --git a/sites/platform/src/administration/users.md b/sites/platform/src/administration/users.md index d158085f2e..3441f9230e 100644 --- a/sites/platform/src/administration/users.md +++ b/sites/platform/src/administration/users.md @@ -32,7 +32,7 @@ An environment type (Production, Staging, and Development) groups one or more en - Only one environment per project can be of the type: Production. It is set automatically as the default branch and can't be overridden separately. - You can change an environment's type (except for the Production environment). -- You can have multiple Staging and Development environments (also called [preview environments](../other/glossary.md#preview-environment)). +- You can have multiple Staging and Development environments. A user can have one of the following roles on an environment type which grants them permissions on all environments of this type: diff --git a/sites/platform/src/administration/web/configure-environment.md b/sites/platform/src/administration/web/configure-environment.md index b35ced7790..4f89b0cb05 100644 --- a/sites/platform/src/administration/web/configure-environment.md +++ b/sites/platform/src/administration/web/configure-environment.md @@ -82,7 +82,7 @@ Under **Status**, you can check whether or not your environment is [active](../. ![Environment status](/images/management-console/env-status.png "0.5") -For preview environments, you can [change their status](../../environments/deactivate-environment.md). +For non-Production environments, you can [change their status](../../environments/deactivate-environment.md). ### Outgoing emails diff --git a/sites/platform/src/create-apps/app-reference.md b/sites/platform/src/create-apps/app-reference.md index a8847f744b..a9a7c4ada2 100644 --- a/sites/platform/src/create-apps/app-reference.md +++ b/sites/platform/src/create-apps/app-reference.md @@ -69,7 +69,7 @@ These are used in the format `runtime:version`: Resources are distributed across all containers in an environment from the total available from your [plan size](../administration/pricing/_index.md). So if you have more than just a single app, it doesn't get all of the resources available. -Each environment has its own resources and there are different [sizing rules for preview environments](#sizes-in-preview-environments). +Each environment has its own resources and there are different [sizing rules for non-production environments](#sizes-in-non-production-environments). By default, resource sizes (CPU and memory) are chosen automatically for an app based on the plan size and the number of other containers in the cluster. @@ -88,12 +88,12 @@ To do so, set `size` to one of the following values: The total resources allocated across all apps and services can't exceed what's in your plan. -### Sizes in preview environments +### Sizes in non-production environments -Containers in preview environments don't follow the `size` specification. +Containers in development environments don't follow the `size` specification. Application containers are set based on the plan's setting for **Environments application size**. The default is **{{< partial "plans/default-dev-env-size" >}}**, but you can increase it by editing your plan. -(Service containers in preview environments are always set to {{< partial "plans/default-dev-env-size" >}} size.) +(Service containers in development environments are always set to {{< partial "plans/default-dev-env-size" >}} size.) ## Relationships @@ -782,7 +782,7 @@ To run cron jobs in a timezone other than UTC, set the [timezone property](#top- ### Paused crons -[Preview environments](../other/glossary.md#preview-environment) ([development type](../other/glossary.md#environment-type)) are often used for a limited time and then abandoned. +Development environments are often used for a limited time and then abandoned. While it's useful for environments under active development to have scheduled tasks, unused environments don't need to run cron jobs. To minimize unnecessary resource use, @@ -790,7 +790,7 @@ crons on environments with no deployments are paused. This affects all environments that aren't live environments. This means all environments on Development plans -and all preview environments on higher plans. +and all non-Production environments on higher plans. Such environments with deployments within 14 days have crons with the status `running`. If there haven't been any deployments within 14 days, the status is `paused`. @@ -800,7 +800,7 @@ or using the CLI by running `{{% vendor/cli %}} environment:info` and looking un #### Restarting paused crons -If the crons on your preview environment are paused but you're still using them, +If the crons on your development environment are paused but you're still using them, you can push changes to the environment or redeploy it. To restart crons without changing anything: diff --git a/sites/platform/src/create-apps/hooks/vary-hooks-by-environment.md b/sites/platform/src/create-apps/hooks/vary-hooks-by-environment.md index 59ec885888..8823ceb71f 100644 --- a/sites/platform/src/create-apps/hooks/vary-hooks-by-environment.md +++ b/sites/platform/src/create-apps/hooks/vary-hooks-by-environment.md @@ -4,7 +4,7 @@ description: Change what runs in your hooks depending on the current environment --- You might have certain commands you want to run only in certain environments. -For example enabling detailed logging in preview environments +For example enabling detailed logging in development environments or purging your CDN cache for production environments. The `deploy` and `post_deploy` hooks can access all [runtime environment variables](../../development/variables/use-variables.md#use-provided-variables). diff --git a/sites/platform/src/create-apps/source-operations.md b/sites/platform/src/create-apps/source-operations.md index 761e09bdfe..db94ef57ff 100644 --- a/sites/platform/src/create-apps/source-operations.md +++ b/sites/platform/src/create-apps/source-operations.md @@ -303,7 +303,7 @@ The following source operation syncronizes your branch with an upstream Git repo If there’s a conflict merging from the upstream repository, the source operation fails and doesn't update from the upstream repository. -Run the `upstream-update` operation on a preview environment rather than directly on Production. +Run the `upstream-update` operation on a Development environment rather than directly on Production. ### Revert to the last commit diff --git a/sites/platform/src/dedicated-gen-2/architecture/development.md b/sites/platform/src/dedicated-gen-2/architecture/development.md index 4f03d1effc..3bce4543fc 100644 --- a/sites/platform/src/dedicated-gen-2/architecture/development.md +++ b/sites/platform/src/dedicated-gen-2/architecture/development.md @@ -1,30 +1,30 @@ --- -title: "{{< vendor/name >}} {{% names/dedicated-gen-2 %}} preview environments" +title: "{{< vendor/name >}} development environments" weight: 2 sidebarTitle: "Dev environments" description: "{{% names/dedicated-gen-2 %}} customers have a development environment for their project that consists of a {{< vendor/name >}} Grid project, typically provisioned by the {{< vendor/name >}} team to reflect the amount of storage in your contract. This environment provides you with all the DevOps, Continuous Integration, Continuous Deployment, and other workflow tooling of the professional product, but segregates the performance impacts from your production hardware." --- -## Architecture (preview environments) +## Architecture (Development Environments) ![{{< vendor/name >}} Professional architecture](/images/dedicated/PS-Arch-NoHA.svg "0.6") ## Default limits -{{% names/dedicated-gen-2 %}} projects provide `production` and `staging` branches linked to the {{% names/dedicated-gen-2 %}} cluster +The Development Environment for a {{% names/dedicated-gen-2 %}} project provides `production` and `staging` branches linked to the {{% names/dedicated-gen-2 %}} cluster and 3 additional active environments for development. This number can be increased if needed for an additional fee. The default storage for {{% names/dedicated-gen-2 %}} contracts is 50GB per environment (production, staging, and each development environment). This comprises total storage for your project and is inclusive of any databases, uploaded files, writable application logging directories, search index cores, and so on. -The storage amount dedicated to your preview environments depends on the terms of your Enterprise contract. +The storage amount for your development environment reflects the amount in your Enterprise contract. -A project may have up to six users associated with it at no additional charge. +A project may have up to six (6) users associated with it at no additional charge. Additional users may be added for an additional fee. -These users have access to both the preview environments and the {{% names/dedicated-gen-2 %}} cluster. +These users have access to both the Development environment and the {{% names/dedicated-gen-2 %}} cluster. -## Larger preview environments +## Larger developments environments -By default, all containers in preview environments are {{< partial "plans/default-dev-env-size" >}} sized, as they have limited traffic needs. +By default, all containers in development environments are {{< partial "plans/default-dev-env-size" >}} sized, as they have limited traffic needs. For more resource-intensive applications this size can be increased for an additional fee. diff --git a/sites/platform/src/define-routes/_index.md b/sites/platform/src/define-routes/_index.md index 323eb97d13..8663f483e5 100644 --- a/sites/platform/src/define-routes/_index.md +++ b/sites/platform/src/define-routes/_index.md @@ -143,9 +143,9 @@ And you can use an absolute URL: In both cases, the URLs for your Production environment are the same. -#### URLs in preview environments +#### URLs in non-Production environments -URLs in preview environments follow a different pattern. +URLs in non-Production environments follow a different pattern. No matter how you have set your default domain (even if you don't have one), using either the absolute URL or the `{default}` placeholder results in the same URL. @@ -160,7 +160,7 @@ Note that the `example.com` prefix isn't part of the generated URL. {{< note title="Previous behavior" >}} -Before April 7, 2022, URLs in preview environments differed depending on whether or not you used the `{default}` placeholder. +Before April 7, 2022, URLs in non-Production environments differed depending on whether or not you used the `{default}` placeholder. If you used the `{default}` placeholder: @@ -241,7 +241,7 @@ Prefix a route with an asterisk (`*`), for example `*.{default}`. If you have configured `example.com` as your default domain, HTTP requests to `www.example.com`, `blog.example.com`, and `us.example.com` are all routed to the same endpoint. -It also works on preview environments. +It also works on development environments. If you have a `feature` branch, it's `{default}` domain looks something like: `feature-def123-vmwklxcpbi6zq.us.platform.sh` (depending on the project's region). So requests to `blog.feature-def123-vmwklxcpbi6zq.us.platform.sh` and `us.feature-def123-vmwklxcpbi6zq.eu.platform.sh` diff --git a/sites/platform/src/development/email.md b/sites/platform/src/development/email.md index 033238461f..d29dd2b776 100644 --- a/sites/platform/src/development/email.md +++ b/sites/platform/src/development/email.md @@ -12,7 +12,7 @@ The SMTP proxy is intended as a zero-configuration, best-effort service. {{< note >}} -All preview environments are limited to 12,000 email credits per calendar month. +All non-production environments are limited to 12,000 email credits per calendar month. {{< /note >}} diff --git a/sites/platform/src/development/sanitize-db/_index.md b/sites/platform/src/development/sanitize-db/_index.md index 1ad9396d5c..654747cc83 100644 --- a/sites/platform/src/development/sanitize-db/_index.md +++ b/sites/platform/src/development/sanitize-db/_index.md @@ -1,6 +1,6 @@ --- title: Sanitize databases -description: Remove sensitive information from databases on preview environments to control access. +description: Remove sensitive information from databases on non-production environments to control access. layout: list toc: false keywords: diff --git a/sites/platform/src/development/sanitize-db/mariadb.md b/sites/platform/src/development/sanitize-db/mariadb.md index 02e09d03e3..f57e567a27 100644 --- a/sites/platform/src/development/sanitize-db/mariadb.md +++ b/sites/platform/src/development/sanitize-db/mariadb.md @@ -1,7 +1,7 @@ --- title: "Sanitizing databases: MariaDB and Drupal" sidebarTitle: MariaDB and Drupal -description: Sanitize MariaDB data in preview environments directly or by using Drush. +description: Sanitize MariaDB data in non-production environments directly or by using Drush. layout: list --- @@ -23,7 +23,7 @@ title=With Drupal and Drush To sanitize your database and get rid of sensitive, live information, use the `drush sql:sanitize` command. Add your script to sanitize the database to [a `deploy` hook](../../create-apps/hooks/hooks-comparison.md#deploy-hook) -for preview environments: +for non-production environments: ```yaml {configFile="app"} hooks: diff --git a/sites/platform/src/development/sanitize-db/postgresql-symfony.md b/sites/platform/src/development/sanitize-db/postgresql-symfony.md index b0a41c0611..b29b559a7c 100644 --- a/sites/platform/src/development/sanitize-db/postgresql-symfony.md +++ b/sites/platform/src/development/sanitize-db/postgresql-symfony.md @@ -1,7 +1,7 @@ --- title: "Sanitizing databases: PostgreSQL and Symfony" sidebarTitle: PostgreSQL and Symfony -description: Sanitize PostgreSQL data in preview environments for Symfony apps. +description: Sanitize PostgreSQL data in non-production environments for Symfony apps. layout: list --- @@ -122,7 +122,7 @@ Set up a script by following these steps: ``` Push the changes to `staging` and verify that environment's database was sanitized. - Once merged to production, all data from future preview environments are sanitized on environment creation. + Once merged to production, all data from future non-production environments are sanitized on environment creation. <---> +++ @@ -146,7 +146,7 @@ Set up a script by following these steps: 3. Make the script sanitize environments with an [environment type](../../administration/users.md#environment-type-roles) other than `production`. - The following example runs only in preview environments + The following example runs only in non-production environments and sanitizes data using the Symfony Command from previous tab, already pushed to all of your environments. ```bash {location="sanitize_fleet.sh"} @@ -286,7 +286,7 @@ You can find the organization identifier for a specific project, within the {{< ``` Push the changes to `staging` and verify that environment's database was sanitized. - Once merged to production, all data from future preview environments are sanitized on environment creation. + Once merged to production, all data from future non-production environments are sanitized on environment creation. {{< /codetabs >}} diff --git a/sites/platform/src/development/sanitize-db/postgresql.md b/sites/platform/src/development/sanitize-db/postgresql.md index 619602576a..cdc512c151 100644 --- a/sites/platform/src/development/sanitize-db/postgresql.md +++ b/sites/platform/src/development/sanitize-db/postgresql.md @@ -1,7 +1,7 @@ --- title: "Sanitizing databases: PostgreSQL and Django" sidebarTitle: PostgreSQL and Django -description: Sanitize PostgreSQL data in preview environments for Django apps. +description: Sanitize PostgreSQL data in non-production environments for Django apps. layout: list --- @@ -49,7 +49,7 @@ Set up a script by following these steps: 3. Make the script sanitize environments with an [environment type](../../administration/users.md#environment-type-roles) other than `production`. - The following example runs only in preview environments + The following example runs only in non-production environments and sanitizes the `display_name` and `email` columns of the `users` table. Adjust the details to fit your data. @@ -93,7 +93,7 @@ Set up a script by following these steps: ``` Push the changes to `staging` and verify that environment's database was sanitized. - Once merged to production, all data from future preview environments are sanitized on environment creation. + Once merged to production, all data from future non-production environments are sanitized on environment creation. {{< /codetabs >}} diff --git a/sites/platform/src/development/troubleshoot.md b/sites/platform/src/development/troubleshoot.md index ee22df023b..d66c98f153 100644 --- a/sites/platform/src/development/troubleshoot.md +++ b/sites/platform/src/development/troubleshoot.md @@ -129,7 +129,7 @@ Typical causes and potential solutions include: ## Site outage -If you can't access some part of your project, whether it's the live site, a preview environment, or the Console, +If you can't access some part of your project, whether it's the live site, development environment, or Console, check the [{{< vendor/name >}} status page](https://status.platform.sh/). There you can see planned maintenance and subscribe to updates for any potential outages. diff --git a/sites/platform/src/development/variables/set-variables.md b/sites/platform/src/development/variables/set-variables.md index b1b8639a3d..e9581620a4 100644 --- a/sites/platform/src/development/variables/set-variables.md +++ b/sites/platform/src/development/variables/set-variables.md @@ -164,7 +164,7 @@ Environment variables are a good place to store values that apply only on {{< ve This includes API credentials for third-party services, mode settings, and which server (development vs. production) to use. One example would be to define a Node.js application's build on a production branch (`NODE_ENV=production`), -but use development mode (`NODE_ENV=development`) for each of your preview environments. +but use development mode (`NODE_ENV=development`) for each of your development environments. Assuming you have a `main` environment for production and a `staging` environment with more child environments for development, run the following commands: diff --git a/sites/platform/src/domains/steps/_index.md b/sites/platform/src/domains/steps/_index.md index f51dd5bbcd..2b4f607929 100644 --- a/sites/platform/src/domains/steps/_index.md +++ b/sites/platform/src/domains/steps/_index.md @@ -8,7 +8,7 @@ layout: single Once your project is ready for production, replace the automatically generated domain with your own custom domain. Note that adding a domain disables the automatically generated URL for your Production environment only. -If you are an Enterprise or Elite customer and have a Grid or {{% names/dedicated-gen-3 %}} project, you can [customize the URLs for your preview environments](/domains/steps/custom-domains-preview-environments). +If you are an Enterprise or Elite customer and have a Grid or {{% names/dedicated-gen-3 %}} project, you can [customize the URLs for your non-production environments](/domains/steps/custom-non-production-domains). {{% names/dedicated-gen-2 %}} customers can also customize the domain for their Staging environment. ## Before you begin diff --git a/sites/platform/src/domains/steps/custom-domains-preview-environments.md b/sites/platform/src/domains/steps/custom-non-production-domains.md similarity index 66% rename from sites/platform/src/domains/steps/custom-domains-preview-environments.md rename to sites/platform/src/domains/steps/custom-non-production-domains.md index 13ab664fd0..56233af708 100644 --- a/sites/platform/src/domains/steps/custom-domains-preview-environments.md +++ b/sites/platform/src/domains/steps/custom-non-production-domains.md @@ -1,29 +1,29 @@ --- -title: Set up a custom domain on your preview environments -sidebarTitle: Preview environments +title: Set up a custom domain on your non-production environments +sidebarTitle: Non-production environments weight: 3 -description: Learn how to set up custom domains on your preview environments +description: Learn how to set up custom domains on your staging and development environments banner: type: tiered-feature --- {{< partial "progressive-rollout/body.md" >}} -[Preview environments](../../other/glossary.md#preview-environment) in your project can't use the custom domain -you have [set up on your production environment](../steps/_index.md).
-By default and for each preview environment, +When a custom domain is [set up on your production environment](../steps/_index.md), +it can't be used for the other, non-production environments in your project. + +Therefore, by default and for each non-production environment, {{< vendor/name >}} automatically replaces the custom production domain with an automatically generated URL. If you don't want to use these default URLs, -you can add a custom domain to each of your preview environments +you can add a custom domain to each of your non-production environments (`staging` or `development` environment types). -To do so, no need to modify your [routes configuration](../../define-routes/_index.md). -When you add a new custom domain for a preview environment, -just attach it to the custom production domain it replaces. +To do so, you don't need to modify your [routes configuration](../../define-routes/_index.md). +You just need to attach each new custom non-production domain to the custom production domain it replaces. If you have multiple custom production domains, -you need to select which one you're replacing. +you need to select which one you are replacing when you add a custom non-production domain. {{< note title="Example" >}} @@ -34,19 +34,19 @@ You want to add the `staging.example.com` custom domain to your staging environm To do so, you need to attach the new `staging.example.com` custom domain to its corresponding custom production domain `example.com`. -You can then access your staging environment through `staging.example.com`, +You can then access your staging environment through `staging.example.com` and still access your production environment through `example.com`. {{< /note >}} If you have multiple custom domains on your production environment, -when you add a custom domain for a preview environment, +when you create a custom non-production domain, you don't need to update your [routes configuration](../../define-routes/_index.md) either. -{{< vendor/name >}} automatically figures out the routing of your preview environment +{{< vendor/name >}} automatically figures out the routing of your non-production environment based on the following elements: - The custom production domains in your existing [routes configuration](../../define-routes/_index.md) -- The custom domains for preview environments attached to each of those custom production domains +- The custom non-production domains attached to each of those custom production domains ## Before you start @@ -63,13 +63,13 @@ You need: {{< /note >}} If you use a [Managed Fastly](../cdn/managed-fastly.md) CDN, - it needs to be configured to operate with custom domains for preview environments. + it needs to be configured to operate with custom non-production domains. For more information, [contact Support](https://console.platform.sh/-/users/~/tickets/open). - A production environment with at least one custom domain already set up -- At least one preview (staging or development) environment +- At least one non-production (staging or development) environment - Optional: The [{{< vendor/name >}} CLI](../../administration/cli/_index.md) (v4.8.0+) -To prevent abuse, by default you can add custom domains to up to 5 preview environments per project only. +To prevent abuse, by default you can add custom domains to up to 5 environments per project only. This limit doesn't include the production environment, and you can increase it without charge. To do so, [contact Support](/learn/overview/get-support.md). @@ -77,25 +77,25 @@ To do so, [contact Support](/learn/overview/get-support.md). {{< note >}} If you delete a custom production domain, -all of the attached custom domains for preview environments are deleted too. -You need to rebuild the affected preview environments for the deletion to be complete. +all of the attached custom non-production domains are deleted too. +You need to rebuild the affected non-production environments for the deletion to be complete. {{< /note >}} If you downgrade from an Elite or Enterprise plan to a Professional plan, -all of the custom domains set on preview environments are automatically removed. +all of the custom domains set on non-production environments are automatically removed. Downgrading your plan doesn't affect custom domains set on your production environments. -## Add a custom domain to a preview environment +## Add a custom domain to a non-production environment -To add a custom domain to a preview environment, follow these steps: +To add a custom domain to a non-production environment, follow these steps: {{< codetabs >}} +++ title=Using the CLI +++ -1. To get the target for your preview environment, +1. To get the target for your non-production environment, run the following command: ```bash @@ -103,12 +103,12 @@ title=Using the CLI ``` 2. [Configure your DNS provider](../steps/_index.md#3-configure-your-dns-provider). - In particular, make sure your DNS record points to the target of your preview environment. + In particular, make sure your DNS record points to the target of your non-production environment. {{< note >}} Using the target of your production environment to configure your DNS provider is technically possible, - but {{< vendor/name >}} recommends using the target of your preview environment as a best practice. + but {{< vendor/name >}} recommends using the target of your non-production environment as a best practice. {{< /note >}} @@ -123,29 +123,30 @@ title=Using the CLI title=In the Console +++ -1. Get the target for your preview environment.
- To do so, navigate to your preview environment and click **{{< icon settings >}} Settings**.
+1. Get the target for your non-production environment.
+ To do so, navigate to your non-production environment and click **{{< icon settings >}} Settings**.
Select the **Domains** tab.
In the **Configure your domain** section, copy the content of the **CNAME record** field.
Save it for later use at step 7. 2. Click **Add domain**. -3. Name the custom domain for your preview environment. +3. Enter a name for your custom non-production domain. -4. Attach the custom domain for your preview environment to the desired production custom domain. +4. If you have multiple production domains, + select the one you want to attach your custom non-production domain to. 5. Click **Add**. 6. Click **Okay**. 7. [Configure your DNS provider](../steps/_index.md#3-configure-your-dns-provider).
- In particular, make sure your DNS record points to the target of your preview environment. + In particular, make sure your DNS record points to the target of your non-production environment. {{< note >}} Using the target of your production environment to configure your DNS provider is technically possible, -but {{< vendor/name >}} recommends using the target of your preview environment as a best practice. +but {{< vendor/name >}} recommends using the target of your non-production environment as a best practice. {{< /note >}} @@ -153,7 +154,7 @@ but {{< vendor/name >}} recommends using the target of your preview environment {{< note >}} -You can’t update a custom domain when it's used on a preview environment. +You can’t update a custom non-production domain. You can only delete it and create a new one as a replacement. {{< /note >}} @@ -189,7 +190,7 @@ title=In the Console 2. Click **Add domain**. -3. Enter `mydev.com` as a name for the custom domain you want to add to `Dev`. +3. Enter `mydev.com` as a name for your custom non-production domain. 4. Select `mysite.com` as the production custom domain you want to attach `mydev.com` to. @@ -207,7 +208,7 @@ for you to add the `mydev.com` custom domain successfully. If the `Dev` environment is later removed, the `mydev.com` custom domain is removed too. -## List the custom domains of a preview environment +## List the custom domains of a non-production environment {{< codetabs >}} +++ @@ -225,13 +226,13 @@ Run a command similar to the following: title=In the Console +++ -1. Navigate to your preview environment and click **{{< icon settings >}} Settings**. +1. Navigate to your non-production environment and click **{{< icon settings >}} Settings**. 2. Select the **Domains** tab.
- All the custom domains for your preview environment are displayed. + All the custom domains for your non-production environment are displayed. {{< /codetabs >}} -## Get a specific custom domain used on a preview environment +## Get a specific custom non-production domain {{< codetabs >}} +++ @@ -249,14 +250,14 @@ Run a command similar to the following: title=In the Console +++ -1. Navigate to your preview environment and click **{{< icon settings >}} Settings**.
+1. Navigate to your non-production environment and click **{{< icon settings >}} Settings**.
2. Select the **Domains** tab.
All the custom domains for the selected environment are displayed. -3. Click **{{< icon "more" >}} More** on a custom domain used on a preview environment to see which actions you can perform on it. +3. Click **{{< icon "more" >}} More** on a specific custom non-production domain to see which actions you can perform on it. {{< /codetabs >}} -## Remove a custom domain from a preview environment +## Remove a custom domain from a non-production environment {{< codetabs >}} +++ @@ -274,10 +275,10 @@ Run a command similar to the following: title=In the Console +++ -1. Navigate to your preview environment and click **{{< icon settings >}} Settings**. +1. Navigate to your non-production environment and click **{{< icon settings >}} Settings**. 2. Select the **Domains** tab.
All the custom domains for the selected environment are displayed. -3. Click **{{< icon "more" >}} More** on the custom domain you want to delete. +3. Click **{{< icon "more" >}} More** on the custom non-production domain you want to delete. 4. Click **Delete**. 5. Click **Yes, delete**. diff --git a/sites/platform/src/domains/steps/tls.md b/sites/platform/src/domains/steps/tls.md index 967f10049a..a631ddd920 100644 --- a/sites/platform/src/domains/steps/tls.md +++ b/sites/platform/src/domains/steps/tls.md @@ -21,8 +21,8 @@ To avoid switching to a default certificate, make sure you replace your custom certificate with an updated one more than seven days before its expiration date. -Note that custom certificates aren't necessary for preview environments. -Wildcard certificates that cover all `*.platform.sh` domains, including preview environments, are automatically provided. +Note that custom certificates aren't necessary for development environments. +Wildcard certificates that cover all `*.platform.sh` domains, including development environments, are automatically provided. ### Add a custom certificate diff --git a/sites/platform/src/environments/_index.md b/sites/platform/src/environments/_index.md index cbf287e453..2451a5a2cb 100644 --- a/sites/platform/src/environments/_index.md +++ b/sites/platform/src/environments/_index.md @@ -158,7 +158,7 @@ Example Agile workflow: ### Naming conventions -You can organize and work with your preview environments in many different ways. +You can organize and work with your development environments in many different ways. It can help to introduce a convention for how you name and structure your environments. For each environment, choose a name that represents what the environment is for. @@ -191,14 +191,14 @@ Staging {{< partial "progressive-rollout/body.md" >}} -[Preview environments](../other/glossary.md#preview-environment) ([development type](../other/glossary.md#environment-type)) are often used for a limited time and then abandoned. +Development environments are often used for a limited time and then abandoned. To prevent unnecessary consumption of resources, -{{< vendor/name >}} automatically pauses preview environments that haven't been redeployed in 14 days. +{{< vendor/name >}} automatically pauses development and staging environments that haven't been redeployed in 14 days. {{< note >}} If you're on a development plan, -all your environments are preview environments that can be paused automatically. +all your environments are development environments that can be paused automatically. This includes your future production environment. To prevent your production environment from being paused automatically, [upgrade to a non-development plan](https://platform.sh/pricing/). diff --git a/sites/platform/src/environments/backup.md b/sites/platform/src/environments/backup.md index a62fdb67ab..a417169cff 100644 --- a/sites/platform/src/environments/backup.md +++ b/sites/platform/src/environments/backup.md @@ -65,7 +65,7 @@ For information on how long backups are retained, see the [data retention policy Backups for Dedicated environments have a [specific frequency](../dedicated-gen-2/overview/backups.md). -On Grid environments, preview environments can have up to 2 [manual backups](#create-a-manual-backup). +On Grid environments, non-Production environments can have up to 2 [manual backups](#create-a-manual-backup). The number of available backups for Production environments depends on your schedule. | Schedule | Manual backups | Automated backups | diff --git a/sites/platform/src/environments/http-access-control.md b/sites/platform/src/environments/http-access-control.md index 1051f0adad..185a800a19 100644 --- a/sites/platform/src/environments/http-access-control.md +++ b/sites/platform/src/environments/http-access-control.md @@ -5,7 +5,7 @@ keywords: - basic authentication --- -When developing your site, you might want to hide your preview environments from outside viewers. +When developing your site, you might want to hide your development environments from outside viewers. Or you may find you have performance issues from [excessive bot access](https://community.platform.sh/t/diagnosing-and-resolving-issues-with-excessive-bot-access/792). You can control access either with a username and password or by allowing/denying specific IP addresses or networks. This setting applies to the entire environment. diff --git a/sites/platform/src/environments/search-engine-visibility.md b/sites/platform/src/environments/search-engine-visibility.md index 0d1a08dc7c..0e4158d959 100644 --- a/sites/platform/src/environments/search-engine-visibility.md +++ b/sites/platform/src/environments/search-engine-visibility.md @@ -4,10 +4,10 @@ sidebarTitle: Set search engine visibility description: Learn how to change.a given environment's visbility to search engines. --- -When you have preview environments, +When you have development environments, you don't want search engines indexing them and diluting the SEO of your production site. -Search engine indexers are told to ignore all preview environments. +Search engine indexers are told to ignore all development environments. When you're ready to go live, give your production environment a [custom domain](../domains/steps/_index.md) and then set it to be visible to search engines. diff --git a/sites/platform/src/get-started/add-data/branch.md b/sites/platform/src/get-started/add-data/branch.md index 38d693a5f3..3bf9790ffb 100644 --- a/sites/platform/src/get-started/add-data/branch.md +++ b/sites/platform/src/get-started/add-data/branch.md @@ -7,9 +7,9 @@ description: Create a separate environment for development and see how it works. The next step in building out your app is adding a service. For comfortable development and testing, start with a separate branch for development. -## Create a preview environment +## Create a development environment -To develop without affecting production, you need a separate [preview environment](../../other/glossary.md#preview-environment). +To develop without affecting production, you need a separate environment. Create one in a terminal: ```bash @@ -58,7 +58,7 @@ You get a message saying the variable wasn't found. Differences such as this allow you to have different builds in different environments. This is useful for things such as connecting to different databases in development and production. -Now you have a preview environment and know how it works. +Now you have a development environment and know how it works. Next, add a service in that environment and then merge it. {{< get-started/next-button next="/get-started/add-data/merge.html" nextText="I'm ready to merge" >}} diff --git a/sites/platform/src/get-started/add-data/merge.md b/sites/platform/src/get-started/add-data/merge.md index ced6e5bae1..9577fa4966 100644 --- a/sites/platform/src/get-started/add-data/merge.md +++ b/sites/platform/src/get-started/add-data/merge.md @@ -5,7 +5,7 @@ description: Add a service and see how data works between branches. --- You have a separate environment with separate data. -Next, add a service to your preview environment. +Next, add a service to your development environment. ## Add a service @@ -138,7 +138,7 @@ To see how the data in parent environments can be inherited, follow these steps: {{% vendor/cli %}} sync data --environment dev ``` -4. Check the data in the preview environment +4. Check the data in the development environment ```bash {{% vendor/cli %}} sql --environment dev 'SELECT * FROM parent_data' @@ -146,7 +146,7 @@ To see how the data in parent environments can be inherited, follow these steps: You see the same table as in step 2. -So you can test your changes with confidence in your preview environments, knowing they work in production. +So you can test your changes with confidence in your development environments, knowing they work in production. But you don't have to worry about your tests affecting your production data. ## What's next diff --git a/sites/platform/src/guides/django/deploy/next-steps.md b/sites/platform/src/guides/django/deploy/next-steps.md index 316de06a8c..d6c55ab0a6 100644 --- a/sites/platform/src/guides/django/deploy/next-steps.md +++ b/sites/platform/src/guides/django/deploy/next-steps.md @@ -28,7 +28,7 @@ See how to configure [Python web servers](../../../languages/python/server.md). ## Sanitize data -By default, each [preview environment](../../../other/glossary.md#preview-environment) ([development type](../../../other/glossary.md#environment-type)) automatically inherits all data from its parent environment. +By default, each development environment automatically inherits all data from its parent environment. So a developer working on a small feature has access to production data, including personally identifiable information (PII). This workflow isn't always desirable or even acceptable based on your compliance requirements. diff --git a/sites/platform/src/guides/gatsby/headless/drupal.md b/sites/platform/src/guides/gatsby/headless/drupal.md index 057d69409e..4988fcfcca 100644 --- a/sites/platform/src/guides/gatsby/headless/drupal.md +++ b/sites/platform/src/guides/gatsby/headless/drupal.md @@ -81,6 +81,6 @@ With Gatsby now deployed and pulling content from a backend Drupal application, ### Live preview and incremental builds -If you replicate the `web.commands.start` block in Gatsby's `{{< vendor/configfile "app" >}}` file above, you can enable incremental builds on your projects. Once you save an update to a piece of Drupal content on a preview branch, Drupal places a request to a dedicated `/__refresh` endpoint on Gatsby. Since Gatsby is running a development server on this preview environment, this call causes Gatsby to retrieve content from Drupal once again, resulting in a near instantly updated article on the frontend. +If you replicate the `web.commands.start` block in Gatsby's `{{< vendor/configfile "app" >}}` file above, you can enable incremental builds on your projects. Once you save an update to a piece of Drupal content on a non-production branch, Drupal places a request to a dedicated `/__refresh` endpoint on Gatsby. Since Gatsby is running a development server on this non-production environment, this call causes Gatsby to retrieve content from Drupal once again, resulting in a near instantly updated article on the frontend. To see how to enable this feature, consult the [template's README](https://github.com/platformsh-templates/gatsby-drupal#user-content-enabling-gatsby-live-preview-manual-configuration). diff --git a/sites/platform/src/guides/symfony/environment-variables.md b/sites/platform/src/guides/symfony/environment-variables.md index 4493f98676..d7afc24622 100644 --- a/sites/platform/src/guides/symfony/environment-variables.md +++ b/sites/platform/src/guides/symfony/environment-variables.md @@ -28,11 +28,11 @@ about the app and its infrastructure. The Symfony integration exposes more environment variables: - `APP_ENV` is set to `prod` by default. - You can manually override this value for a preview environment + You can manually override this value for a development environment by setting the `SYMFONY_ENV` environment variable to `dev`, and remove it when done. - `APP_DEBUG` is set to `0` by default. - You can manually override this value for a preview environment + You can manually override this value for a development environment by setting the `SYMFONY_DEBUG` environment variable to `1`, and remove it when done. - `APP_SECRET` is set to the value of `PLATFORM_PROJECT_ENTROPY`, which is a random and unique value for all {{< vendor/name >}} projects. @@ -60,7 +60,7 @@ The Symfony integration exposes more environment variables: If you need to clear the build cache directory, run the `symfony cloud:project:clear-build-cache` command. - `SYMFONY_PROJECT_DEFAULT_ROUTE_URL` (only defined at **runtime**): The default endpoint serving your project. - Use this variable to avoid hard-coding domains that can be used to reach preview environments. + Use this variable to avoid hard-coding domains that can be used to reach non-production environments. Parts of the URL are also exposed as their own variables using the following syntax: `SYMFONY_PROJECT_DEFAULT_ROUTE_` followed by the name of the part (`SCHEME`, `DOMAIN`, `PORT`, and `PATH`). diff --git a/sites/platform/src/guides/symfony/faq.md b/sites/platform/src/guides/symfony/faq.md index 0f11aa1aca..4e8cef4a41 100644 --- a/sites/platform/src/guides/symfony/faq.md +++ b/sites/platform/src/guides/symfony/faq.md @@ -66,7 +66,7 @@ symfony logs all [access] 78.247.136.119 - - [14/Aug/2020:10:52:27 +0000] "GET / HTTP/1.1" 500 843 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Safari/537.36" ``` -If the error occurs on a preview environment, +If the error occurs on a non-production environment, or on the main environment of a non-production project, you can also enable Symfony's dev/debug mode to inspect the cause of the error: diff --git a/sites/platform/src/integrations/activity/reference.md b/sites/platform/src/integrations/activity/reference.md index dfd38ac33c..cf6008587f 100644 --- a/sites/platform/src/integrations/activity/reference.md +++ b/sites/platform/src/integrations/activity/reference.md @@ -290,7 +290,7 @@ Those queues include the following types of activities: Production activities are prioritized across all queues. When an activity for the production environment is triggered, it's placed at the top of the queue. -This makes it unlikely that activities on preview environments block activities for the production environment for long, +This makes it unlikely that activities on non-production environments block activities for the production environment for long, though there may be a temporary wait. ## Examples diff --git a/sites/platform/src/languages/nodejs/debug.md b/sites/platform/src/languages/nodejs/debug.md index 4a5d6ca171..3ab0de981a 100644 --- a/sites/platform/src/languages/nodejs/debug.md +++ b/sites/platform/src/languages/nodejs/debug.md @@ -9,7 +9,7 @@ Follow the steps below to debug a specific app. You can choose to debug in an environment deployed to {{< vendor/name >}} or with your app running locally but connected to deployed services. -In either case, make sure to debug in a preview environment. +In either case, make sure to debug in a non-production environment. {{% troubleshoot %}} diff --git a/sites/platform/src/languages/python/_index.md b/sites/platform/src/languages/python/_index.md index 97305b3ac3..b6f9c67e0d 100644 --- a/sites/platform/src/languages/python/_index.md +++ b/sites/platform/src/languages/python/_index.md @@ -223,7 +223,7 @@ markdownify=false ## Sanitizing data By default, data is inherited automatically by each child environment from its parent. -If you need to sanitize data in preview environments for compliance, +If you need to sanitize data in non-production environments for compliance, see how to [sanitize databases](../../development/sanitize-db/_index.md). ## Frameworks diff --git a/sites/platform/src/languages/ruby.md b/sites/platform/src/languages/ruby.md index d1374cddb0..d936572b87 100644 --- a/sites/platform/src/languages/ruby.md +++ b/sites/platform/src/languages/ruby.md @@ -32,7 +32,7 @@ A complete example is included at the end of this section. 2. Setup environment variables. - Rails runs by default on a preview environment. + Rails runs by default on a development environment. You can change the Rails/Bundler via those environment variables, some of which are defaults on {{< vendor/name >}}. diff --git a/sites/platform/src/learn/overview/build-deploy.md b/sites/platform/src/learn/overview/build-deploy.md index cfa21df18d..11c912503b 100644 --- a/sites/platform/src/learn/overview/build-deploy.md +++ b/sites/platform/src/learn/overview/build-deploy.md @@ -28,9 +28,9 @@ So each container is tied to a specific Git commit. If there are no new changes for a given container, the existing container can be reused. This saves you the time the build step would take. -This means the build is independent of the given environment and preview environments are perfect copies of production. +This means the build is independent of the given environment and development environments are perfect copies of production. If you use environment variables to set up different build configuration options for different environments, -your build step isn't reused and your preview environments may differ from production. +your build step isn't reused and your development environments may differ from production. You can't connect to services (like databases) during the build step. Once the app has gone through all of the build steps, it can connect to services in the deploy process. diff --git a/sites/platform/src/other/glossary.md b/sites/platform/src/other/glossary.md index 6a81c67e0d..9322733e32 100644 --- a/sites/platform/src/other/glossary.md +++ b/sites/platform/src/other/glossary.md @@ -62,7 +62,7 @@ Run: To define the environment type for the branch, include `--type `. -For example, to create the branch `develop` as a [preview environment](#preview-environment) ([development type](#environment-type)) from the branch `main`, run: +For example, to create the branch `develop` as a Development environment from the branch `main`, run: ```bash {{% vendor/cli %}} branch develop main --type development @@ -117,20 +117,6 @@ complete with code, data, and running services. Your production environment comes from the [default branch](../environments/_index.md#default-environment) and you can set up any other branch as a testing environment. -## Environment type - -{{< vendor/name >}} offers three environment types: - -- Your **production environment** is your live site. -- A **development environment** is an isolated environment where you can safely develop new features without affecting production. -- A **staging environment** has a similar configuration to your production environment (but usually with less resources for cost optimization). - It is useful to perform user acceptance testing in a production-like setting. - -The phrase "[preview environment](#preview-environment)" can apply to both a development or staging environment, -as it simply describes a non-production environment. - -Find out more about [user roles on each environment type](../administration/users.md#environment-type-roles). - ## Grid Grid environments are standard for Professional plans. @@ -180,13 +166,6 @@ A Platform as a Service is an end-to-end hosting solution that includes workflow tools, APIs, and other functionality above and beyond basic hosting. The best example is {{< vendor/name >}}(although we're a little biased). -## Preview environment - -A preview environment is a non-production environment you can use to develop and/or test changes without affecting production.
-A preview environment can either be a development environment or a staging environment. -Staging environments have an identical software configuration to your production hardware but reduced hardware specs. -They are useful to perform user acceptance testing. - ## Production plan A subscription level that allows you to host your production website diff --git a/sites/platform/src/security/backups.md b/sites/platform/src/security/backups.md index ad996cd3e2..073875ffa0 100644 --- a/sites/platform/src/security/backups.md +++ b/sites/platform/src/security/backups.md @@ -7,9 +7,9 @@ The frequency of backups varies based on the [backup schedule](../environments/b Retention is governed by the [data retention policy](./data-retention.md). This section details the recovery point objective (RPO) and recovery time objective (RTO) for each option. -## Preview environments +## Development environments -For preview environments, users can manage their own manual backup and restore functions. +For non-Production environments, users can manage their own manual backup and restore functions. See how to [back up](../environments/backup.md#create-a-manual-backup) and [restore](../environments/restore.md). **RPO**: User defined. diff --git a/themes/psh-docs/layouts/shortcodes/guides/gatsby/headless-plansize.md b/themes/psh-docs/layouts/shortcodes/guides/gatsby/headless-plansize.md index a2530520d8..fc2ca31b2b 100644 --- a/themes/psh-docs/layouts/shortcodes/guides/gatsby/headless-plansize.md +++ b/themes/psh-docs/layouts/shortcodes/guides/gatsby/headless-plansize.md @@ -3,6 +3,6 @@ This size gives the project enough resources for all of your containers as well as the memory necessary to actually pull content from {{ .Get "name" }} into Gatsby during its build. Keep in mind that the increased plan size applies only to your production environment, -and not to preview environments (which default to {{ partial "plans/default-dev-env-size" }}). +and not to development environments (which default to {{ partial "plans/default-dev-env-size" }}). As you continue to work with Gatsby and a backend headless CMS, -you may want to [upsize your preview environments](/administration/pricing.html#preview-environments). +you may want to [upsize your development environments](/administration/pricing.html#development-environments).