Skip to content

Commit 3161cf5

Browse files
Update new-app-node-request-template.md
Hi team, Please check the wording. The new node changes the options available, although it seems clear. We had a customer ask where to fill in for Cloud Foundry. :)
1 parent 1b82c4e commit 3161cf5

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/en/docs/support/new-app-node-request-template.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,9 @@ Fill in the required details for the new licensed app node on the [Request New A
2929

3030
By default, all developers in your organization can create node requests. You can limit this to Mendix Admins only by contacting your Customer Success Manager or requesting it via a support ticket.
3131

32-
If you have an app deployed to **SAP** and need a *Subscription Secret*, you need to choose the **Hosting type** *Virtual Private Cloud* and then, on the subsequent screen choose **Hosting type** *Cloud Foundry* and **Virtual Private Cloud Name** *SAP BTP*.
32+
**Mendix for Private Cloud** is only for deployments on Kubernetes using the Mendix Operator. For more information, please confirm [here](https://docs.mendix.com/developerportal/deploy/private-cloud/)
33+
For an app deployed on **Windows**, please choose Server-Based (Windows-Server) and collect the ServerID ( follow the [steps](https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/#windows-server))
34+
If you have an app deployed to **Docker**, **Cloud Foundry**, or **Kubernetes** ( without Mendix Operator), please choose **Container Based (Docker, Cloud Foundry, Kubernetes)** to get your licenses.
3335

3436
## Resizing an Existing Environment{#resize}
3537

0 commit comments

Comments
 (0)