You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ Therefore, do not assume that an established WebSocket connection will remain op
62
62
## Move to Kubernetes
63
63
64
64
* Only [supported Mendix versions](https://docs.mendix.com/releasenotes/studio-pro/lts-mts/) are able to move to Kubernetes.
65
-
* 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.
65
+
* 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.
66
66
* If your model is using the [SAML module](https://marketplace.mendix.com/link/component/1174), these versions are compatible with Kubernetes:
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/environments-details.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,8 @@ In the **Application Status** section of the **General** tab, you can find the f
92
92
***Project ID** – the unique identifier of the app
93
93
***Environment ID** – the unique identifier of the environment
94
94
***Running Since** – the date the app was started, if it is running
95
-
***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
95
+
***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
96
+
***Subdomain Suffix** – the application's subdomain name
96
97
***URL** – the URL of the app
97
98
***Custom Domains** – any [custom domains](/developerportal/deploy/custom-domains/) of the app; to add a new domain, click **Add Custom Domain**
98
99
***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
103
104
104
105
#### Naming of Environments – Flexible Environments in Mendix Cloud {#naming}
105
106
106
-
If you are the app's [Technical Contact](/developerportal/general/app-roles/#technical-contact), you can rename the environments.
107
+
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.
107
108
108
-
To rename an environment, follow these steps:
109
-
110
-
1. Click **Change** next to the name of the environment.
111
-
2. Enter the new name, which must meet the following requirements:
112
-
* Consists of at least two characters.
113
-
* Consists of only alphanumeric characters and hyphens (`a-z`, `A-Z`, `0-9`, and `-`).
114
-
* Does not begin or end with a hyphen.
109
+
***Display Name requirements**:
110
+
* Must start and end with an alphanumeric or non-latin character
111
+
* Must contain two or more alphanumeric or non-latin characters and hyphens (–)
112
+
* Maximum of 200 characters are allowed
113
+
***Subdomain Suffix requirements**
114
+
* Consists of at least two characters
115
+
* Consists of only alphanumeric characters and hyphens (`a-z`, `A-Z`, `0-9`, and `-`)
116
+
* Does not begin or end with a hyphen
115
117
116
118
{{% alert color="info" %}}
117
-
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.
119
+
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.
118
120
{{% /alert %}}
119
121
120
122
### Deployment Package Details
@@ -139,7 +141,6 @@ It also includes the option to change your plan. For details, refer to [Changing
139
141
***Database Plan Space** – the storage capacity of the database
140
142
***Database Plan Memory** – the database's RAM size
141
143
***File Storage** – available size for storing blobs
142
-
***Backup Storage** – total size available for database backup files
143
144
***Multi-AZ Enabled** – a **Yes** or **No** value indicating whether multiple availability zones are enabled
0 commit comments