diff --git a/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md b/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md index f28a91270b2..642a771e23c 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md @@ -62,7 +62,7 @@ Therefore, do not assume that an established WebSocket connection will remain op ## Move to Kubernetes * Only [supported Mendix versions](https://docs.mendix.com/releasenotes/studio-pro/lts-mts/) are able to move to Kubernetes. -* The platform configures `CF_INSTANCE_INDEX=0` for 1 of the instances to define a leader instance and to make [Community Commons](/appstore/modules/community-commons-function-library/) function `GetCFInstanceIndex` partially backwards compatible. The leader instance will return `0`. All follower instances will return `-1`. We advise to stop using function `GetCFInstanceIndex` as it is Cloud Foundry specific. +* The platform configures `CF_INSTANCE_INDEX=0` for 1 of the instances to define a leader instance and to make [Community Commons](/appstore/modules/community-commons-function-library/) function `GetCFInstanceIndex` partially backwards compatible. The leader instance will return `0` while all follower instances will return `-1`. We advise stopping the use of the `GetCFInstanceIndex` function as it is specific to Cloud Foundry. * If your model is using the [SAML module](https://marketplace.mendix.com/link/component/1174), these versions are compatible with Kubernetes: * Mendix 9 – Version 3.6.19 and higher. * Mendix 10 – Version 4.1.0 and higher. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md b/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md index c84e217003e..60e38fa5306 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md @@ -92,7 +92,8 @@ In the **Application Status** section of the **General** tab, you can find the f * **Project ID** – the unique identifier of the app * **Environment ID** – the unique identifier of the environment * **Running Since** – the date the app was started, if it is running -* **Name** – the type of environment (Acceptance, Production, Test, or the name of a [flexible environment](/developerportal/deploy/mendix-cloud-deploy/#flexible-environments)); for more information, see the [Naming of Environments](#naming) section below +* **Display Name** – the type of environment (Acceptance, Production, Test, or the name of a [flexible environment](/developerportal/deploy/mendix-cloud-deploy/#flexible-environments)); for more information, see the [Naming of Environments](#naming) section below +* **Subdomain Suffix** – the application's subdomain name * **URL** – the URL of the app * **Custom Domains** – any [custom domains](/developerportal/deploy/custom-domains/) of the app; to add a new domain, click **Add Custom Domain** * **Studio Pro Target** – a **Yes** or **No** value indicating whether the environment is the designated deployment target from Studio Pro; for more information, see [Studio Pro Deployment Settings](/developerportal/deploy/studio-deployment-settings/) @@ -103,18 +104,19 @@ In the **Application Status** section of the **General** tab, you can find the f #### Naming of Environments – Flexible Environments in Mendix Cloud {#naming} -If you are the app's [Technical Contact](/developerportal/general/app-roles/#technical-contact), you can rename the environments. +If you are the app's [Technical Contact](/developerportal/general/app-roles/#technical-contact), you can rename the environment’s **Subdomain Suffix** or **Display Name** by clicking **Change** next to either of the options. -To rename an environment, follow these steps: - -1. Click **Change** next to the name of the environment. -2. Enter the new name, which must meet the following requirements: - * Consists of at least two characters. - * Consists of only alphanumeric characters and hyphens (`a-z`, `A-Z`, `0-9`, and `-`). - * Does not begin or end with a hyphen. +* **Display Name requirements**: + * Must start and end with an alphanumeric or non-latin character + * Must contain two or more alphanumeric or non-latin characters and hyphens (–) + * Maximum of 200 characters are allowed +* **Subdomain Suffix requirements** + * Consists of at least two characters + * Consists of only alphanumeric characters and hyphens (`a-z`, `A-Z`, `0-9`, and `-`) + * Does not begin or end with a hyphen {{% alert color="info" %}} -After you rename an environment, it may take up to 15 minutes before you can access an app via its URL. This is because the URL includes the name of the environment, and the old value needs to be removed from the DNS cache. It may take considerably longer for the change to be visible worldwide. +After you rename an environment’s subdomain suffix, it may take up to 15 minutes before you can access an app via its URL. This is because the URL includes the subdomain name of the environment, and the old value needs to be removed from the DNS cache. It may take considerably longer for the change to be visible worldwide. {{% /alert %}} ### Deployment Package Details @@ -139,7 +141,6 @@ It also includes the option to change your plan. For details, refer to [Changing * **Database Plan Space** – the storage capacity of the database * **Database Plan Memory** – the database's RAM size * **File Storage** – available size for storing blobs -* **Backup Storage** – total size available for database backup files * **Multi-AZ Enabled** – a **Yes** or **No** value indicating whether multiple availability zones are enabled #### Scaling {#scaling}