diff --git a/content/en/docs/deployment/docker-deploy/_index.md b/content/en/docs/deployment/docker-deploy/_index.md deleted file mode 100644 index cb94ccfc424..00000000000 --- a/content/en/docs/deployment/docker-deploy/_index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: "Docker" -url: /developerportal/deploy/docker/ -weight: 60 -description: "Describes how to deploy your Mendix app to a Docker environment." -no_list: false -description_list: true ---- - -## Introduction - -This section describes how to deploy your Mendix app to a Docker environment. - -## Docker Deployment Options - -Mendix offers two options for Docker deployments: Portable App Distribution or the Docker Buildpack. - -### Portable App Distribution - -[Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/) allows users to generate their portable app with a single MxBuild command. It requires fewer manual steps than the Docker Buildpack, simpler environment configuration, and no `rootfs` preparation. Running Portable App Distribution can take as little as 3-6 minutes (the time may vary based on the application's size and complexity). - -### Docker Buildpack - -The Docker Buildpack offers custom `rootfs` configuration, but requires multiple build steps, a more complex setup process, and a longer total build time (at least 14-25 minutes). - -## Documents in This Section diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index c03975d42b2..27591c1caca 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -109,7 +109,7 @@ You will need to add the license credentials and configure the license in the Me ### Cloud Foundry{#cloudfoundry} -The following steps describe activating the license for deployments using the Cloud Foundry Buildpack. If you are deploying using Portable App Distribution, follow the steps in the [Portable App Distribution](#portableappdistribution) section below. +The following steps describe activating the license for deployments using the Cloud Foundry Buildpack. If you are deploying using Mendix Portable Runtime, follow the steps in the [Mendix Portable Runtime](#portableappdistribution) section below. To activate a license on your app running on Cloud Foundry, you need the license credentials provided by Mendix Support. @@ -124,7 +124,7 @@ Then restart the app so that the environment variables are read, and the license ### Docker -The following steps describe activating the license for deployments using the Docker Buildpack. If you are deploying using Portable App Distribution, follow the steps in the [Portable App Distribution](#portableappdistribution) section below. +The following steps describe activating the license for deployments using the Docker Buildpack. If you are deploying using Mendix Portable Runtime, follow the steps in the [Mendix Portable Runtime](#portableappdistribution) section below. To activate a license on your app running in a Docker container, you need the license credentials provided by Mendix Support. @@ -156,7 +156,7 @@ For full instructions on how to do this, see [Activate a Mendix License on Micro ### Unix-Like Server -The following steps describe activating the license for deployments using the M2EE tool. If you are deploying using Portable App Distribution, follow the steps in the [Portable App Distribution](#portableappdistribution) section below. +The following steps describe activating the license for deployments using the M2EE tool. If you are deploying using Mendix Portable Runtime, follow the steps in the [Mendix Portable Runtime](#portableappdistribution) section below. To license a Mendix app on Linux or another Unix-like operating system, follow these steps: @@ -167,9 +167,9 @@ To license a Mendix app on Linux or another Unix-like operating system, follow t For more instructions on how to do this, see [Linux Deployment](/developerportal/deploy/linux/). -### Portable App Distribution{#portableappdistribution} +### Mendix Portable Runtime{#portableappdistribution} -To activate the license for a Mendix app using Portable App Distribution on Docker, Cloud Foundry, or Unix-like servers, follow these steps: +To activate the license for a Mendix app using Mendix Portable Runtime on Docker, Cloud Foundry, or Unix-like servers, follow these steps: 1. Open the `$ConfigName.conf` in `etc/configurations`. 2. Add the `LicenseID` and `LicenseKey` to your runtime configuration: diff --git a/content/en/docs/deployment/on-premises-design/buildpacks/_index.md b/content/en/docs/deployment/on-premises-design/buildpacks/_index.md new file mode 100644 index 00000000000..17ab69b04c2 --- /dev/null +++ b/content/en/docs/deployment/on-premises-design/buildpacks/_index.md @@ -0,0 +1,16 @@ +--- +title: "Buildpacks" +url: /developerportal/deploy/buildpacks/ +weight: 60 +description: "Describes how to deploy your Mendix app to a Docker environment." +no_list: false +description_list: true +aliases: + - /developerportal/deploy/docker/ +--- + +## Introduction + +This section describes how to deploy your Mendix app with a buildpack. This is an optional deployment mechanism offered for customers who require this option. For the standard Mendix deployment mechanism, see [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/). + +## Documents in This Section diff --git a/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy.md b/content/en/docs/deployment/on-premises-design/buildpacks/cloud-foundry-deploy.md similarity index 98% rename from content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy.md rename to content/en/docs/deployment/on-premises-design/buildpacks/cloud-foundry-deploy.md index 5642e0a4bbf..ff4fce6802b 100644 --- a/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy.md +++ b/content/en/docs/deployment/on-premises-design/buildpacks/cloud-foundry-deploy.md @@ -22,7 +22,7 @@ aliases: ## Introduction {{% alert color="warning" %}} -Cloud Foundry buildpack deployment from Studio Pro is deprecated in version 10 and removed in version 11. Consider using the [Portable App Distribution for Cloud Foundry](/developerportal/deploy/cloud-foundry-pad/) option instead. +Cloud Foundry buildpack deployment from Studio Pro is deprecated in version 10 and removed in version 11. Consider using the [Mendix Portable Runtime for Cloud Foundry](/developerportal/deploy/cloud-foundry-pad/) option instead. The following documentation is provided for reference purposes only. {{% /alert %}} diff --git a/content/en/docs/deployment/docker-deploy/docker-buildpack.md b/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md similarity index 99% rename from content/en/docs/deployment/docker-deploy/docker-buildpack.md rename to content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md index 1015d62c22b..de2093d4368 100644 --- a/content/en/docs/deployment/docker-deploy/docker-buildpack.md +++ b/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md @@ -1,7 +1,7 @@ --- title: "Docker Buildpack" url: /developerportal/deploy/docker-deploy/ -weight: 60 +weight: 20 description: "Describes how to deploy using a Docker image using a Docker Buildpack." #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. --- diff --git a/content/en/docs/deployment/on-premises-design/cloud-foundry/_index.md b/content/en/docs/deployment/on-premises-design/cloud-foundry/_index.md deleted file mode 100644 index 4404136188c..00000000000 --- a/content/en/docs/deployment/on-premises-design/cloud-foundry/_index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "Cloud Foundry" -url: /developerportal/deploy/cloud-foundry/ -weight: 50 -no_list: false -description_list: true ---- - -## Introduction - -This section describes how to deploy your Mendix app to an on-premise Cloud Foundry environment. - -## Documents in This Section diff --git a/content/en/docs/deployment/on-premises-design/linux/linux.md b/content/en/docs/deployment/on-premises-design/linux/linux.md index 3ce1b41000c..b2edbc3d1dc 100644 --- a/content/en/docs/deployment/on-premises-design/linux/linux.md +++ b/content/en/docs/deployment/on-premises-design/linux/linux.md @@ -7,7 +7,7 @@ aliases: - /developerportal/deploy/unix-like/ --- -{{% alert color="warning" %}} Linux deployment is only supported on Debian 10 (buster) for the [Mendix Runtime version 9, 10, and 11](/releasenotes/studio-pro/lts-mts/). We will not add support for any other versions of the Mendix Runtime. Consider using the [Portable App Distribution for Linux](/developerportal/deploy/linux-pad/) option instead. {{% /alert %}} +{{% alert color="warning" %}} Linux deployment is only supported on Debian 10 (buster) for the [Mendix Runtime version 9, 10, and 11](/releasenotes/studio-pro/lts-mts/). We will not add support for any other versions of the Mendix Runtime. Consider using the [Mendix Portable Runtime for Linux](/developerportal/deploy/linux-pad/) option instead. {{% /alert %}} ## Introduction diff --git a/content/en/docs/deployment/general/pad/_index.md b/content/en/docs/deployment/pad/_index.md similarity index 58% rename from content/en/docs/deployment/general/pad/_index.md rename to content/en/docs/deployment/pad/_index.md index 337cf9b94be..17a3cda7955 100644 --- a/content/en/docs/deployment/general/pad/_index.md +++ b/content/en/docs/deployment/pad/_index.md @@ -1,49 +1,46 @@ --- -title: "Portable App Distribution" +title: "Mendix Portable Runtime" url: /developerportal/deploy/portable-app-distribution-deploy/ weight: 15 -description: "Describes the Portable App Distribution deployment method for Mendix apps." +description: "Describes the Mendix Portable Runtime deployment method for Mendix apps." no_list: false description_list: true -beta: true --- -{{% alert color="warning" %}} This feature is in beta. For more information, see [Release Status](/releasenotes/release-status/). {{% /alert %}} - ## Introduction -Portable App Distribution provides a flexible and straightforward method for isolated server-based deployments. By enabling customers to generate a bundled artifact packaged as a .zip file and run it directly, Portable App Distribution simplifies the deployment process. +Mendix Portable Runtime (previously called Portable App Distribution) provides a flexible and straightforward method for isolated server-based deployments. By enabling customers to generate a bundled artifact packaged as a .zip file and run it directly, Mendix Portable Runtime simplifies the deployment process. ## Benefits -Portable App Distribution offers the following benefits: +Mendix Portable Runtime offers the following benefits: * Simplified deployment - Portable apps eliminate complex installation procedures, making it easier and faster to get software up and running across different machines. This reduces setup time and potential configuration errors. * Enhanced consistency - By bundling all dependencies, portable apps ensure a consistent operating environment for the application, regardless of the underlying system configuration. * Improved mobility and flexibility - Teams can easily move applications between workstations, virtual machines, or even cloud instances without the need for reinstallation, fostering greater agility in project work. * Reduced system impact - Portable apps often run in isolated environments, which can help prevent conflicts with other installed software and maintain system stability. * Streamlined updates - Managing updates can be more straightforward, as new versions of a portable application can often be deployed by simply replacing the package. -* Layered configuration - Portable App Distribution supports defining base configurations that can be extended with environment-specific or deployment-type-specific entries (for example, distinct configurations for development, testing, or production environments). +* Layered configuration - Mendix Portable Runtime supports defining base configurations that can be extended with environment-specific or deployment-type-specific entries (for example, distinct configurations for development, testing, or production environments). ## Licensing -You can test Portable App Distribution on a [Free App](/developerportal/deploy/mendix-cloud-deploy/#free-app). For more information about Free Apps and their limitations, as well as licensing apps outside of the Mendix Cloud, see [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). +You can test Mendix Portable Runtime on a [Free App](/developerportal/deploy/mendix-cloud-deploy/#free-app). For more information about Free Apps and their limitations, as well as licensing apps outside of the Mendix Cloud, see [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). -To license a Mendix app on the Portable App Distribution, add it to your configuration. For more information, see [Obtaining a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#get-license). +To license a Mendix app on the Mendix Portable Runtime, add it to your configuration. For more information, see [Obtaining a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#get-license). ## Prerequisites -The Portable App Distribution functionality is available in Mendix Studio Pro versions 10.24.19 LTS, 11.9, 11.6.5 MTS, and above. The functionality will be enabled for more Studio Pro versions in future releases. +The Mendix Portable Runtime functionality is available in Mendix Studio Pro versions 10.24.19 LTS, 11.9, 11.6.5 MTS, and above. The functionality will be enabled for more Studio Pro versions in future releases. You must also ensure that you have the supported version of [Java Runtime Environment](/refguide/system-requirements/#java). -## Creating a Portable App Distribution File +## Creating a Mendix Portable Runtime File In most production environments, deployment packages are created by using the [Mx-Build](/refguide/mxbuild/) command-line tool. However, you can also [manually create a deployment package](/refguide/create-deployment-package-dialog/) if required, for example, for a local test deployment. ## Deploying Your App -After you create the Portable App Distribution file, deploy it to your environment. +After you create the Mendix Portable Runtime file, deploy it to your environment. ### Deploying Locally @@ -72,8 +69,8 @@ On Linux, if the ZIP was extracted on Windows, the +x flag is not preserved. Win For more information about deploying to a self-hosted environment, refer to the following topics: -* [Portable App Distribution for Docker](/developerportal/deploy/docker-deploy-pad/) -* [Portable App Distribution for Linux](/developerportal/deploy/linux-pad/) -* [Portable App Distribution for Cloud Foundry](/developerportal/deploy/cloud-foundry-pad/) +* [Mendix Portable Runtime for Docker](/developerportal/deploy/docker-deploy-pad/) +* [Mendix Portable Runtime for Linux](/developerportal/deploy/linux-pad/) +* [Mendix Portable Runtime for Cloud Foundry](/developerportal/deploy/cloud-foundry-pad/) ## Read More diff --git a/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md b/content/en/docs/deployment/pad/cloud-foundry-deploy-pad.md similarity index 74% rename from content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md rename to content/en/docs/deployment/pad/cloud-foundry-deploy-pad.md index 5b056c0334b..379dcda39b2 100644 --- a/content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md +++ b/content/en/docs/deployment/pad/cloud-foundry-deploy-pad.md @@ -1,8 +1,8 @@ --- -title: "Portable App Distribution on Cloud Foundry" +title: "Reference Guide for Cloud Foundry Deployments" url: /developerportal/deploy/cloud-foundry-pad/ -weight: 20 -description: "Describes how to deploy to a Cloud Foundry environment by using Portable App Distribution." +weight: 70 +description: "Describes how to deploy to a Cloud Foundry environment by using Mendix Portable Runtime." --- ## Introduction @@ -12,26 +12,26 @@ Cloud Foundry is a platform-as-a-service (PaaS) that automates the deployment, s This documentation provides guidance on understanding Cloud Foundry on-premise deployments and serves as a helpful reference rather than official implementation support. {{% alert color="info" %}} -Unlike the Cloud Foundry Buildpack deployment where Mendix provides full end-to-end tooling support, the Portable App Distribution approach only requires Java to run, with Mendix's support strictly limited to the Portable App Distribution package itself. All implementation, configuration, and deployment activities, including Cloud Foundry deployment, remain the sole responsibility of the customer. +Unlike the Cloud Foundry Buildpack deployment where Mendix provides full end-to-end tooling support, the Mendix Portable Runtime approach only requires Java to run, with Mendix's support strictly limited to the Mendix Portable Runtime package itself. All implementation, configuration, and deployment activities, including Cloud Foundry deployment, remain the sole responsibility of the customer. For information about the scope of support, see [Support for Different Deployment Strategies](/support/deployment-strategy-support/). {{% /alert %}} ## Prerequisites -To deploy your app to an on-premises Cloud Foundry configuration using [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/), ensure that you fulfill the following prerequisites: +To deploy your app to an on-premises Cloud Foundry configuration using [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/), ensure that you fulfill the following prerequisites: * You have access to the Cloud Foundry organization and space where the application is deployed. * You have access to the database configuration from the database service. * You have access to binding other required Cloud Foundry services. * The Cloud Foundry CLI is installed. -* You have generated the [Portable App Distribution .zip file](/developerportal/deploy/portable-app-distribution-deploy/). +* You have generated the [Mendix Portable Runtime .zip file](/developerportal/deploy/portable-app-distribution-deploy/). -## Deploying an App with Portable App Distribution +## Deploying an App with Mendix Portable Runtime To deploy your app to Cloud Foundry, perform the following steps: 1. Log in to Cloud Foundry, and then access the organization and space where the application is deployed. -2. Save the [Portable App Distribution .zip file](/developerportal/deploy/portable-app-distribution-deploy/) to an accessible location. +2. Save the [Mendix Portable Runtime .zip file](/developerportal/deploy/portable-app-distribution-deploy/) to an accessible location. 3. Create a *manifest.yml* file in the root directory of your app. By default, the `cf push` command uses the *manifest.yml* file in the app directory. To specify a different location for the manifest, you must pass its local path to the `-f` flag when you run `cf push`. diff --git a/content/en/docs/deployment/docker-deploy/docker-monitoring.md b/content/en/docs/deployment/pad/docker-monitoring.md similarity index 99% rename from content/en/docs/deployment/docker-deploy/docker-monitoring.md rename to content/en/docs/deployment/pad/docker-monitoring.md index 0ce488e3800..ae53a6d97c8 100644 --- a/content/en/docs/deployment/docker-deploy/docker-monitoring.md +++ b/content/en/docs/deployment/pad/docker-monitoring.md @@ -1,7 +1,7 @@ --- title: "Monitoring Tools in Docker" url: /developerportal/deploy/docker-monitoring/ -weight: 30 +weight: 50 description: "Describes the available monitoring tools for Docker deployments of Mendix." --- diff --git a/content/en/docs/deployment/docker-deploy/docker-pad.md b/content/en/docs/deployment/pad/docker-pad.md similarity index 82% rename from content/en/docs/deployment/docker-deploy/docker-pad.md rename to content/en/docs/deployment/pad/docker-pad.md index 227bbc5afa7..eb945b3d02b 100644 --- a/content/en/docs/deployment/docker-deploy/docker-pad.md +++ b/content/en/docs/deployment/pad/docker-pad.md @@ -1,13 +1,13 @@ --- -title: "Portable App Distribution for Docker" +title: "Best Practices for Docker Deployment" url: /developerportal/deploy/docker-deploy-pad/ -weight: 20 -description: "Describes how to deploy using a Docker image by using Portable App Distribution." +weight: 40 +description: "Describes how to deploy using a Docker image by using Mendix Portable Runtime." --- ## Introduction -This guide provides a walkthrough for deploying your Mendix application using [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/) with Docker. This approach is particularly useful for containerized environments, and can significantly ease your CI/CD setup. +This guide provides a walkthrough for deploying your Mendix application using [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/) with Docker. This approach is particularly useful for containerized environments, and can significantly ease your CI/CD setup. {{% alert color="info" %}} This document is not an official Mendix implementation, or a substitute for recommended production deployment strategies. For more features, such as app management or governance, we suggest using [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) or [Mendix on Azure](/developerportal/deploy/mendix-on-azure/), which offer a structured, tested experience with cloud infrastructure. @@ -15,13 +15,13 @@ This document is not an official Mendix implementation, or a substitute for reco For information about the scope of support, see [Support for Different Deployment Strategies](/support/deployment-strategy-support/). {{% /alert %}} -## Benefits of Portable App Distribution +## Benefits of Mendix Portable Runtime -Portable App Distribution revolutionizes the way in which Mendix applications are packaged and delivered. This innovative approach bundles your application code with all its necessary dependencies into a single, self-contained, and runnable artifact. This greatly simplifies the deployment of Mendix applications, whether you are targeting on-premise infrastructure or modern containerized environments like Docker, making the entire process more efficient and seamless. +Mendix Portable Runtime revolutionizes the way in which Mendix applications are packaged and delivered. This innovative approach bundles your application code with all its necessary dependencies into a single, self-contained, and runnable artifact. This greatly simplifies the deployment of Mendix applications, whether you are targeting on-premise infrastructure or modern containerized environments like Docker, making the entire process more efficient and seamless. -The ability to generate a Portable App Distribution with a single build command means that creating a Docker-ready artifact becomes a streamlined process, making the overall integration into existing Docker-based CI/CD pipelines more efficient and less prone to errors. +The ability to generate a Mendix Portable Runtime with a single build command means that creating a Docker-ready artifact becomes a streamlined process, making the overall integration into existing Docker-based CI/CD pipelines more efficient and less prone to errors. -The Portable App Distribution feature allows you to package and deploy Mendix apps without relying on the Mendix Cloud or a Mendix Operator. This is particularly useful for the following use cases: +The Mendix Portable Runtime feature allows you to package and deploy Mendix apps without relying on the Mendix Cloud or a Mendix Operator. This is particularly useful for the following use cases: * Air-gapped environments where internet access is restricted or unavailable * Private cloud deployments where you manage your own infrastructure @@ -29,7 +29,7 @@ The Portable App Distribution feature allows you to package and deploy Mendix ap Docker provides a consistent and reproducible environment for running Mendix apps, making it ideal for cloud-native and containerized deployments. -Portable App Distribution offers a more agile, user-centric, and efficient deployment ecosystem, empowering customers with greater control over their Docker deployments and simplifying the internal deployment processes. +Mendix Portable Runtime offers a more agile, user-centric, and efficient deployment ecosystem, empowering customers with greater control over their Docker deployments and simplifying the internal deployment processes. ## Prerequisites @@ -40,13 +40,13 @@ Before you begin, ensure you have the following: * Docker installed on your system (for building and running Docker images) * Access to a container registry (for pushing and pulling Docker images) -## Deploying an App with Portable App Distribution +## Deploying an App with Mendix Portable Runtime -The Portable App Distribution feature in Mendix Studio Pro provides you with the necessary application files to build a Docker image. It packages your Mendix application as a self-contained distribution, ready for integration into your Docker environment. +The Mendix Portable Runtime feature in Mendix Studio Pro provides you with the necessary application files to build a Docker image. It packages your Mendix application as a self-contained distribution, ready for integration into your Docker environment. -To deploy your app to Docker, you must create a Portable App Distribution Package, build a Docker image, and then deploy the Docker image (including optionally pushing it to a container registry). For more information, refer to the sections below. +To deploy your app to Docker, you must create a Mendix Portable Runtime Package, build a Docker image, and then deploy the Docker image (including optionally pushing it to a container registry). For more information, refer to the sections below. -### Creating a Portable App Distribution Package +### Creating a Mendix Portable Runtime Package To create a Portable Package from your Mendix app, perform the following steps: @@ -57,7 +57,7 @@ To create a Portable Package from your Mendix app, perform the following steps: The Portable Package is saved to the following location: `/releases/.zip`. -For more information about Portable Packages, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/). Files included in the Portable Package are the core of your Mendix application and are ready to be included in a Docker image. +For more information about Portable Packages, see [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/). Files included in the Portable Package are the core of your Mendix application and are ready to be included in a Docker image. ### Building a Docker Image @@ -94,7 +94,7 @@ To build a Docker image from the Portable Package, perform the following steps: CMD ["./bin/start", "etc/Default"] ``` - You must create this Dockerfile yourself and place it alongside the application files generated by the Portable App Distribution. The `COPY` commands in the example above assume that the `app`, `bin`, `etc`, and `lib` directories are in the same location as your Dockerfile. + You must create this Dockerfile yourself and place it alongside the application files generated by the Mendix Portable Runtime. The `COPY` commands in the example above assume that the `app`, `bin`, `etc`, and `lib` directories are in the same location as your Dockerfile. 3. Build the Docker image by using the following command: `docker build -t : -f build/docker/Dockerfile`, where: @@ -116,7 +116,7 @@ Once the Docker image is available in your container registry, you can deploy it 1. Pull the Docker image from your container registry by running the following command: `docker pull /:`, replacing ``, ``, and `` with the appropriate values for your Docker image. 2. Optional: Configure the container. - The Portable App Distribution container can be configured to suit your deployment environment and requirements. You can do this in the `etc` [configuration folder](/developerportal/deploy/portable-apps-distribution/reference/#folder-structure). You can also apply the configuration through environment variables or a configuration file, giving you flexibility depending on your setup and preferences. Both approaches support the same set of runtime settings, so you can choose whichever method best fits your workflow. + The Mendix Portable Runtime container can be configured to suit your deployment environment and requirements. You can do this in the `etc` [configuration folder](/developerportal/deploy/portable-apps-distribution/reference/#folder-structure). You can also apply the configuration through environment variables or a configuration file, giving you flexibility depending on your setup and preferences. Both approaches support the same set of runtime settings, so you can choose whichever method best fits your workflow. For more information, see the [Environment Variables](#env-variables) and [Configuration File](#config-file) sections below. @@ -134,7 +134,7 @@ You can view your running Mendix application at `localhost:8080`. To stop the ap For more complex setups involving multiple Docker containers, or for simpler local testing purposes, you can use Docker Compose. It allows you to define and run multi-container Docker applications. -The following is an example of a *docker-compose.yaml* file that sets up your Mendix application with an HSQLDB for local testing. This example assumes you have the Portable App Distribution files (`app`, `bin`, `etc`, `lib`) in a parent directory relative to your *docker-compose.yaml* file. +The following is an example of a *docker-compose.yaml* file that sets up your Mendix application with an HSQLDB for local testing. This example assumes you have the Mendix Portable Runtime files (`app`, `bin`, `etc`, `lib`) in a parent directory relative to your *docker-compose.yaml* file. ```yaml # This file provides an example on how to start the runtime with HSQLDB. diff --git a/content/en/docs/deployment/docker-deploy/kubernetes-pad.md b/content/en/docs/deployment/pad/kubernetes-pad.md similarity index 85% rename from content/en/docs/deployment/docker-deploy/kubernetes-pad.md rename to content/en/docs/deployment/pad/kubernetes-pad.md index d9167f4c4ab..6ed610b3be3 100644 --- a/content/en/docs/deployment/docker-deploy/kubernetes-pad.md +++ b/content/en/docs/deployment/pad/kubernetes-pad.md @@ -1,13 +1,13 @@ --- -title: "Portable App Distribution for Kubernetes" +title: "Mendix Portable Runtime for Kubernetes" url: /developerportal/deploy/docker-deploy-k8s/ -weight: 20 -description: "Describes how to use Portable App Distribution to deploy on Kubernetes without installing the Mendix Operator." +weight: 60 +description: "Describes how to use Mendix Portable Runtime to deploy on Kubernetes without installing the Mendix Operator." --- ## Introduction -This guide provides a walkthrough for deploying your Mendix application using [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/) with Kubernetes, but without relying on the Mendix Operator. This is particularly useful for air-gapped environments, private cloud deployments, or scenarios where you need full control over the deployment process. +This guide provides a walkthrough for deploying your Mendix application using [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/) with Kubernetes, but without relying on the Mendix Operator. This is particularly useful for air-gapped environments, private cloud deployments, or scenarios where you need full control over the deployment process. {{% alert color="info" %}} This document is not an official Mendix implementation, or a substitute for recommended production deployment strategies. For more features, such as app management or governance, we suggest using [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) or [Mendix on Azure](/developerportal/deploy/mendix-on-azure/), which offer a structured, tested experience with cloud infrastructure. @@ -15,13 +15,13 @@ This document is not an official Mendix implementation, or a substitute for reco For information about the scope of support, see [Support for Different Deployment Strategies](/support/deployment-strategy-support/). {{% /alert %}} -## Benefits of Portable App Distribution +## Benefits of Mendix Portable Runtime -Portable App Distribution revolutionizes the way in which Mendix applications are packaged and delivered. This innovative approach bundles your application code with all its necessary dependencies into a single, self-contained, and runnable artifact. This greatly simplifies the deployment of Mendix applications, whether you are targeting on-premise infrastructure or modern containerized environments like Docker, making the entire process more efficient and seamless. +Mendix Portable Runtime revolutionizes the way in which Mendix applications are packaged and delivered. This innovative approach bundles your application code with all its necessary dependencies into a single, self-contained, and runnable artifact. This greatly simplifies the deployment of Mendix applications, whether you are targeting on-premise infrastructure or modern containerized environments like Docker, making the entire process more efficient and seamless. -The ability to generate a Portable App Distribution with a single build command means that creating a Docker-ready artifact becomes a streamlined process, making the overall integration into existing Docker-based CI/CD pipelines more efficient and less prone to errors. +The ability to generate a Mendix Portable Runtime with a single build command means that creating a Docker-ready artifact becomes a streamlined process, making the overall integration into existing Docker-based CI/CD pipelines more efficient and less prone to errors. -The Portable App Distribution feature allows you to package and deploy Mendix apps without relying on the Mendix Cloud or a Mendix Operator. This is particularly useful for the following use cases: +The Mendix Portable Runtime feature allows you to package and deploy Mendix apps without relying on the Mendix Cloud or a Mendix Operator. This is particularly useful for the following use cases: * Air-gapped environments where internet access is restricted or unavailable * Private cloud deployments where you manage your own infrastructure @@ -29,7 +29,7 @@ The Portable App Distribution feature allows you to package and deploy Mendix ap Docker provides a consistent and reproducible environment for running Mendix apps, making it ideal for cloud-native and containerized deployments. -Portable App Distribution offers a more agile, user-centric, and efficient deployment ecosystem, empowering customers with greater control over their Docker deployments and simplifying the internal deployment processes. +Mendix Portable Runtime offers a more agile, user-centric, and efficient deployment ecosystem, empowering customers with greater control over their Docker deployments and simplifying the internal deployment processes. ## Prerequisites @@ -41,11 +41,11 @@ Before you begin, ensure you have the following: * Kubernetes cluster (if deploying to Kubernetes) * `kubectl` configured to connect to your Kubernetes cluster -## Deploying an App with Portable App Distribution +## Deploying an App with Mendix Portable Runtime -The Portable App Distribution feature in Mendix Studio Pro provides you with the necessary application files to build a Docker image. It packages your Mendix application as a self-contained distribution, ready for integration into your Docker environment. +The Mendix Portable Runtime feature in Mendix Studio Pro provides you with the necessary application files to build a Docker image. It packages your Mendix application as a self-contained distribution, ready for integration into your Docker environment. -To deploy your app to Docker, you must [create a Portable App Distribution Package](/developerportal/deploy/portable-app-distribution-deploy/#creating-a-portable-app-distribution-file), build a Docker image, and then deploy the Docker image (including pushing it to a container registry). For more information, refer to the sections below. +To deploy your app to Docker, you must [create a Mendix Portable Runtime Package](/developerportal/deploy/portable-app-distribution-deploy/#creating-a-portable-app-distribution-file), build a Docker image, and then deploy the Docker image (including pushing it to a container registry). For more information, refer to the sections below. ### Building a Docker Image diff --git a/content/en/docs/deployment/on-premises-design/linux/linux-pad.md b/content/en/docs/deployment/pad/linux-pad.md similarity index 77% rename from content/en/docs/deployment/on-premises-design/linux/linux-pad.md rename to content/en/docs/deployment/pad/linux-pad.md index 345e30dcbb9..f70f080f2f3 100644 --- a/content/en/docs/deployment/on-premises-design/linux/linux-pad.md +++ b/content/en/docs/deployment/pad/linux-pad.md @@ -1,28 +1,28 @@ --- -title: "Portable App Distribution on Linux" +title: "Reference Guide for Linux Deployments" url: /developerportal/deploy/linux-pad/ -description: "How to install and configure Mendix on a Linux system using Portable App Distribution." -weight: 20 +description: "How to install and configure Mendix on a Linux system using Mendix Portable Runtime." +weight: 80 --- ## Introduction -Portable App Distribution refers to packaging applications in a self-contained format that includes all necessary dependencies, allowing them to run on various Linux systems without requiring traditional installation. +Mendix Portable Runtime refers to packaging applications in a self-contained format that includes all necessary dependencies, allowing them to run on various Linux systems without requiring traditional installation. -This documentation provides guidance for deploying Portable App Distribution in a Linux environment and serves as a helpful reference rather than official implementation support. +This documentation provides guidance for deploying Mendix Portable Runtime in a Linux environment and serves as a helpful reference rather than official implementation support. {{% alert color="info" %}} -Unlike the M2EE-based deployment, where Mendix provides full end-to-end tooling support, the Portable App Distribution approach only requires Java to run, with Mendix's support strictly limited to the Portable App Distribution package itself. All implementation, configuration, and deployment activities, including Linux deployment, remain the customer's sole responsibility. +Unlike the M2EE-based deployment, where Mendix provides full end-to-end tooling support, the Mendix Portable Runtime approach only requires Java to run, with Mendix's support strictly limited to the Mendix Portable Runtime package itself. All implementation, configuration, and deployment activities, including Linux deployment, remain the customer's sole responsibility. For information about the scope of support, see [Support for Different Deployment Strategies](/support/deployment-strategy-support/). {{% /alert %}} ## Prerequisites -To deploy your app to an on-premises Linux configuration using [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/), ensure that you fulfill the following prerequisites: +To deploy your app to an on-premises Linux configuration using [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/), ensure that you fulfill the following prerequisites: * A Linux environment. This can be a virtual machine, a physical server, or a cloud instance (for example, AWS EC2, Azure VM, Google Cloud VM). You will need `sudo` or `root` privileges for some commands. * Java Development Kit (JDK). Your application requires a compatible Java runtime. For installation instructions, refer to the following sections. -* Your [Portable App Distribution .zip file](/developerportal/deploy/portable-app-distribution-deploy/). +* Your [Mendix Portable Runtime .zip file](/developerportal/deploy/portable-app-distribution-deploy/). * A method to transfer the .zip file onto your Linux machine, for example: * Cloud storage - If your Linux machine is in the cloud, you can use the cloud provider's CLI (for example, AWS S3, Azure Blob Storage, Google Cloud Storage). @@ -30,7 +30,7 @@ To deploy your app to an on-premises Linux configuration using [Portable App Dis * Version Control System (VCS) - If your .zip is stored in a repository. * Artifactory/Nexus: For artifact management. -## Deploying an App with Portable App Distribution +## Deploying an App with Mendix Portable Runtime To deploy your app to Linux, perform the following steps: @@ -55,10 +55,10 @@ To deploy your app to Linux, perform the following steps: If your application requires it, you can change the Java version on vendor as needed, for example, `openjdk-21-jdk` or `java-21-amazon-corretto`. - {{% alert color="info" %}} Your Portable App Distribution only requires a Java Runtime Environment (JRE) to run, but it is often recommended to install a full JDK as it includes the JRE and development tools. {{% /alert %}} + {{% alert color="info" %}} Your Mendix Portable Runtime only requires a Java Runtime Environment (JRE) to run, but it is often recommended to install a full JDK as it includes the JRE and development tools. {{% /alert %}} 4. Verify that Java is correctly installed by running the following command: `java -version`. -5. Upload the Portable App Distribution .zip file to a location where your Linux server can access it by using one of the following options, depending on the location and configuration of your Linux machine. +5. Upload the Mendix Portable Runtime .zip file to a location where your Linux server can access it by using one of the following options, depending on the location and configuration of your Linux machine. * For Azure Blob Storage (often done as part of a CI/CD pipeline): `az storage blob upload --account-name --container-name --name .zip --file /build/distributions/your-app.zip --auth-mode login` @@ -102,7 +102,7 @@ To deploy your app to Linux, perform the following steps: sh bin/start ``` - The `bin/start` script is a common convention for Portable App Distributions using the Default configuration. If your application uses a different configuration, start script, or command, adjust accordingly. + The `bin/start` script is a common convention for Mendix Portable Runtimes using the Default configuration. If your application uses a different configuration, start script, or command, adjust accordingly. 9. Verify that the application is running by opening the following URL in your browser: `http://:8080`. diff --git a/content/en/docs/deployment/general/pad/pad-best-practices.md b/content/en/docs/deployment/pad/pad-best-practices.md similarity index 99% rename from content/en/docs/deployment/general/pad/pad-best-practices.md rename to content/en/docs/deployment/pad/pad-best-practices.md index 61ad41cee7a..5077cbd6f40 100644 --- a/content/en/docs/deployment/general/pad/pad-best-practices.md +++ b/content/en/docs/deployment/pad/pad-best-practices.md @@ -2,7 +2,7 @@ title: "Best Practices for Managing Configuration File Precedence" url: /developerportal/deploy/portable-app-distribution-deploy/best-practices/ linktitle: "Best Practices" -weight: 90 +weight: 20 description: "Describes the best practices for managing the configuration order for Portable Apps Distribution." --- diff --git a/content/en/docs/deployment/general/pad/pad-reference.md b/content/en/docs/deployment/pad/pad-reference.md similarity index 95% rename from content/en/docs/deployment/general/pad/pad-reference.md rename to content/en/docs/deployment/pad/pad-reference.md index 6815d59785b..c0c8f422306 100644 --- a/content/en/docs/deployment/general/pad/pad-reference.md +++ b/content/en/docs/deployment/pad/pad-reference.md @@ -2,17 +2,17 @@ title: "Reference Guide for Portable Apps Distribution" url: /developerportal/deploy/portable-apps-distribution/reference/ linktitle: "Reference Guide" -weight: 100 +weight: 30 description: "Describes the folder structure and commmand line parameters for the Portable Apps Distribution deployment method for Mendix apps." --- ## Introduction -In the following Reference Guide document, you can find information about the folder structure of the .zip file generated by Portable App Distribution, as well as the available command-line parameters for the start script. The Reference Guide also suggests some best practices for managing the order of your custom configuration files. +In the following Reference Guide document, you can find information about the folder structure of the .zip file generated by Mendix Portable Runtime, as well as the available command-line parameters for the start script. The Reference Guide also suggests some best practices for managing the order of your custom configuration files. ## Folder Structure -The .zip file generated by Portable App Distribution contains the following files and directories: +The .zip file generated by Mendix Portable Runtime contains the following files and directories: * `app/` - The application, containing the following directories (similar to the .mda file): @@ -126,7 +126,7 @@ runtime.params { ## File Storage -The *example.conf* file in the Portable App Distribution .zip file contains example file storage settings for AWS S3 and Azure Blob Storage. +The *example.conf* file in the Mendix Portable Runtime .zip file contains example file storage settings for AWS S3 and Azure Blob Storage. ### AWS S3 @@ -255,7 +255,7 @@ runtime.params { ## Certificates -The *example.conf* file in the Portable App Distribution .zip file contains example runtime settings for certificates. +The *example.conf* file in the Mendix Portable Runtime .zip file contains example runtime settings for certificates. ```text runtime.params { diff --git a/content/en/docs/refguide/modeling/menus/app-menu/create-deployment-package-dialog.md b/content/en/docs/refguide/modeling/menus/app-menu/create-deployment-package-dialog.md index 42d637d824e..90e1369a39b 100644 --- a/content/en/docs/refguide/modeling/menus/app-menu/create-deployment-package-dialog.md +++ b/content/en/docs/refguide/modeling/menus/app-menu/create-deployment-package-dialog.md @@ -27,7 +27,7 @@ Unfortunately, from the error shown on the log during deployment, it is not alwa Here, you can decide whether you will create a portable deployment package. -A portable deployment package bundles your application code with all its necessary dependencies into a single, self-contained artifact. For more information about portable packages, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/). +A portable deployment package bundles your application code with all its necessary dependencies into a single, self-contained artifact. For more information about portable packages, see [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/). {{< figure src="/attachments/refguide/modeling/menus/app-menu/create-deployment-package-dialog/create-portable-package.png" alt="Create Deployment Package dialog with the portable option selected" width="500" >}} diff --git a/content/en/docs/releasenotes/studio-pro/10/10.24.md b/content/en/docs/releasenotes/studio-pro/10/10.24.md index 6ae4b644c0d..16b6cc1ac91 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.24.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md @@ -67,9 +67,9 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for ### New Features -#### Portable App Distribution (Beta) +#### Mendix Portable Runtime -Portable App Distribution revolutionizes server deployments and simplifies local testing by packaging applications as self-contained zip files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible HOCON-based configuration management for seamless operations across development, testing, and production environments. For more information, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/). +Mendix Portable Runtime (previously called Portable App Distribution) revolutionizes server deployments and simplifies local testing by packaging applications as self-contained zip files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible HOCON-based configuration management for seamless operations across development, testing, and production environments. For more information, see [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/). ### Improvements diff --git a/content/en/docs/releasenotes/studio-pro/11/11.6.md b/content/en/docs/releasenotes/studio-pro/11/11.6.md index 025f7d4b6ca..8a6c7e0ece5 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.6.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.6.md @@ -54,7 +54,7 @@ mts: true * We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions. * We fixed an issue where the Microsoft Defender exclusion utility failed to run * We fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild. -* We fixed an issue where exporting a Portable App Package failed because file copy operations were performed outside the default file-system scope. +* We fixed an issue where exporting a portable app package failed because file copy operations were performed outside the default file-system scope. * We resolved an OS command injection vulnerability in the Git process runner reported by Veracode. * We fixed an issue that caused the **History** pane to crash. * We fixed conversions of **Partial** clones to **Full** clones. Now, your Mendix version is displayed in the new **History** panel after converting a **Partial** clone to a **Full** one. @@ -132,11 +132,11 @@ Additionally, some Marketplace modules could have an incorrect version string in * We added support for XPath constraints in nanoflow database retrieves to follow associations from a variable, so comparisons like `$var/Association = $var` now work. * We added support for strict mode in offline apps (PWA and Native Mobile). Please note that switching strict mode on for existing offline apps may cause problems for existing apps that still call the old API (`retrieve_by_xpath`) in full synchronization, because the `retrieve_by_xpath` is not available in strict mode. -#### Portable App Distribution (Beta) +#### Mendix Portable Runtime -Portable App Distribution revolutionizes server deployments and simplifies local testing by packaging applications as self-contained zip files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible HOCON-based configuration management for seamless operations across development, testing, and production environments. +Mendix Portable Runtime (previously called Portable App Distribution) revolutionizes server deployments and simplifies local testing by packaging applications as self-contained zip files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible HOCON-based configuration management for seamless operations across development, testing, and production environments. -For more information, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/). +For more information, see [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/). ### Improvements diff --git a/content/en/docs/releasenotes/studio-pro/11/11.9.md b/content/en/docs/releasenotes/studio-pro/11/11.9.md index 615d14e47c4..3ea3e03a828 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.9.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.9.md @@ -43,11 +43,11 @@ weight: 91 * You can now undo changes generated by Maia on a per-document basis. * Maia can now set annotation texts in the logic editors. -#### Portable App Distribution (Beta) +#### Mendix Portable Runtime -We have added a new Portable App Distribution option for deployments. Portable App Distribution revolutionizes server deployments and simplifies local testing by packaging applications as self-contained ZIP files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible file-based configuration management for seamless operations across development, testing, and production environments. +We have added a new Mendix Portable Runtime option for deployments. Mendix Portable Runtime (previously called Portable App Distribution) revolutionizes server deployments and simplifies local testing by packaging applications as self-contained ZIP files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible file-based configuration management for seamless operations across development, testing, and production environments. -For more information, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/). +For more information, see [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/). #### Rspack (Beta) diff --git a/content/en/docs/support/deployment-strategy-support.md b/content/en/docs/support/deployment-strategy-support.md index e8dfda2ac12..31b49e1d610 100644 --- a/content/en/docs/support/deployment-strategy-support.md +++ b/content/en/docs/support/deployment-strategy-support.md @@ -13,7 +13,7 @@ With our Multi-Cloud strategy, Mendix allows the apps that you build to be deplo The full stack is depicted in the table below. This indicates which components are **Mendix** supported, or supported by a **Mendix Partner** or a third party. If no support is indicated, then you will need to arrange support of this component yourself. Each of the components is described in more detail in [Components of the Mendix Stack](/support/mendix-stack-components/). -| Stack (refer to [Components of the Mendix Stack](/support/mendix-stack-components/) for more information) | Mendix Cloud | Cloud Dedi­cated | Mendix on Kubernetes - Con­nected | Mendix on Kubernetes - Stand­alone | Private Mendix Platform | SAP BTP | Cloud Foundry, Docker & Kuber­netes, Portable App Distribution, Tradi­tional³ | +| Stack (refer to [Components of the Mendix Stack](/support/mendix-stack-components/) for more information) | Mendix Cloud | Cloud Dedi­cated | Mendix on Kubernetes - Con­nected | Mendix on Kubernetes - Stand­alone | Private Mendix Platform | SAP BTP | Cloud Foundry, Docker & Kuber­netes, Mendix Portable Runtime, Tradi­tional³ | | --- | --- | --- | --- | --- | --- | --- | --- | | **Appli­cation** | | | | | | | | | | **Platform Support­ed Marketplace content** | Mendix | Mendix | Mendix | Mendix | Mendix | Mendix | Mendix | @@ -81,11 +81,11 @@ Mendix Support does not have access to app health, logs, graphs and monitoring {{< figure src="/attachments/support/sap-cloud-platform.png" width="40%" class="no-border" >}} -## Cloud Foundry / Docker and Kubernetes / Portable App Distribution / Traditional Architectures +## Cloud Foundry / Docker and Kubernetes / Mendix Portable Runtime / Traditional Architectures Mendix is compatible with all the well-known cloud providers: IBM Cloud, Microsoft Azure, Amazon Web Services (AWS), Red Hat OpenShift, and Google Cloud Platform. -Depending on the Cloud architecture a Mendix application is built using the [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/), the [Mendix Cloud Foundry buildpack](https://github.com/mendix/cf-mendix-buildpack), the [Mendix Docker Buildpack](https://github.com/mendix/docker-mendix-buildpack) or to a Unix-like or Windows server. +Depending on the Cloud architecture a Mendix application is built using the [Mendix Portable Runtime](/developerportal/deploy/portable-app-distribution-deploy/), the [Mendix Cloud Foundry buildpack](https://github.com/mendix/cf-mendix-buildpack), the [Mendix Docker Buildpack](https://github.com/mendix/docker-mendix-buildpack) or to a Unix-like or Windows server. Check our [System Requirements](/refguide/system-requirements/) for the supported components of any Cloud Foundry / Docker and Kubernetes / traditional architecture. diff --git a/content/en/docs/support/mendix-stack-components.md b/content/en/docs/support/mendix-stack-components.md index 5cd87171457..7352246030e 100644 --- a/content/en/docs/support/mendix-stack-components.md +++ b/content/en/docs/support/mendix-stack-components.md @@ -33,7 +33,7 @@ Mendix Support can analyze this component if your app is running on Mendix Cloud Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers. If it is running on SAP BTP instead, the selected third party can analyze this component. -## Buildpack, m2ee, Service Console, and Portable App Distribution {#buildpack-m2ee-and-service-console} +## Buildpack, m2ee, Service Console, and Mendix Portable Runtime {#buildpack-m2ee-and-service-console} The Mendix buildpacks for [Cloud Foundry](https://github.com/mendix/cf-mendix-buildpack) and [Docker](https://github.com/mendix/docker-mendix-buildpack) are available in GitHub repositories. The documentation for the buildpacks and m2ee tools is contained within these GitHub repositories. Because they are released under an open-source license, the code can be inspected, and the functionality and options can be understood by customers who wish to use these buildpacks. diff --git a/content/en/docs/support/new-app-node-request-template.md b/content/en/docs/support/new-app-node-request-template.md index 3e1ce4dab24..ac0e1afebbb 100644 --- a/content/en/docs/support/new-app-node-request-template.md +++ b/content/en/docs/support/new-app-node-request-template.md @@ -27,7 +27,7 @@ To deploy your app to a new licensed node, you will need to request a node from * **Mendix Cloud Dedicated** – Select this option for apps deployed to Mendix Cloud Dedicated. * **Mendix for Private Cloud** – Select this option for apps deployed to Kubernetes using the Mendix Operator. Refer to [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) for more information. * **Server-based (Windows Server)** – Select this option for apps deployed to Windows. You are required to enter the **Server ID**, which you can retrieve by following the steps in the [Windows Server](/developerportal/deploy/licensing-apps-outside-mxcloud/#windows-server) section of *Licensing Apps*. -* **Container-based (Docker, Cloud Foundry, Kubernetes)** – Select this option for apps deployed to Portable App Distribution, Docker, Cloud Foundry, or Kubernetes, without Mendix Operator. +* **Container-based (Docker, Cloud Foundry, Kubernetes)** – Select this option for apps deployed to Mendix Portable Runtime, Docker, Cloud Foundry, or Kubernetes, without Mendix Operator. * **SAP** – Select this option for apps deployed to SAP. To request your node from Mendix Support, complete the following steps: