diff --git a/content/en/docs/apidocs-mxsdk/apidocs/app-repository-api.md b/content/en/docs/apidocs-mxsdk/apidocs/app-repository-api.md index 9334819c93e..e6af21a2dcb 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/app-repository-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/app-repository-api.md @@ -278,7 +278,7 @@ An object with the following key-value pairs: |`latestCommit.author.name`|String|The full name of the commit author. {{% alert color="info" %}}For Subversion repositories, this will be the same value as the email address of the author. {{% /alert %}}| |`latestCommit.author.email`|String|The email address of the commit author.| |`latestCommit.date`|String|The commit date and time in RFC 3339 format.| -|`latestCommit.message`|String|The commit message.| +|`latestCommit.message`|String|The comit message.| |`latestCommit.relatedStories`|Array|An array of related user story IDs, if available.| |`latestCommit.mendixVersion`|String, optional|The Mendix version used to make this commit, if available.| diff --git a/content/en/docs/apidocs-mxsdk/apidocs/content-api.md b/content/en/docs/apidocs-mxsdk/apidocs/content-api.md index 8b2367df1f2..0843e26ac5f 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/content-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/content-api.md @@ -26,7 +26,7 @@ For details on how to generate a PAT, see the [Creating a PAT](/community-tools/ Select the following : -Select **mx:marketplace-content:read** as the **Marketplace** scope in order to perform `GET` operations. +Select **mx:marketplace-content:read** as the **Marketplace** scope in orde to perform `GET` operations. Copy and store the generated value (`{GENERATED_PAT}`) somewhere safe so you can use it to authorize your API calls. diff --git a/content/en/docs/apidocs-mxsdk/apidocs/user-identifiers-api.md b/content/en/docs/apidocs-mxsdk/apidocs/user-identifiers-api.md index 904d2213e26..91184a4bd0f 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/user-identifiers-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/user-identifiers-api.md @@ -3,7 +3,7 @@ title: "User Identifiers API" linktitle: "User Identifiers API" url: /apidocs-mxsdk/apidocs/user-identifiers-api/ type: swagger -description: "User Identifiers API allows Mendix Admins to perform operations related to user identifiers belonging to their company." +description: "User Identifiers API allows Mendix Admins to perform operations related to user identifiers beloging to their company." weight: 112 --- @@ -49,7 +49,7 @@ To authenticate calls when using the Open API specification below, click **Autho The following steps lead to retrieval of user's UUIDs of the email addresses provided in {emailAddresses}. 1. Set up your authentication PAT. You must be a Mendix Admin. -1. Create a request body containing the email addresses under `emailAddresses`. For example, to get user UUIDs of `jane.doe@domain.tld` and `john.doe@domain.tld`, provide a body like this: +1. Create a request body containing the email adresses under `emailAddresses`. For example, to get user UUIDs of `jane.doe@domain.tld` and `john.doe@domain.tld`, provide a body like this: ```json {linenos=false} { diff --git a/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/_index.md b/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/_index.md index c179b3243a0..bbb7bf37aa9 100644 --- a/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/_index.md +++ b/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/_index.md @@ -55,4 +55,4 @@ All element types have both an interface and a full form. In the JavaScriptDoc y After the server has sent all unit interfaces, the Model SDK client reconstructs the app tree from the available information. However, before you can manipulate an (existing) unit/element or access information on it that's not available in its interface, you have to obtain the full unit/element. -## 5 Documents in This Category +## 5 Documents in This Cateogery diff --git a/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md b/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md index fdff1f587f8..4bc3e53eef9 100644 --- a/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md +++ b/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md @@ -129,7 +129,7 @@ A retrieve action is either an association-based retrieve or a database-based re | Studio Pro Guide | Model SDK API docs | | --- | --- | | [Retrieve](/refguide/retrieve/) |[RetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.retrievesource.html) | -| [XPath](/refguide/xpath/) constraints |[AssociationRetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.associationretrievesource.html) | +| [XPath](/refguide/xpath/) constraints |[AssocationRetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.associationretrievesource.html) | | |[DatabaseRetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.databaseretrievesource.html) | | |[Range](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.range.html), [ConstantRange](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.constantrange.html) and [CustomRange](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.customrange.html) | | |[SortItemList](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.sortitemlist.html) and [SortItem](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.sortitem.html) | diff --git a/content/en/docs/appstore/_index.md b/content/en/docs/appstore/_index.md index 06bac41e50a..33ca8a93dd4 100644 --- a/content/en/docs/appstore/_index.md +++ b/content/en/docs/appstore/_index.md @@ -6,7 +6,7 @@ weight: 40 no_list: false description_list: true cascade: - - content_type: "Marketplace" + - content_type: "Marketplace Guide" - mendix_version: 10 --- diff --git a/content/en/docs/appstore/overview/_index.md b/content/en/docs/appstore/overview/_index.md index 1af615b1b4b..7fad0b8308e 100644 --- a/content/en/docs/appstore/overview/_index.md +++ b/content/en/docs/appstore/overview/_index.md @@ -73,7 +73,7 @@ On this page, you can see and manage the drafts for all the Marketplace content This page presents details on how many total drafts you have, which drafts are ready to publish or are awaiting approval, and which drafts have been declined. -{{< figure src="/attachments/appstore/overview/my-marketplace/my-drafts.png" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/my-drafts.png" class="no-border" >}} These are the possible **Status** entries for each item: @@ -97,7 +97,7 @@ Click the name of the component to go its [component details page](/appstore/com Click the context menu to access various options for managing your content: -{{< figure src="/attachments/appstore/overview/my-marketplace/my-content.png" width="400" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/my-content.png" width="400" class="no-border" >}} * **Manage Drafts** – Click this to manage the drafts of the component * Only one draft version of a component can exist at a time, so when one draft version is in progress, another draft cannot be initiated @@ -118,7 +118,7 @@ In addition, you may see a label on a component name for the [content group](#co You can see all the Marketplace content you have trials for on this page: -{{< figure src="/attachments/appstore/overview/my-marketplace/my-subscriptions.jpg" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/my-subscriptions.jpg" class="no-border" >}} The table presents the **Names** of products you have trials for. @@ -136,7 +136,7 @@ Click the name of the component to go its [component details page](/appstore/com Click the context menu to access various options for managing this content: -{{< figure src="/attachments/appstore/overview/my-marketplace/saved.png" width="400" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/saved.png" width="400" class="no-border" >}} * **Receive/Stop Email Notifications** – click this to start receiving email notifications or to stop the notifications if you already have them enabled * **Unsave** – click this to remove the component from your saved content @@ -163,7 +163,7 @@ Click the name of the component to go its [component details page](/appstore/com Click the context menu to access various options for managing this content: -{{< figure src="/attachments/appstore/overview/my-marketplace/company-content.png" width="400" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/company-content.png" width="400" class="no-border" >}} The options in this menu are the same as described for the context menu for the [My Content](#my-content) section above. However, the **Edit a Version** and **Unpublish a Version** options are only available for your own versions of company content. @@ -171,7 +171,7 @@ The options in this menu are the same as described for the context menu for the You can see all the content shared within your organization on this page, which includes previously purchased products, trial subscriptions, paid subscriptions, or company-level services: -{{< figure src="/attachments/appstore/overview/my-marketplace/company-subscriptions.png" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/company-subscriptions.png" class="no-border" >}} The table presents the **Names** of the products your company has subscribed to. @@ -199,7 +199,7 @@ This table breaks down the roles and permissions for content groups: On this tab, you can assign content to this content group that can only be managed by members of this group. To assign a component to a content group, click **Assign Content** and select a company Marketplace component from the dialog box: -{{< figure src="/attachments/appstore/overview/my-marketplace/group-content.png" width="400" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/group-content.png" width="400" class="no-border" >}} {{% alert color="info" %}} A component can only be assigned to one content group at a time. If a component is already assigned to another content group, it will not appear in this dialog box. @@ -207,7 +207,7 @@ A component can only be assigned to one content group at a time. If a component Click the context menu to access various options for managing this content: -{{< figure src="/attachments/appstore/overview/my-marketplace/group-content-context.png" width="400" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/group-content-context.png" width="400" class="no-border" >}} The options in this menu are the same as described for the context menu for the [My Content](#my-content) section above. The **Unassign from Group** button is only available for [Group Admins](#members) and can be used to remove content from the content group. diff --git a/content/en/docs/appstore/overview/component-details.md b/content/en/docs/appstore/overview/component-details.md index 024682cac73..d5fcafe34d9 100644 --- a/content/en/docs/appstore/overview/component-details.md +++ b/content/en/docs/appstore/overview/component-details.md @@ -10,33 +10,29 @@ description: "Presents information on the component details page." Clicking the tile of a [Marketplace](https://marketplace.mendix.com/) component brings you to its details page with the sections described below. -{{< figure src="/attachments/appstore/overview/overview/component-details.png" class="no-border" >}} +{{< figure src="/attachments/appstore/overview/component-details/component-details.png" >}} ## 2 Header The header for a component presents the following details: +* Labels (if there is any) + * **Partner**: If the header contains this label, it means that the component is partner-supported. + * These components can have a **Contact Us** button for setting up your subscription with the partner. + * If you already have an active subscription or trial, click **View status** to go to the [Company Subscriptions](/appstore/overview/#company-subscriptions) page. + * **Mendix**: If the header contains this label, it means that the component is platform-supported. + * **Siemens**: If the header contains this label, it means that the component is Siemens-supported. + * **Recommended**: If the header contains this label, it means that the component meets your company's policies and guidelines, and therefore is recommended by your Mendix Admins. * The name of the component - * The review average (in stars) and the number of reviews - * The number of times the component has been downloaded - -* **Save and Get Notified** – click this to add the component to your [Saved Content](/appstore/overview/#personal) list - +* **Save** – Click this to add the component to your [Saved Content](/appstore/overview/#personal) list. * Depending on the content type: - * **Use in Studio Pro** for modules and widgets – click this to copy the content ID so that you can [search for and use the component in Studio Pro](/appstore/use-content/#current-sp) - * **Start with Template** for starter templates – click this to use the template - * **Download** for other content types – click this to download the component - * **Contact Us** – click this to contact Mendix or the community supplier - -* The partner icon is applied to components that are supported by a partner: - - {{< figure src="/attachments/appstore/overview/overview/partner.png" width="25" class="no-border" >}} - - * These components have a **Contact Us** button for setting up your subscription with the partner - * If you already have an active subscription or trial, click **View status** to go to the [Company Subscriptions](/appstore/overview/#company-subscriptions) page + * **Use in Studio Pro** for modules and widgets – Click this to copy the content ID so that you can [search for and use the component in Studio Pro](/appstore/use-content/#current-sp). + * **Start with Template** for starter templates – Click this to use the template. + * **Download** for other content types – Click this to download the component. + * **Contact Us** – Click this to contact Mendix or the community supplier. The **Usage** section presents the following information (depending on the type of component): @@ -58,12 +54,14 @@ The component details page also presents the following tabs: * **Documentation** – This tab includes details on typical use cases, features and limitations, dependencies, installation and configuration, frequently asked questions, and screenshots. * [Platform-supported components](/appstore/marketplace-content-support/#category) are documented according to content type or category in the [Marketplace Guide](/appstore/). * **Releases** – This tab lists all the versions of the component along with details like the **Framework version** and the **UUID**. - * Each version can be downloaded by clicking **Download.** + * Each version can be downloaded by clicking **Download.** + * If any version has the label **React-Ready** next to it, it means this version is optimized for React Client applications. * **Reviews** – This tab shows user reviews of the component. - * You can browse, sort by review date, and filter by ratings for insights on the component. - * You can select the **Only show my reviews** checkbox to check your own reviews. - * You can click **Write Review** to open a section where you can add text, rate the component, and submit the review. - * Before you write a review, you can first read the **Tips for Sharing Your Review**, which appears on the right. You can now rate a component four or five stars without leaving a review. For three-, two-, and one-star ratings, a review is mandatory. - * You can find all your reviews on your [My Reviews](/appstore/overview/#my-reviews) page in the Marketplace home page. - * If you are a developer of the component, you can **Reply** to a review. + * You can browse, sort by review date, and filter by ratings for insights on the component. + * You can select the **Only show my reviews** checkbox to check your own reviews. + * You can click **Write Review** to open a section where you can add text, rate the component, and submit the review. + * Before you write a review, you can first read the **Tips for Sharing Your Review**, which appears on the right. You can now rate a component four or five stars without leaving a review. For three-, two-, and one-star ratings, a review is mandatory. + * You can find all your reviews on your [My Reviews](/appstore/overview/#my-reviews) page in the Marketplace home page. + * If you are a developer of the component, you can **Reply** to a review. * **Developers** – This tab shows the names of the developers who most recently updated the component, with links to their [Mendix Profile](/community-tools/mendix-profile/). + diff --git a/content/en/docs/appstore/use-content/_index.md b/content/en/docs/appstore/use-content/_index.md index 999e01ee344..d62a9d69dff 100644 --- a/content/en/docs/appstore/use-content/_index.md +++ b/content/en/docs/appstore/use-content/_index.md @@ -42,11 +42,11 @@ To download content in Studio Pro [9.19](/releasenotes/studio-pro/9.19/) and abo 3. To open the Marketplace in Studio Pro, you can either click the **View** menu in the top bar and select **Marketplace**, or you can click the Marketplace icon on the right side of the top bar - {{< figure src="/attachments/appstore/overview/use-content/toolbar.png" alt="Marketplace icon" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/toolbar.png" alt="Marketplace icon" class="no-border" >}} The **Marketplace** pane opens. - {{< figure src="/attachments/appstore/overview/use-content/marketplace.png" alt="Search result for rating" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/marketplace.png" alt="Search result for rating" class="no-border" >}} 4. You can explore Marketplace content in the following ways: * Use **Search in the Marketplace** to find the component that you want to download @@ -56,7 +56,7 @@ To download content in Studio Pro [9.19](/releasenotes/studio-pro/9.19/) and abo 5. Select a component from the pane to see its details: - {{< figure src="/attachments/appstore/overview/use-content/component-details.png" alt="Details of Blank App example component" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/component-details.png" alt="Details of Blank App example component" class="no-border" >}} The details presented here correspond to what you see on the [component details page](/appstore/component-details/) in the online Mendix Marketplace. @@ -101,7 +101,7 @@ Click **OK** in the confirmation pop-up window. Your extension is now installed If you do not want to trust the extension and would prefer to remove the extension altogether, you can remove the add-on module that was added. -{{< figure src="/attachments/appstore/overview/use-content/trust-extension.png" alt="trust extension" >}} +{{< figure src="/attachments/appstore/use-content/trust-extension.png" alt="trust extension" >}} ##### 2.1.1.4 Apps {#apps} @@ -141,7 +141,7 @@ To import content downloaded from the online Mendix Marketplace into Studio Pro, 4. Click **Download** to download the latest version of the component. Or, if you want to download an older component version, go to the **Releases** tab and **Download** the desired version. 5. In the **App Explorer**, right-click the app, then click **Import module package**, and select the component you downloaded: - {{< figure src="/attachments/appstore/overview/use-content/import-module-in-app-explorer.png" alt="import-module-in-app-explorer" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/import-module-in-app-explorer.png" alt="import-module-in-app-explorer" class="no-border" >}} The **Import Module** dialog box opens. @@ -191,7 +191,7 @@ To add a widget from the **Toolbox**, follow these steps: 1. Open the page where you want to add the widget. 2. In the **Toolbox**, search for the name of the widget (for example, *Rating* to find the widget): - {{< figure src="/attachments/appstore/overview/use-content/toolbox-rating.png" alt="Rating widget found in the toolbox" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/toolbox-rating.png" alt="Rating widget found in the toolbox" class="no-border" >}} 3. Drag the widget to the place on the page where you want it to be. @@ -199,16 +199,16 @@ To add a widget using the **Add widget** option from the toolbar, follow these s 1. Click **Add widget** on the toolbar on the page where you want to add the widget. The **Select Widget** dialog box opens. - {{< figure src="/attachments/appstore/overview/use-content/add-widget.png" alt="Add widget" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/add-widget.png" alt="Add widget" class="no-border" >}} 2. In the **Filter** bar, enter the name of the widget, for example *Rating*, to find the widget. - {{< figure src="/attachments/appstore/overview/use-content/select-widget.png" alt="Rating widget highlighted in Select Widget dialog box" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/select-widget.png" alt="Rating widget highlighted in Select Widget dialog box" class="no-border" >}} 3. Click the widget and then click **Select**. 4. In the page, click where you want to drop the widget. The widget is added to the location where the mouse pointer is. - {{< figure src="/attachments/appstore/overview/use-content/widget-dropped-in-page.png" alt="Rating widget in the page" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/widget-dropped-in-page.png" alt="Rating widget in the page" class="no-border" >}} #### 3.1.2 Updating the Widget to a Newer Version @@ -230,15 +230,15 @@ To configure the widget, follow these steps: 1. Go to the **Errors** pane and check the error message. This error shows after you drop the **Rating** widget into the page: - {{< figure src="/attachments/appstore/overview/use-content/widget-errors.png" alt="Errors pane" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/widget-errors.png" alt="Errors pane" class="no-border" >}} 2. In the page, double-click the Rating widget. The **Edit Rating** dialog box opens and the **Attribute** field shows **(none)** – this means that no attribute is assigned, which causes the error. - {{< figure src="/attachments/appstore/overview/use-content/edit-rating.png" alt="Edit Rating dialog box" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/edit-rating.png" alt="Edit Rating dialog box" class="no-border" >}} 3. Click **Select** to select an attribute. In this example, we select the attribute **ProductRating**. This is the attribute of an entity that we already created. - {{< figure src="/attachments/appstore/overview/use-content/select-attribute.png" alt="ProductRating selected in Select Attribute dialog box" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/select-attribute.png" alt="ProductRating selected in Select Attribute dialog box" class="no-border" >}} 4. In the **Edit Rating** dialog box, click **OK**. The error in the **Errors** pane disappears. @@ -258,7 +258,7 @@ To update the module in your app to a newer version, follow these steps:: {{% alert color="warning" %}}If you have made any changes to the existing module, selecting **Replace existing module** option will replace all the changes that you made, for example, your renamed entities, attributes, and associations as well as their respective tables and columns represented in the database will all be replaced. Your user data will stay if you have not changed entities, attributes, or associations. If you have changed data types, your user data can be influenced as well. For more information, see [Attribute Type Migration](/refguide/attributes-type-migration/).{{% /alert %}} - {{< figure src="/attachments/appstore/overview/use-content/import-module.png" alt="Import Module dialog box" class="no-border" >}} + {{< figure src="/attachments/appstore/use-content/import-module.png" alt="Import Module dialog box" class="no-border" >}} 3. Check the **userlib** folder in your app directory for duplicate Java libraries. If your **userlib** folder contains multiple versions of the same Java library, it is usually safe to delete the old ones and keep only the new one. diff --git a/content/en/docs/appstore/use-content/marketplace-content-support.md b/content/en/docs/appstore/use-content/marketplace-content-support.md index 4fd2ca5ef28..0a40829819e 100644 --- a/content/en/docs/appstore/use-content/marketplace-content-support.md +++ b/content/en/docs/appstore/use-content/marketplace-content-support.md @@ -85,3 +85,4 @@ Partner-supported content is created and maintained by partners as part of the [ | ---------------- | -------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | | **Siemens** | N/A | Siemens supports. | Content in this category is provided and supported by the Siemens team. Siemens supports this content as-is when you are equipped with an SLA with Siemens. | | **Community** | Mendix community supports | Options: No support from partner, or Mendix community supports | Content is provided as-is by members of the Mendix community, and support depends on the availability and effort of the owner. | + diff --git a/content/en/docs/appstore/use-content/modules/deep-link.md b/content/en/docs/appstore/use-content/modules/deep-link.md index 4d0d7531611..0b44cbcd1ed 100644 --- a/content/en/docs/appstore/use-content/modules/deep-link.md +++ b/content/en/docs/appstore/use-content/modules/deep-link.md @@ -10,6 +10,10 @@ description: "Describes the configuration and usage of the Deep Link module, whi This module is deprecated from Studio Pro 10.6.0. It is replaced by [page URLs](/refguide/page-properties/#url) and [microflow URLs](/refguide/microflow/#url). For instructions on migrating to page and microflow URLs, see the [Migrating to Page and Microflow URLs](#migrate-page-micro) section below.
We will continue to actively support this module for Mendix 9. {{% /alert %}} +{{% alert color="warning" %}} +However, both the page URLs and microflow URLs are not yet able to support continuations, for instance, for certain SSO modules. As a result, you cannot configure the SSO correctly using page URLs and microflow URLs. If this affects your app, then you should not stop using the Deep Link module yet. We aim to add these features in Q2 2024. +{{% /alert %}} + ## 1 Introduction The [Deep Link](https://marketplace.mendix.com/link/component/43/) module allows you to configure a mapping between a request handler and microflows. In this way, you can create additional entry points to access specific parts of your application. The Deep Link module is design- and runtime-configurable, it respects security, and it supports links for both logged-in and anonymous users. diff --git a/content/en/docs/appstore/use-content/modules/document-generation.md b/content/en/docs/appstore/use-content/modules/document-generation.md index f22d74375a8..5e308a3202c 100644 --- a/content/en/docs/appstore/use-content/modules/document-generation.md +++ b/content/en/docs/appstore/use-content/modules/document-generation.md @@ -390,7 +390,7 @@ In case you encounter a `DocGenWaitForContentException` exception with error cod ##### 6.2.1.2 Navigation Exception -In case you encounter a `DocGenNavigationException` exception with error code `DOCGEN_NAVIGATION_ERROR` while generating a document, refer to the table below for more details and suggestions on how to resolve them. +In case you encounter a `DocGenNavigationException` exception wıth error code `DOCGEN_NAVIGATION_ERROR` while generating a document, refer to the table below for more details and suggestions on how to resolve them. | Error message | Potential reasons | | ------------------------------------------------------------ | ------------------------------------------------------------ | diff --git a/content/en/docs/appstore/use-content/modules/encryption.md b/content/en/docs/appstore/use-content/modules/encryption.md index 5c6ae2e4a19..4a0ed04fa40 100644 --- a/content/en/docs/appstore/use-content/modules/encryption.md +++ b/content/en/docs/appstore/use-content/modules/encryption.md @@ -49,7 +49,7 @@ If you are updating the module from a version below 1.4.1 to 1.4.1 or above (inc ## 3 FileDocument Encryption -Encrypt and decrypt the contents of FileDocument entities using the [PGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) algorithm. The key used for symmetric encryption is embedded into encrypted file content. The certificate to use asymmetric encryption of the symmetric key is stored in the database. +Encrypt and decrypt the contents of FileDocument entities using the [PGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) algorithm. The key used for symetric encryption is embedded into encrypted file content. The certificate to use asymetric encryption of the symetric key is stored in the database. ### 3.1 Typical Use Cases diff --git a/content/en/docs/appstore/use-content/modules/excel-exporter.md b/content/en/docs/appstore/use-content/modules/excel-exporter.md index 72bc67d5ec0..78d9b9c9560 100644 --- a/content/en/docs/appstore/use-content/modules/excel-exporter.md +++ b/content/en/docs/appstore/use-content/modules/excel-exporter.md @@ -259,7 +259,7 @@ On the **Sheet Preferences** tab, you can define sheet preferences with the foll * **New**: opens the **Form title** dialog box that contains the following items: * **Column number**: the number of the column, same as **Column index** * **Automatic resize** - * If selected, the column width is automatically adjusted and **Column width** is unavailable + * If selected, the column width is automatically adjusted and **Column width** is unavailble * If unselected, the **Column width** property becomes available * **Column width (pixels)**: the fixed width of the column in pixels * **Edit**: opens the **Form title** dialog box where you can make changes to the selected column settings diff --git a/content/en/docs/appstore/use-content/modules/genai/_index.md b/content/en/docs/appstore/use-content/modules/genai/_index.md index 73d8a51f0a6..699f165fada 100644 --- a/content/en/docs/appstore/use-content/modules/genai/_index.md +++ b/content/en/docs/appstore/use-content/modules/genai/_index.md @@ -1,7 +1,7 @@ --- title: "Enrich Your Mendix App with GenAI Capabilities" url: /appstore/modules/genai/ -linktitle: "GenAI Capabilities of Mendix" +linktitle: "GenAI Capabilites of Mendix" description: "Describes the general properties and common concepts of generative AI in the context of developing Mendix applications and illustrates the preferred way of leveraging platform-supported connectors in applications following the GenAI Commons patterns." --- diff --git a/content/en/docs/appstore/use-content/modules/genai/concepts/prompt-engineering.md b/content/en/docs/appstore/use-content/modules/genai/concepts/prompt-engineering.md index a30e510abbd..4ed5dc3d1ff 100644 --- a/content/en/docs/appstore/use-content/modules/genai/concepts/prompt-engineering.md +++ b/content/en/docs/appstore/use-content/modules/genai/concepts/prompt-engineering.md @@ -57,7 +57,7 @@ You can instruct the model to format the output in a specific way. For example: ## 3 Use an Iterative Approach -Mendix recommends that you test your prompt against different scenarios. Writing a prompt is therefore similar to modeling a microflow. +Mendix recommends that you test your prompt against different scenarios. Writing a prompt is therefore similar to modelling a microflow. You should do the following: diff --git a/content/en/docs/appstore/use-content/modules/genai/genai-commons.md b/content/en/docs/appstore/use-content/modules/genai/genai-commons.md index b86fd394026..93abf07cf24 100644 --- a/content/en/docs/appstore/use-content/modules/genai/genai-commons.md +++ b/content/en/docs/appstore/use-content/modules/genai/genai-commons.md @@ -358,7 +358,7 @@ Use this microflow to control how the model should determine which function to l | Name | Type | Mandatory | Description | |---|---|---|---| | `Request` | [Request](#request) | Yes | The request for which to set a tool choice. | -| `Tool` | [Tool](#tool) | Required if `ENUM_ToolChoice` equals `tool`. | Specifies the tool to be used. Required if the `ENUM_ToolChoice` equals `tool`; ignored for all other enumeration values. | +| `Tool` | [Tool](#tool) | Required if `ENUM_ToolChoice` equals `tool`. | Specifies the tool to be used. Required if the `ENUM_ToolChoice` equals `tool`; ignored for all other enumaration values. | | `ENUM_ToolChoice` | [ENUM_ToolChoice](#enum-toolchoice) | Yes | Determines the tool choice. For more information, see the [ENUM_ToolChoice](#enum-toolchoice) section for a list of the available values. | ###### 4.3.1.7.2 Return Value @@ -399,11 +399,11 @@ Use this microflow to get the list of references that may be included in the mod | Name | Type | Description | |---|---|---| -| `ReferenceList` | List of [Reference](#reference) | The references with optional citations that were part of the response message. | +| `ReferenceList` | List of [Reference](#reference) | The references with optinional citations that were part of the response message. | ### 4.3.3 Chat Completions Interface {#chat-completions-interface} -The [OpenAI connector](/appstore/modules/genai/openai/) and the [Amazon Bedrock connector](/appstore/modules/genai/bedrock/) both have two chat completion operations implemented that share the same interface, meaning that they expect the same entities as input and as output. This has the advantage that these operations can be exchanged very easily without much additional development effort. +The [OpenAI connector](/appstore/modules/genai/openai/) and the [Amazon Bedrock connector](/appstore/modules/genai/bedrock/) boh have two chat completion operations implemented that share the same interface, meaning that they expect the same entities as input and as output. This has the advantage that these operations can be exchanged very easily without much additional development effort. We recommend that you adapt to the same interface when developing custom chat completion operations, such as integration with different AI providers. The generic interfaces are described below. For more detailed information, refer to the documentation of the connector that you want to use, since it may expect specializations of the generic GenAI common entities as an input. diff --git a/content/en/docs/appstore/use-content/modules/image-crop.md b/content/en/docs/appstore/use-content/modules/image-crop.md index 775c389ce4f..71d5443f53b 100644 --- a/content/en/docs/appstore/use-content/modules/image-crop.md +++ b/content/en/docs/appstore/use-content/modules/image-crop.md @@ -71,7 +71,7 @@ These are the **Cropper** widget properties: * **newWidth** and **newHeight** – make sure these match the **Aspect ratio** used in the [Cropper Widget](#cropper) to make sure the image does not get transformed inconsistently * If either **newWidth** or **newHeight** are set to *0*, the image will be scaled based on the entered value while keeping the aspect ratio * If both **Max width** and **Max height** are set to *0*, the width and height set by the end-user with the widget will be used -* **thumbnailWidth** and **thumbnailHeight** – this is the size of the thumbnail, which is editable so that you can keep this in or near the same aspect ratio as the new image; the default implementation uses the thumbnail size as configured in **Configuration/ThumbnailSize** unless the image is smaller than the thumbnail +* **thumbnailWidth** and **thumbnailHeight** – this is the size of the thumbnail, which is editable so that you can keep this in or near the same aspect ratio as the new image; the default implementation uses the tumbnail size as configured in **Configuration/ThumbnailSize** unless the image is smaller than the thumbnail ## 5 Developing This Marketplace Component diff --git a/content/en/docs/appstore/use-content/modules/mendix-mini-surveys.md b/content/en/docs/appstore/use-content/modules/mendix-mini-surveys.md index 6870fdc950f..93a45492c8f 100644 --- a/content/en/docs/appstore/use-content/modules/mendix-mini-surveys.md +++ b/content/en/docs/appstore/use-content/modules/mendix-mini-surveys.md @@ -96,7 +96,7 @@ If this occurs, try the following: * In the app, open the settings of the Mini Survey widget. Make sure that you have entered the correct survey ID. -* In the app, enable the **TEST_MODE** constant. If the survey loads, then the survey has triggered an [op-out rule](#survey-rules) and will not show. In this case, clear the survey opt-out rules by clearing your browser cache or using incognito mode. +* In the app, enable the **TEST_MODE** constant. If the survey loads, then the survey has triggered an [op-out rule](#survey-rules) and will not show. In this case, clear the survey opt-out rules by clearing your browser cache or using igcognito mode. ### 5.2 Surveys Do not Work Locally When Running Multiple Applications diff --git a/content/en/docs/appstore/use-content/modules/model-reflection.md b/content/en/docs/appstore/use-content/modules/model-reflection.md index d7a8092ba5f..6e101a2a95e 100644 --- a/content/en/docs/appstore/use-content/modules/model-reflection.md +++ b/content/en/docs/appstore/use-content/modules/model-reflection.md @@ -35,7 +35,7 @@ For all other attributes, the functions from *java.util.Formatter* are used (for All the patterns use the locale from the context. Based on the user's language, the pattern will change its behavior if necessary. -### 2.2 Display Pattern Example (Using En_US Language) +### 2.2 Display Pattern Example (Using En_US Lanuage) * Long attribute with a thousand separator: * Pattern: `%,8d%n` diff --git a/content/en/docs/appstore/use-content/modules/snowflake/snowflake-edc.md b/content/en/docs/appstore/use-content/modules/snowflake/snowflake-edc.md index 13630279942..d56554352e3 100644 --- a/content/en/docs/appstore/use-content/modules/snowflake/snowflake-edc.md +++ b/content/en/docs/appstore/use-content/modules/snowflake/snowflake-edc.md @@ -274,7 +274,7 @@ To execute and test the query in Studio Pro, follow these steps: from ztoday as zt ``` - This query results in a single string return value, containing a nested json with weather forecast for today for multiple postal code areas. This resulting string is captured in a non-persistent entity (NPE) with a single attribute. + This query results in a single string return value, containing a nested json with weather forecast for today for multiple zipcode areas. This resulting string is captured in a non-persistent entity (NPE) with a single attribute. {{< figure src="/attachments/appstore/modules/external-database-connector/sample-snowflake-query-replication.png" >}} diff --git a/content/en/docs/appstore/use-content/modules/unit-testing.md b/content/en/docs/appstore/use-content/modules/unit-testing.md index 6d4eb6dd2ff..4120a7fe728 100644 --- a/content/en/docs/appstore/use-content/modules/unit-testing.md +++ b/content/en/docs/appstore/use-content/modules/unit-testing.md @@ -63,7 +63,7 @@ The Unit Testing module publishes a **reportStep** microflow that can be used in ### 4.2 Creating a Java Unit Tests (with JUNit) -The Java unit test runner is driven by [JUnit](https://junit.org/junit5/) and requires a general understanding of JUnit version 4. A JUnit test method is run if it exists somewhere in the module name space (that is, it is stored as a Java class that lives somewhere in the *javasource/yourmodulename* folder). A Java function is recognized as a test if it is public, non-static, parameter-less, and annotated with the `org.junit.Test` annotation. Multiple tests can exists in a single class, but JUnit does not guarantee the execution order of the tests. +The Java unit test runner is driven by [JUnit](https://junit.org/junit5/) and requires a general understanding of JUnit version 4. A JUnit test method is run if it exists somewhere in the module name space (that is, it is stored as a Java class that lives somewhere in the *javasource/yourmodulename* folder). A Java function is recognized as a test if it is public, non-static, parameter-less, and annotated with the `org.junit.Test` annotation. Multiple tests can exists in a single class, but JUnit does not guarantuee the execution order of the tests. For some example JUnit unit tests, see the *src/javasource/unittesting/UnittestingUnitTest1.java* and *src/javasource/unittesting/UnittestingUnitTest2.java* files. diff --git a/content/en/docs/appstore/use-content/modules/workflow-commons.md b/content/en/docs/appstore/use-content/modules/workflow-commons.md index badf8835b8d..e51139dd8fa 100644 --- a/content/en/docs/appstore/use-content/modules/workflow-commons.md +++ b/content/en/docs/appstore/use-content/modules/workflow-commons.md @@ -125,7 +125,7 @@ Workflow Audit Trail is a detailed, chronological record that tracks all changes ### 5.2 Configuration {#configuration} -Workflow Audit Trail uses [workflow events](/refguide/workflow-events/#configuration) to store data of a single or all workflows in your app. You can configure the audit trail to keep track of a specific set of events which you can configure in the **Event handlers** setting in [App Settings](/refguide/app-settings/#event-handlers) or through [workflow properties](/refguide/workflow-properties/#event-handlers). For more information about event handlers in workflows, see the [Event Handlers](/refguide/workflow-properties/#event-handlers) section in *Workflow Properties*. +Workflow Audit Trail uses [workflow events](/refguide/workflow-events/#configuration) to store data of a single or all workflows in your app. You can configure the audit trail to keep track of a specific set of events which you can configure in the **Event handlers** setting in [App Settings](/refguide/app-settings/#event-handlers) or through [workflow properties](/refguide/workflow-properties/#event-handlers). For more information about event handlers in workflows, see the [Event Handlers](/refguide/workflow-properties/#event-handlers) secion in *Workflow Properties*. {{% alert color="info" %}}The event handlers added in workflow properties override the app-wide event handlers in **App Settings**. When adding event handlers at workflow level while the event handlers defined at app level are still applicable, then they should be added at workflow level as well. {{% /alert %}} diff --git a/content/en/docs/catalog/_index.md b/content/en/docs/catalog/_index.md index 245d083e6fa..72d3299cae5 100644 --- a/content/en/docs/catalog/_index.md +++ b/content/en/docs/catalog/_index.md @@ -6,7 +6,7 @@ weight: 41 no_list: false description_list: true cascade: - - content_type: "Catalog" + - content_type: "Catalog Guide" - mendix_version: 10 aliases: - /data-hub/data-catalog/index.html diff --git a/content/en/docs/community-tools/_index.md b/content/en/docs/community-tools/_index.md index c4e5e252ecf..4c3cb7e73ea 100644 --- a/content/en/docs/community-tools/_index.md +++ b/content/en/docs/community-tools/_index.md @@ -6,7 +6,7 @@ weight: 38 no_list: false description_list: true cascade: - - content_type: "Community" + - content_type: "Community Tools Guide" - mendix_version: 10 aliases: - /developerportal/community-tools/ @@ -18,7 +18,7 @@ The Mendix Portal is the online platform of Mendix. It includes [Apps](/develope ## 1 Introduction -Visit the [Mendix Community](https://community.mendix.com) for all the information you need as a member of the Mendix community. Each section of the site represents a community tool that is continuously updated with new content and exciting developments. Furthermore, the content on the site is not only created for the Mendix community, it is created by the Mendix community! +Visit the [Mendix Community](https://community.mendix.com) for all the information you need as a member of the Mendix community. Each section of the site represents a community tool that is continuously updated with new content and exciting developments. Futhermore, the content on the site is not only created for the Mendix community, it is created by the Mendix community! {{< figure src="/attachments/community-tools/site.png" class="no-border" >}} diff --git a/content/en/docs/community-tools/mendix-community.md b/content/en/docs/community-tools/mendix-community.md index 2a16f69bdff..7e6f7075656 100644 --- a/content/en/docs/community-tools/mendix-community.md +++ b/content/en/docs/community-tools/mendix-community.md @@ -63,7 +63,7 @@ Each question has the following details: 7. The number of answers to the question 8. The number of emojis received 9. The name, avatar, and [points level](/community-tools/mendix-profile/#level) of the Mendix community member who asked the question -10. The avatars of the Mendix community members who have answered and commented +10. The avatars of the Mendix comminity members who have answered and commented {{% alert color="info" %}} Hover over the Mendix user name to see the profile card with their Mendix points. Click the Mendix user name on the card to go to their Mendix Profile. @@ -264,7 +264,7 @@ Each idea has the following details: 11. The name, avatar, and [points level](/community-tools/mendix-profile/#level) of the Mendix community member who posted the idea -12. The avatars of the Mendix community members who have commented +12. The avatars of the Mendix comminity members who have commented #### 3.3.1 Searching and Filtering Ideas diff --git a/content/en/docs/community-tools/mendix-profile/user-settings.md b/content/en/docs/community-tools/mendix-profile/user-settings.md index de5dd70439d..0950a7b846f 100644 --- a/content/en/docs/community-tools/mendix-profile/user-settings.md +++ b/content/en/docs/community-tools/mendix-profile/user-settings.md @@ -108,7 +108,7 @@ If you are using the Mendix platform to manage credentials then your password ha You can update the password of your logged-in account via the [Change Password](https://login.mendix.com/mxid3/request-password-reset) button that is available by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) on the logged-in account. You can also reach this screen using the **Forgot password?** link on the login screen. -* Passwords on the Mendix platform must fulfill the following criteria: +* Passwords on the Mendix platform must fulfil the following criteria: * The password must contain * at least one special character from `` `~!@#$%^&*()-_+=[]{};:'"\|,.<>/? `` diff --git a/content/en/docs/control-center/_index.md b/content/en/docs/control-center/_index.md index d768874e04e..1c09e1893f2 100644 --- a/content/en/docs/control-center/_index.md +++ b/content/en/docs/control-center/_index.md @@ -6,7 +6,7 @@ weight: 35 no_list: false description_list: true cascade: - - content_type: "Control Center" + - content_type: "Control Center Guide" - mendix_version: 10 aliases: - /developerportal/control-center diff --git a/content/en/docs/control-center/apps.md b/content/en/docs/control-center/apps.md index 387c09a1efa..e6f7c909c54 100644 --- a/content/en/docs/control-center/apps.md +++ b/content/en/docs/control-center/apps.md @@ -75,7 +75,7 @@ The description of the items that you can select are as follows: * **DB RAM**: the size the RAM allocation for database operations -* **DB Storage**: the size of the database storage +* **DB Storage**: the size of the dabase storage * **DB Storage Extra**: the extra storage of the database @@ -127,7 +127,7 @@ The description of the items that you can select are as follows: * **NamespaceID**: the ID of the namespace -* **Namespace**: the Kubernetes namespace +* **Namespace**: the Kubernets namespace {{% alert color="info" %}}For more information, see [How to Create a Cluster and Namespace](/developerportal/deploy/private-cloud-cluster/#3-creating-a-cluster-and-namespace) in *Creating a Private Cloud Cluster*.{{% /alert %}} @@ -267,7 +267,7 @@ Deleting and deactivating apps is currently not supported for licensed apps or a ## 9 Deactivating and Deleting Apps {#deactivate-delete-apps} -You can delete or deactivate a single app, or deactivate (or activate) multiple apps in one go. +You can delete or deactivate a single app, or deactive (or activate) mutilple apps in one go. The consequences of deactivating and deleting an app are as below: diff --git a/content/en/docs/control-center/company-settings.md b/content/en/docs/control-center/company-settings.md index 820dd1512d3..d5632ab101b 100644 --- a/content/en/docs/control-center/company-settings.md +++ b/content/en/docs/control-center/company-settings.md @@ -8,7 +8,7 @@ no_list: list ## 1 Introduction -The **Company Settings** page allows you to change company details, company email domains, and security contact. Moreover, you can view and add Mendix Admins of your company. +The **Company Settings** page allows you to change company details, company email domains, and security contact. Moreoever, you can view and add Mendix Admins of your company. ## 2 General Settings diff --git a/content/en/docs/developerportal/_index.md b/content/en/docs/developerportal/_index.md index 2a83720108e..7166fbcb08e 100644 --- a/content/en/docs/developerportal/_index.md +++ b/content/en/docs/developerportal/_index.md @@ -63,7 +63,7 @@ The features in the navigation pane can also be accessed via APIs, enabling thir The **Company Apps** tab displays all the apps created by members of your [company](/control-center/company-settings/). -There are also details on the app's [Target Cloud](/deployment/), and the [Total Members](/control-center/members/) who can view or edit the app. +There are also details on the app's [Target Cloud](/developerportal/deploy/), and the [Total Members](/control-center/members/) who can view or edit the app. You can also sort the order of the apps here by **Updated Date**, **Last Created**, **App Name**, **App Name, descending**, **Oldest Updated**, or **Oldest Created**. @@ -73,7 +73,7 @@ You can also sort the order of the apps here by **Updated Date**, **Last Created The **Pending Invites** tab is only visible if you have any pending invites. {{% /alert %}} -The **Pending Invites** tab presents the pending invitations to apps that you have received. You can accept or decline the invite. +The **Pending Invites** tab presents the pending invitations to apps that you have received. You can accept or deline the invite. {{% alert color="info" %}} You get an invite only when someone invites you to an app from a different company. If someone invites you to an app from your company, you will be added automatically. diff --git a/content/en/docs/deployment/_MAPPING.txt b/content/en/docs/developerportal/deploy/_MAPPING.txt similarity index 100% rename from content/en/docs/deployment/_MAPPING.txt rename to content/en/docs/developerportal/deploy/_MAPPING.txt diff --git a/content/en/docs/deployment/_index.md b/content/en/docs/developerportal/deploy/_index.md similarity index 96% rename from content/en/docs/deployment/_index.md rename to content/en/docs/developerportal/deploy/_index.md index a7f0f72ca6b..13716523f05 100644 --- a/content/en/docs/deployment/_index.md +++ b/content/en/docs/developerportal/deploy/_index.md @@ -1,13 +1,10 @@ --- title: "Deployment" -url: /deployment/ -description: "Describes how to deploy Mendix apps to different environments and how to manage those deployments." -weight: 32 +url: /developerportal/deploy/ +description: "Describes the deployment section of Apps navigation pane: how to deploy Mendix apps to different environments and how to manage those deployments." +weight: 10 no_list: false description_list: true -cascade: - - content_type: "Deployment" - - mendix_version: 10 #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. --- diff --git a/content/en/docs/deployment/cloud-foundry-deploy.md b/content/en/docs/developerportal/deploy/cloud-foundry-deploy.md similarity index 90% rename from content/en/docs/deployment/cloud-foundry-deploy.md rename to content/en/docs/developerportal/deploy/cloud-foundry-deploy.md index c30691af345..ce8e802c842 100644 --- a/content/en/docs/deployment/cloud-foundry-deploy.md +++ b/content/en/docs/developerportal/deploy/cloud-foundry-deploy.md @@ -69,7 +69,7 @@ To deploy a Mendix app to Cloud Foundry, you have to configure the settings in S 1. Open Studio Pro, choose the menu option **Run > Edit Cloud Foundry Settings**: - {{< figure src="/attachments/deployment/cloud-foundry-deploy/edit-cf-settings.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings.png" class="no-border" >}} 2. Enter the following in the credentials of the **Edit Cloud Foundry Settings** window: @@ -78,11 +78,11 @@ To deploy a Mendix app to Cloud Foundry, you have to configure the settings in S * **User name** is the name of your account on the platform * **Password** is the password which authenticates your account - {{< figure src="/attachments/deployment/cloud-foundry-deploy/edit-cf-settings-window.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings-window.png" class="no-border" >}} 3. Click **Next**. You will be logged onto the platform. - {{< figure src="/attachments/deployment/cloud-foundry-deploy/edit-cf-settings-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings-details.png" class="no-border" >}} 4. Enter the following details, which will be constrained by the platform account you are using: @@ -95,7 +95,7 @@ To deploy a Mendix app to Cloud Foundry, you have to configure the settings in S 5. Click **Next**. The Cloud Foundry *App* will be created on the platform. Note that this is currently just the environment for the app and will not contain the Mendix app until you have deployed it. - {{< figure src="/attachments/deployment/cloud-foundry-deploy/edit-cf-configure-app.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-configure-app.png" class="no-border" >}} {{% alert color="warning" %}} Your Cloud Foundry environment needs to be configured with the resources needed by the Mendix app. You cannot run your app until it has the resources it needs. @@ -132,11 +132,11 @@ To add a database service to your app, follow these steps: 2. Find the list of services which you can add. This may be in a **Service Marketplace** or you may need to **Add Service** to get a list of services you can add. Note that services are provided to spaces, not to individual apps. 3. Select a database which is supported by Mendix. Supported databases include PostgreSQL, DashDB, Compose For PostgreSQL, ClearDB MySQL, and ElephantSQL (PostgreSQL as a service) - {{< figure src="/attachments/deployment/cloud-foundry-deploy/marketplaces.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/marketplaces.png" class="no-border" >}} 4. Select the plan that fits your needs. Each database will have different plans with, for example, different memory, space, and clustering. These will each have different costs associated with them, but there will usually be a development version which you can use for free. - {{< figure src="/attachments/deployment/cloud-foundry-deploy/db-service-plans.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/db-service-plans.png" class="no-border" >}} 5. Configure the database by setting the following: @@ -144,7 +144,7 @@ To add a database service to your app, follow these steps: * **Space** – the space to which you want to add the instance * **App** – this is the app to which you want to bind this database. That is, the app which is going to store its data in this database. - {{< figure src="/attachments/deployment/cloud-foundry-deploy/db-configure.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/db-configure.png" class="no-border" >}} {{% alert color="info" %}}Different consoles may use slightly different names for these configuration items.{{% /alert %}} @@ -168,7 +168,7 @@ You may need to configure your file store by using environment variables. See th 2. Open the app you want to deploy to Cloud Foundry. 3. Choose the menu option **Run > Run on Cloud Foundry**: - {{< figure src="/attachments/deployment/cloud-foundry-deploy/run-on-cf.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/run-on-cf.png" class="no-border" >}} The Mendix app will now be deployed to the configured Cloud Foundry app and started automatically @@ -181,7 +181,7 @@ After deploying an app from Studio Pro, two variables will be added automaticall * **ADMIN_PASSWORD** – the password of the default admin of your Mendix app. Note that if you haven't changed it in Studio Pro, you will be unable to deploy your app until you change it to something more secure * **DEVELOPMENT_MODE** – *true* by default; this allows the app to be run in the cloud without security being turned on: change it to false to run the app in production -{{< figure src="/attachments/deployment/cloud-foundry-deploy/app-variables.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/app-variables.png" class="no-border" >}} ## 8 Troubleshooting @@ -190,7 +190,7 @@ If you encounter any problems, you should consult the application logs. These ar 1. Navigate to your app in the platform console. 2. Open the **Logs**. -{{< figure src="/attachments/deployment/cloud-foundry-deploy/cf-log.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/cloud-foundry-deploy/cf-log.png" class="no-border" >}} ### 8.1 Cannot Push Project Folder diff --git a/content/en/docs/deployment/deploying-to-mindsphere.md b/content/en/docs/developerportal/deploy/deploying-to-mindsphere.md similarity index 89% rename from content/en/docs/deployment/deploying-to-mindsphere.md rename to content/en/docs/developerportal/deploy/deploying-to-mindsphere.md index 387ed4d6c20..a09ad98bfa1 100644 --- a/content/en/docs/deployment/deploying-to-mindsphere.md +++ b/content/en/docs/developerportal/deploy/deploying-to-mindsphere.md @@ -21,7 +21,7 @@ There are some limitations to what you can do in your Mendix app if it is deploy {{% alert color="info" %}} You can easily copy code examples shown within grey blocks into the clipboard. Hover the cursor over the code block and click the copy button which appears. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/copy-from-documentation.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/copy-from-documentation.png" class="no-border" >}} {{% /alert %}} @@ -60,15 +60,15 @@ Open Studio Pro (version 7.22.2 or above) and follow these steps: 3. Select **Siemens Insights Hub Starter Application** in the search results. 4. Click **Download** to create a new app using this app as the template. - {{< figure src="/attachments/deployment/deploying-to-mindsphere/app-store-download.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-download.png" class="no-border" >}} 5. Open your Mendix Studio Pro and select the Import App Package on the **Open App** dialog. - {{< figure src="/attachments/deployment/deploying-to-mindsphere/import-app-package.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/import-app-package.png" class="no-border" >}} 6. Select you just downloaded starter template package 7. To start the new app, confirm where to store the app, the app name, and the app directory, then click **OK**. - {{< figure src="/attachments/deployment/deploying-to-mindsphere/app-store-download-project.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-download-project.png" class="no-border" >}} ### 3.2 Option B: Customizing an Existing App{#existingapp} @@ -94,7 +94,7 @@ Now that you have your new app, or have imported the Insights Hub modules into a The following items in the SiemensInsightsHubSingleSignOn module need to be configured. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/image2.png" alt="Folder structure of the SiemensInsightsHubSingleSignOn module" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image2.png" alt="Folder structure of the SiemensInsightsHubSingleSignOn module" class="no-border" >}} #### 4.1.1 CockpitApplicationName @@ -140,17 +140,17 @@ If you are using the Siemens Insights Hub Starter Application, this will already If you are are modifying an existing app, you can do this on the *Runtime* tab of the **App** > **Settings** dialog box accessed through the **App Explorer**. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/image4.png" alt="App settings dialog" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image4.png" alt="App settings dialog" class="no-border" >}} ### 4.2 Configuring the Insights Hub OS Bar (SiemensInsightsHubOSBarConnector) Change the OS Bar to show information about the app you are running. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/image10.png" alt="Example of the information in the OS Bar" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image10.png" alt="Example of the information in the OS Bar" class="no-border" >}} This is configured as a JSON object held as the default value of the string constant **Config** in the *SiemensOSBarConfig* module. The imported module has a correctly formatted set of example values. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/image11.png" alt="Dialog for setting the Config constant for the OS Bar" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image11.png" alt="Dialog for setting the Config constant for the OS Bar" class="no-border" >}} Change the JSON to contain appropriate values for the following information: @@ -173,7 +173,7 @@ A Mendix based application for Insights Hub can be deployed to Mendix or to Insi Just click the Publish Button in Mendix Studio Pro. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/runMendixApp.png" alt="Deploy to Mendix" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/runMendixApp.png" alt="Deploy to Mendix" class="no-border" >}} Once your app is deployed you can automatically register the app in your Insights Hub tenant. @@ -194,7 +194,7 @@ To create a Mendix deployment package from your app, do the following: 1. Open your app in Studio Pro. 2. Select **App** > **Create Deployment Package**. - {{< figure src="/attachments/deployment/deploying-to-mindsphere/image13.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image13.png" class="no-border" >}} 3. Select the correct **Development line** and **Revision**. 4. Set the **New version** number and add a **Description** if required. @@ -303,11 +303,11 @@ However, the Auto Registration process is only available on region Europe 1. To start the **Auto Registration** process click the **View** Button in Mendix Studio Pro once your app is deployed to Mendix Cloud. Your default browser will open and your app will start the process. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/AutoRegistrationExplanation.png" alt="AutoRegistrationExplanation" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationExplanation.png" alt="AutoRegistrationExplanation" class="no-border" >}} Click **Start Auto Registration**. The process now tries to figure out on which tenant your app should be registered. Therefore you have to login: -{{< figure src="/attachments/deployment/deploying-to-mindsphere/WebKeyLogin.png" alt="Login to Siemens Digital Industry Software" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/WebKeyLogin.png" alt="Login to Siemens Digital Industry Software" class="no-border" >}} {{% alert color="info" %}} If you have more then one tenant on Insights Hub you will get a list of tenants. Choose the tenant where you want to register your app. @@ -317,7 +317,7 @@ If you have only one tenant on Insights Hub, the process will automatically sele Give a name, internal name, and, optionally, a description in order to register your app. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/AutoRegistrationNameAndDescription.png" alt="AutoRegistrationNameAndDescription" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationNameAndDescription.png" alt="AutoRegistrationNameAndDescription" class="no-border" >}} If you are on a **Developer** tenant you also have to select at least one application role which will be assigned to your account automatically. @@ -325,7 +325,7 @@ On a **Start for Free** tenant the **admin** role will be assigned automatically Click **Register** to start the registration process on your tenant. After a few seconds, a summary page is shown and you are able to navigate directly to your app. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/AutoRegistrationSummary.png" alt="AutoRegistrationSummary" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationSummary.png" alt="AutoRegistrationSummary" class="no-border" >}} {{% alert color="info" %}} The **Auto Registration** process creates application roles and scopes for your app automatically. @@ -377,7 +377,7 @@ To create a new app manually in the Insights Hub launchpad, do the following: {{% alert color="info" %}}These content security policy (CSP) settings are needed to ensure that the Insights Hub OS Bar and the [Mendix Feedback](/appstore/modules/mendix-feedback/) widget are loaded correctly. You may need to set additional CSP settings if you make additional calls to other domains (for example, if you use Google maps from maps.googleapi.com).{{% /alert %}} - {{< figure src="/attachments/deployment/deploying-to-mindsphere/image14.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image14.png" class="no-border" >}} 15. Click **Save** to save these details. 16. Click **Register** to register your app with the Insights Hub launchpad. @@ -393,7 +393,7 @@ To set up the appropriate scopes in Insights Hub, do the following: 3. Associate it with the Insights Hub default roles **user** and/or **admin**. Or associate it with one of your self created Insights Hub roles. Insights Hub supports up to five application roles. 4. Click **Save**. - {{< figure src="/attachments/deployment/deploying-to-mindsphere/image15.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image15.png" class="no-border" >}} {{% alert color="info" %}} If you are using the app template, you should create two scopes, *user* and *admin*. @@ -401,7 +401,7 @@ If you are using the app template, you should create two scopes, *user* and *adm For an explanation of the relationship between Mendix roles and Insights Hub roles, see section [Roles and Scopes](/partners/siemens/mindsphere-module-details/#rolesscopes) in *Insights Hub Module Details*. -{{< figure src="/attachments/deployment/deploying-to-mindsphere/image8.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image8.png" class="no-border" >}} {{% alert color="info" %}} You will also need to use the **Add Core Role** option to add *Core Roles* to your app if it makes calls to Insights Hub. The ones you need to add will depend on which features of Insights Hub you are using. @@ -413,7 +413,7 @@ Once you have created the scopes for your app, you will need to assign them to t 1. Go to **Settings > Roles** from the Insights Hub launchpad. - {{< figure src="/attachments/deployment/deploying-to-mindsphere/image16.png" width="50%" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/deploying-to-mindsphere/image16.png" width="50%" class="no-border" >}} 2. Choose the app role (scope) you want to assign from the list of **Roles**. 3. Click **Edit assignment**. diff --git a/content/en/docs/deployment/docker-deploy/_index.md b/content/en/docs/developerportal/deploy/docker-deploy/_index.md similarity index 91% rename from content/en/docs/deployment/docker-deploy/_index.md rename to content/en/docs/developerportal/deploy/docker-deploy/_index.md index f308de4346e..af293701dbb 100644 --- a/content/en/docs/deployment/docker-deploy/_index.md +++ b/content/en/docs/developerportal/deploy/docker-deploy/_index.md @@ -12,7 +12,7 @@ Docker is an open source container technology. With Mendix, you can use it for s The Docker Buildpack simplifies the creation of Docker images locally, but it falls short in terms of running, managing, and operating them effectively compared to the capabilities offered by Mendix for Private Cloud. Leveraging Mendix for Private Cloud means entrusting the Mendix Operator to automate these essential tasks whenever Kubernetes handles your containers. The following diagram illustrates the disparity between Docker Buildpack and Mendix Operator: -{{< figure src="/attachments/deployment/docker-deploy/dockerbuildpack-vs-mxoperator.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/docker-deploy/dockerbuildpack-vs-mxoperator.png" class="no-border" >}} {{% alert color="info" %}} Mendix suggests that, if you are planning to deploy to your own cloud platform at scale, a better solution for production apps is to use [Mendix for Private Cloud](/developerportal/deploy/private-cloud/). This provides you with structured and tested solutions for integrating with your own cloud infrastructure using comprehensive, automated, native functions, avoiding the need to create your own processes from scratch. @@ -43,7 +43,7 @@ To build the Docker image, follow these steps: 4. Open the **Command Prompt** and navigate to the folder where you unzipped the buildpack. 5. Open your app in Studio Pro and select the menu option **App** > **Show App Directory in Explorer**: - {{< figure src="/attachments/deployment/docker-deploy/create-deployment-package.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/docker-deploy/create-deployment-package.png" class="no-border" >}} 6. Copy the project folder and all its subfolders to the unzipped docker build folder. The project folder needs to be in the same folder as the Docker file, otherwise Docker cannot access it. 7. Execute the following command: @@ -56,7 +56,7 @@ To build the Docker image, follow these steps: A successful build will resemble the output shown below: - {{< figure src="/attachments/deployment/docker-deploy/build-image.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/docker-deploy/build-image.png" class="no-border" >}} {{% alert color="info" %}} You can find much more information and links to relevant Docker documentation in the [Mendix Docker Buildpack](https://github.com/mendix/docker-mendix-buildpack) GitHub repository. diff --git a/content/en/docs/deployment/docker-deploy/run-mendix-docker-image.md b/content/en/docs/developerportal/deploy/docker-deploy/run-mendix-docker-image.md similarity index 100% rename from content/en/docs/deployment/docker-deploy/run-mendix-docker-image.md rename to content/en/docs/developerportal/deploy/docker-deploy/run-mendix-docker-image.md diff --git a/content/en/docs/deployment/docker-deploy/run-mendix-on-kubernetes.md b/content/en/docs/developerportal/deploy/docker-deploy/run-mendix-on-kubernetes.md similarity index 99% rename from content/en/docs/deployment/docker-deploy/run-mendix-on-kubernetes.md rename to content/en/docs/developerportal/deploy/docker-deploy/run-mendix-on-kubernetes.md index a4d0249d4e1..529057903d6 100644 --- a/content/en/docs/deployment/docker-deploy/run-mendix-on-kubernetes.md +++ b/content/en/docs/developerportal/deploy/docker-deploy/run-mendix-on-kubernetes.md @@ -45,7 +45,7 @@ If the application makes use of persistable FileDocument or FileImage entities, This architecture overview shows all the components in the deployment: -{{< figure src="/attachments/deployment/docker-deploy/run-mendix-on-kubernetes/kubernetes.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/docker-deploy/run-mendix-on-kubernetes/kubernetes.png" class="no-border" >}} The deployment of your Mendix app needs the following Kubernetes components: diff --git a/content/en/docs/deployment/general/_index.md b/content/en/docs/developerportal/deploy/general/_index.md similarity index 55% rename from content/en/docs/deployment/general/_index.md rename to content/en/docs/developerportal/deploy/general/_index.md index 6a25cc75f6c..1d4a7cfba60 100644 --- a/content/en/docs/deployment/general/_index.md +++ b/content/en/docs/developerportal/deploy/general/_index.md @@ -2,7 +2,7 @@ title: "General" url: /developerportal/deploy/general/ weight: 5 -description: "Presents an overview of deployment topics that are relevant to more than one platform." +description: "Presents an overview of the Deployment section of Apps navigation pane, focusing on topics that are relevant to more than one platform." #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. --- @@ -12,7 +12,7 @@ Mendix apps can be deployed to many different platforms. Much of the deployment However, several topics relate to multiple platforms. These topics are covered in this section of the documentation instead of in the platform-specific sections. -The subjects covered in this documentation section are as follows: +The subjects covered in the *General* section are as follows: * [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/) * [Secure Outgoing Connections from your Application](/developerportal/deploy/securing-outgoing-connections-from-your-application/) @@ -31,3 +31,32 @@ The time it takes to build your model depends on the complexity of the model and {{% alert color="info" %}} Starting September 1, 2024, your app will need to run Mendix version 8 or above to build a deployment package on the Mendix platform. This applies to all cloud deployment models, including Mendix Cloud, Mendix Cloud Dedicated, Private Cloud, and SAP Cloud. If your app runs on version 7 or below, you will still be able to build a local deployment package from Studio Pro. {{% /alert %}} + +## 3 Managing Your Deployed Apps + +For many of the platforms to which a Mendix app can be deployed, the following pages in the Mendix Portal let you deploy and manage your app: + +* Environments +* Mobile App + +You can access both of these pages via the Mendix Portal’s [navigation pane](/developerportal/#navigation-pane). + +### 3.1 Environments + +For supported platforms, the **Environments** page allows you to review and configure different aspects of your app. It also allows you to deploy to your chosen platform, configure individual environments, and transport your app between staging environments. + +For details on the **Environments** pages for Mendix Cloud, Mendix for Private Cloud, and SAP deployments, see the following pages: + +* Mendix Cloud deployments – [Environments](/developerportal/deploy/environments/) +* Mendix for Private Cloud deployments – [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/#environment-details) +* SAP deployments – [SAP Business Technology Platform](/developerportal/deploy/sap-cloud-platform/#EnvironmentDetails) + +Other platforms are not currently supported on the Mendix **Environments** page; instead, you must go to the relevant platform portal to monitor and configure your environments. + +### 3.2 Mobile App + +On the **Mobile App** page, you can manage and publish your app in mobile app stores. + +Mendix supports Android and iOS. + +For more details, see [Mobile App](/developerportal/deploy/mobileapp/). diff --git a/content/en/docs/deployment/general/deployment-location.md b/content/en/docs/developerportal/deploy/general/deployment-location.md similarity index 99% rename from content/en/docs/deployment/general/deployment-location.md rename to content/en/docs/developerportal/deploy/general/deployment-location.md index a8b2eb5f739..c5c0d234208 100644 --- a/content/en/docs/deployment/general/deployment-location.md +++ b/content/en/docs/developerportal/deploy/general/deployment-location.md @@ -1,7 +1,7 @@ --- title: "Deployment Location" url: /developerportal/deploy/deployment-location/ -weight: 50 +weight: 45 description: "URL considerations for deploying Mendix" --- diff --git a/content/en/docs/deployment/general/licensing-apps-outside-mxcloud.md b/content/en/docs/developerportal/deploy/general/licensing-apps-outside-mxcloud.md similarity index 99% rename from content/en/docs/deployment/general/licensing-apps-outside-mxcloud.md rename to content/en/docs/developerportal/deploy/general/licensing-apps-outside-mxcloud.md index 3c3e0e992e5..abc68045d54 100644 --- a/content/en/docs/deployment/general/licensing-apps-outside-mxcloud.md +++ b/content/en/docs/developerportal/deploy/general/licensing-apps-outside-mxcloud.md @@ -1,7 +1,7 @@ --- title: "Licensing Apps" url: /developerportal/deploy/licensing-apps-outside-mxcloud/ -weight: 50 +weight: 5 description: "How to apply licenses to apps which are outside Mendix Cloud" #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. #NB have left out AWS and Azure Marketplace offerings for now, pending further research. diff --git a/content/en/docs/deployment/general/running-in-iframe.md b/content/en/docs/developerportal/deploy/general/running-in-iframe.md similarity index 99% rename from content/en/docs/deployment/general/running-in-iframe.md rename to content/en/docs/developerportal/deploy/general/running-in-iframe.md index 7b89022d889..b0d7092a381 100644 --- a/content/en/docs/deployment/general/running-in-iframe.md +++ b/content/en/docs/developerportal/deploy/general/running-in-iframe.md @@ -1,7 +1,7 @@ --- title: "Iframes and Running Apps" url: /developerportal/deploy/running-in-iframe/ -weight: 50 +weight: 40 description: "Issues to take into consideration when running apps in an iframe" #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. --- diff --git a/content/en/docs/deployment/general/securing-outgoing-connections-from-your-application.md b/content/en/docs/developerportal/deploy/general/securing-outgoing-connections-from-your-application.md similarity index 84% rename from content/en/docs/deployment/general/securing-outgoing-connections-from-your-application.md rename to content/en/docs/developerportal/deploy/general/securing-outgoing-connections-from-your-application.md index 58430abf49a..8e5331e62db 100644 --- a/content/en/docs/deployment/general/securing-outgoing-connections-from-your-application.md +++ b/content/en/docs/developerportal/deploy/general/securing-outgoing-connections-from-your-application.md @@ -2,7 +2,7 @@ title: "Secure Outgoing Connections from Your App" linktitle: "Secure Outgoing Connections" url: /developerportal/deploy/securing-outgoing-connections-from-your-application/ -weight: 50 +weight: 10 description: "Describes which methods are available for securing connections from your app to the outside world." #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. #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. @@ -20,7 +20,7 @@ There are various methods which are used for securing connections from *back end In some cases, encryption and authentication on connections is unnecessary. In this case unencrypted TCP/UDP based protocols can be used. This means that any data which is sent over this connection could be read if it is intercepted. -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399049.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399049.png" class="no-border" >}} ### Scenario 2 - TLS/HTTPS @@ -30,7 +30,7 @@ Using encryption, data sent and received over the connection cannot be decoded i To connect to the service from Mendix Cloud, the service is exposed on an external IP address and port. If this service is owned by you, it can be firewalled to only allow Mendix Cloud to connect to it. For more information about the IP address ranges of your app in Mendix Cloud, see [Mendix IP Addresses: Outgoing IP](/developerportal/deploy/mendix-ip-addresses/#outgoing). -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399047.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399047.png" class="no-border" >}} ### Scenario 3 - TLS/HTTPS *With Client Certificate Validation* @@ -38,7 +38,7 @@ For additional security, the server can validate the client's identity by checki The rest of the security features of scenario 2 can also be applied. -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399050.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399050.png" class="no-border" >}} ### Scenario 4 - Proxy Server for TLS Offloading @@ -46,13 +46,13 @@ If a back end service owned by you does not support HTTPS out of the box, you ca Migrations of back-end services within the same region can be done transparently by decoupling it from the public address of your service. The app in Mendix Cloud simply connects to an HTTPS endpoint. -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399044.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399044.png" class="no-border" >}} ### Scenario 5 - Proxy Server for TLS Offloading *With Client Certificate Validation* This scenario is identical to scenario 4, with one exception: your app includes a Client Certificate and the proxy server uses this to validate the identity of the app. -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399045.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399045.png" class="no-border" >}} ### Scenario 6 - VPN @@ -71,7 +71,7 @@ The following disadvantages apply: * Connections are added to (virtual) machines, this makes deployment to multi-tenant public-cloud environments based on containerization a challenge * VPN gateways potentially add two more single points of failure -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399048.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399048.png" class="no-border" >}} ### Scenario 7 - SSH Server as a TCP Proxy @@ -79,7 +79,7 @@ For certain deployments (for example, where non-HTTP protocols are used), you ca Setting up an SSH enabled server and setting up a public/private keypair is a trivial task for most system administrators, but it is not as simple and standardized as HTTPS (reverse) proxy servers. When HTTP based protocols are available, scenarios 2 to 5 are preferable. -{{< figure src="/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399052.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399052.png" class="no-border" >}} ## 3 Notes diff --git a/content/en/docs/deployment/general/two-factor-authentication.md b/content/en/docs/developerportal/deploy/general/two-factor-authentication.md similarity index 79% rename from content/en/docs/deployment/general/two-factor-authentication.md rename to content/en/docs/developerportal/deploy/general/two-factor-authentication.md index f887a761a96..20b66e1580c 100644 --- a/content/en/docs/deployment/general/two-factor-authentication.md +++ b/content/en/docs/developerportal/deploy/general/two-factor-authentication.md @@ -1,7 +1,7 @@ --- title: "Two-Factor Authentication" url: /developerportal/deploy/two-factor-authentication/ -weight: 1 +weight: 20 description: "Describes the purpose and functionality of 2FA in the Mendix Portal." #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. --- @@ -12,7 +12,7 @@ Mendix Cloud provides two-factor authentication (2FA) to help secure your accoun This extra layer of authentication is required when you perform sensitive activities on Mendix Cloud nodes, such as deploying packages and handling production data. Actions that require 2FA are indicated by a padlock ({{% icon name="lock" %}}) in [Apps](https://sprintr.home.mendix.com). For example, switching to the production environment requires 2FA. -{{< figure src="/attachments/deployment/general/two-factor-authentication/production.png" max-width=30% alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/production.png" max-width=30% alt="" class="no-border" >}} To use 2FA, you need to have access to your mobile phone and an active session in the Mendix Portal. @@ -22,7 +22,7 @@ To set up 2FA, you first need to perform an action that requires 2FA. For exampl Then, choose one of the two authentication methods: -{{< figure src="/attachments/deployment/general/two-factor-authentication/authenticator-choice.png" max-width=70% alt="" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/authenticator-choice.png" max-width=70% alt="" >}} You can set up either [authentication via SMS](#sms-authentication) or [authentication via an authenticator app](#app-authentication). Instructions for both authentication methods are provided below. @@ -41,21 +41,21 @@ To set up 2FA with SMS, follow this process: 1. Click **Use SMS** in the dialog box that opens the first time you perform an action that requires 2FA. 2. Enter a phone number to which SMS messages can be sent. Click **Send text message**. - {{< figure src="/attachments/deployment/general/two-factor-authentication/setup-sms.png" max-width=70% alt="" >}} + {{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/setup-sms.png" max-width=70% alt="" >}} 3. Check your text messages to retrieve the verification code. Enter the code and click **Activate**. - {{< figure src="/attachments/deployment/general/two-factor-authentication/enter-sms-code.png" max-width=70% alt="" >}} + {{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/enter-sms-code.png" max-width=70% alt="" >}} #### 2.1.2 SMS Authentication Once you have 2FA configured to use SMS, you can use it to complete sensitive operations in the Mendix Portal. When you perform an operation that requires 2FA, you can send an authentication code to your mobile phone. -{{< figure src="/attachments/deployment/general/two-factor-authentication/authentication-sms.png" max-width=70% alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/authentication-sms.png" max-width=70% alt="" class="no-border" >}} Then, authenticate yourself by entering the authentication code from the text message. -{{< figure src="/attachments/deployment/general/two-factor-authentication/please-authenticate.png" max-width=70% alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/please-authenticate.png" max-width=70% alt="" class="no-border" >}} ### 2.2 Authenticating with an Authenticator App{#app-authentication} @@ -68,7 +68,7 @@ To set up 2FA with an authenticator app, follow this process: 1. Click **Use Authenticator** in the dialog box that opens when you use 2FA for the first time. 2. Follow the setup steps outlined in the **Authenticator** dialog box: - {{< figure src="/attachments/deployment/general/two-factor-authentication/authenticator-app-setup.png" max-width=70% alt="" >}} + {{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/authenticator-app-setup.png" max-width=70% alt="" alt="" >}} 1. **Download a client** – Install and open an authenticator app on your mobile phone. 2. **Set up your authenticator** – Add an account in your authenticator app, using the provided key or QR code. @@ -81,7 +81,7 @@ Your account is now secured with 2FA and ready to use. Once you have 2FA configured to use an authenticator app, you can use it to complete sensitive operations in the Mendix Portal. When you perform operations that require 2FA, you can use your authenticator app to get a six-digit code that is valid for 60 seconds. You will need to enter that code in the Mendix Portal to authenticate yourself. -{{< figure src="/attachments/deployment/general/two-factor-authentication/enter-authenticator-code.png" max-width=70% alt="" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/enter-authenticator-code.png" max-width=70% alt="" alt="" >}} ## 3 Changing Your Authentication Method{#change-2fa-method} @@ -89,7 +89,7 @@ To change your 2FA method, phone number, or authenticator app, you need to deact To deactivate your 2FA, go to **User Settings** > [Developer Settings](/community-tools/mendix-profile/user-settings/#dev-settings). Then, in the **Two-Factor Authentication (2FA)** section, click **Deactivate**. -{{< figure src="/attachments/deployment/general/two-factor-authentication/deactivate.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/deactivate.png" alt="" alt="" >}} In the dialog box that opens, confirm that you want to deactivate your 2FA. This sends a verification email to your registered email address; click the **Deactivate 2FA** link in the email to complete the deactivation process. The email link is valid for several minutes; if it expires before you use it, you can repeat this process to get a new link. @@ -97,10 +97,11 @@ In the dialog box that opens, confirm that you want to deactivate your 2FA. This Once your 2FA is deactivated, your Developer Settings will show the following message: -{{< figure src="/attachments/deployment/general/two-factor-authentication/not-configured.png" max-width=70% alt="" >}} +{{< figure src="/attachments/developerportal/deploy/general/two-factor-authentication/not-configured.png" max-width=70% alt="" alt="" >}} You can reactivate your 2FA by triggering any action that requires 2FA. Then, set up your new authentication method using the setup steps outlined on this page. ## 4 Read More +* [Deploy](/developerportal/deploy/) * [Settings](/developerportal/settings/) diff --git a/content/en/docs/deployment/general/version-downgrade-prevention.md b/content/en/docs/developerportal/deploy/general/version-downgrade-prevention.md similarity index 99% rename from content/en/docs/deployment/general/version-downgrade-prevention.md rename to content/en/docs/developerportal/deploy/general/version-downgrade-prevention.md index 0ea574c9bac..4f9aea82b6c 100644 --- a/content/en/docs/deployment/general/version-downgrade-prevention.md +++ b/content/en/docs/developerportal/deploy/general/version-downgrade-prevention.md @@ -1,7 +1,7 @@ --- title: "Version Downgrade Protection" url: /developerportal/deploy/version-downgrade-prevention/ -weight: 50 +weight: 30 description: "What to do if you cannot migrate a Mendix database to an earlier version" #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps. --- diff --git a/content/en/docs/deployment/general/webhooks.md b/content/en/docs/developerportal/deploy/general/webhooks.md similarity index 98% rename from content/en/docs/deployment/general/webhooks.md rename to content/en/docs/developerportal/deploy/general/webhooks.md index ef927568ce5..cd558d5c79c 100644 --- a/content/en/docs/deployment/general/webhooks.md +++ b/content/en/docs/developerportal/deploy/general/webhooks.md @@ -2,7 +2,7 @@ title: "Webhooks" linktitle: "Webhooks" url: /developerportal/deploy/webhooks/ -weight: 10 +weight: 75 description: "Creating a webhook to trigger actions from Mendix Cloud and Mendix for Private Cloud." --- @@ -135,7 +135,7 @@ You can use Mendix to verify your webhook; the [Community Commons](/appstore/mod 1. Prefix this hashed string with the prefix from the webhook signature (for example, `v1,`). 1. Compare the string you have created (the hash and the prefix) with the `webhook-signature` you retrieved from the list of `System.HttpHeader` objects earlier. If the two strings match, then the webhook call is valid. -{{< figure src="/attachments/deployment/webhooks/validation-microflow.png" alt="Completed validation microflow" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/webhooks/validation-microflow.png" alt="Completed validation microflow" class="no-border" >}} ## 5 Package Upload to the Mendix Portal diff --git a/content/en/docs/deployment/mendix-app-on-industrial-edge.md b/content/en/docs/developerportal/deploy/mendix-app-on-industrial-edge.md similarity index 100% rename from content/en/docs/deployment/mendix-app-on-industrial-edge.md rename to content/en/docs/developerportal/deploy/mendix-app-on-industrial-edge.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/_about.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/_about.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/_about.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/_about.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/_index.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/_index.md similarity index 98% rename from content/en/docs/deployment/mendix-cloud-deploy/_index.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/_index.md index 456f229fd8c..d09de510935 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/_index.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/_index.md @@ -47,7 +47,7 @@ Free Apps make it possible to start creating and deploying apps with Mendix for As noted in the table above, a Free App goes into sleep mode after about an hour of inactivity. If you access the app while it is inactive, it displays the following message: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/appresumed.png" alt="A Resuming app message" width=60% class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/appresumed.png" alt="A Resuming app message" width=60% class="no-border" >}} If, after a couple of minutes, your app does not wake up, contact [Mendix Support](https://support.mendix.com). @@ -78,7 +78,7 @@ If the standard environments that you get with a licensed app do not meet your r Apps deployed to Mendix Cloud are configured to use a PostgreSQL database. It is not possible to configure your app to use an alternative database if it is deployed to Mendix Cloud. -If you need to use a different database, consider deploying your app to a different platform. For more information, see [Deployment](/deployment/). +If you need to use a different database, consider deploying your app to a different platform. For more information, see [Deployment](/developerportal/deploy/). ### 1.4 URLs and Ports diff --git a/content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/access-restrictions.md similarity index 83% rename from content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/access-restrictions.md index 3b244eb710e..b552fed2fbe 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/access-restrictions.md @@ -19,7 +19,7 @@ You can specify multiple different access restriction profiles for your applicat Click **New** to create a new access restriction profile. Select an existing profile and click **Edit** to modify it, **Clone** to copy it, or **Delete** to delete it. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/access-restriction-profiles.png" alt="The Access Restriction Profiles tab" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/access-restriction-profiles.png" alt="The Access Restriction Profiles tab" class="no-border" >}} When configuring an access restriction profile, keep the following considerations in mind: @@ -31,7 +31,7 @@ When configuring an access restriction profile, keep the following consideration To view the page where you can configure an access restriction profile, click **New** to create a new profile or **Edit** to modify an existing profile. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/v4-access-restriction-profile.png" alt="The access restriction profile editing page" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/v4-access-restriction-profile.png" alt="The access restriction profile editing page" class="no-border" >}} Add IP ranges and certificate profiles as described below, then click **Save** to save the access restriction profile. @@ -53,7 +53,7 @@ Your CA must contain a single root certificate and can have multiple intermediat Once the CA is uploaded, you will see a tree containing the root certificate and any intermediate certificates included in the CA. When you upload a CA, the last certificate in the CA will be selected by default. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/ca-profile.png" alt="Certificate authority profile" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/ca-profile.png" alt="Certificate authority profile" class="no-border" >}} Select the checkbox next to each intermediate or root certificate you want to use. Client certificates will be accepted if they are signed by any selected certificate. If you select more than one certificate in a branch, the client certificate will be accepted if it is signed by any of the selected certificates. @@ -69,7 +69,7 @@ You can specify a number of different IP ranges. Click **Create** to add a new I For each IP range, you can specify a **Name** for the range and a range of addresses. Mendix Cloud supports both IPv4 and IPv6 format addresses. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/ip-range.png" alt="Edit IP Range dialog box" width=60% class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/ip-range.png" alt="Edit IP Range dialog box" width=60% class="no-border" >}} ## 3 Applying a Restriction to an Application Environment @@ -109,19 +109,19 @@ To restrict access to the app to an IP range, follow these steps: 1. From [Apps](https://sprintr.home.mendix.com), go to the app's **Environments** page. 2. Switch to the **Access Restriction Profiles** tab. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/app-restriction.png" alt="The Access Restriction Profiles tab" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/app-restriction.png" alt="The Access Restriction Profiles tab" class="no-border" >}} 3. Create an access restriction profile. 4. Add one or more IP ranges to the access restriction profile. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/scenario1.png" alt="IP ranges added to the access restriction profile" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/scenario1.png" alt="IP ranges added to the access restriction profile" class="no-border" >}} 5. Save the access restriction profile. 6. Go to the **Deploy** tab of the **Environments** page. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment. 7. Switch to the **Network** tab. 8. Select the top-level path (`/`) and click **Edit**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/environment-restriction.png" alt="The Edit Path Range Access Restriction dialog box" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/environment-restriction.png" alt="The Edit Path Range Access Restriction dialog box" class="no-border" >}} {{% alert color="info" %}}Any path below this path that does not have an explicit restriction will inherit this access restriction profile.{{% /alert %}} @@ -142,7 +142,7 @@ To add this additional access restriction profile, follow these steps: 1. Go to the **Access Restriction Profiles** tab of the **Environments** page. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/app-restriction.png" alt="The Access Restriction Profiles tab" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/app-restriction.png" alt="The Access Restriction Profiles tab" class="no-border" >}} 2. Create a new access restriction profile. 3. Upload the certificate of the internal CA that is used to sign the client certificates. @@ -151,7 +151,7 @@ To add this additional access restriction profile, follow these steps: 6. Switch to the **Network** tab. 7. Edit the `/ws/` path of the environment to apply the new access restriction profile. This overrides the default profile (for the top level `/`) for the selected path (`/ws/`). - {{< figure src="/attachments/deployment/mendix-cloud-deploy/access-restrictions/environment-restriction-2.png" alt="The Edit Path Range Access Restriction dialog box" width=75% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/environment-restriction-2.png" alt="The Edit Path Range Access Restriction dialog box" width=75% class="no-border" >}} {{% alert color="info" %}} If the `/ws/` path should still be reachable from the office location without using a client certificate, add the IP ranges of the office location to the profile used for `/ws/`. @@ -160,6 +160,6 @@ If the `/ws/` path should still be reachable from the office location without us ## 5 Read More * [Certificates](/developerportal/deploy/certificates/) -* [Deployment](/deployment/) +* [Deployment](/developerportal/deploy/) * [Environments](/developerportal/deploy/environments/) * [Environment Details](/developerportal/deploy/environments-details/) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/_index.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/_index.md similarity index 97% rename from content/en/docs/deployment/mendix-cloud-deploy/backups/_index.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/_index.md index 55f2ea9e19a..bf162a3c9fb 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/_index.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/_index.md @@ -67,7 +67,7 @@ The monthly backup occurs on the first Sunday of the month. If the first nightly The **Backups** page presents options for managing your backups. These are described below. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/backup-controls.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/backup-controls.png" alt="" class="no-border" >}} ### 3.1 Create Backup @@ -133,7 +133,7 @@ You can view details of a backup by clicking **More Options** ({{% icon name="th | **Snapshot Size Uncompressed (MB)** | The size of database dump and files of the snapshot in MB | | **Comment** | A comment added to the backup | -{{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/backup-details.png" alt="Backup Details" max-width=60% class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/backup-details.png" alt="Backup Details" max-width=60% class="no-border" >}} ## 4 Data Location {#data-location} diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/create-backup.md similarity index 87% rename from content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/create-backup.md index a0e1dd0f015..d3463cd246f 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/create-backup.md @@ -29,11 +29,11 @@ To create a backup archive of a licensed app, follow these steps: 1. Click **Backups** in the navigation pane. 1. Select the environment for which you want to create a backup snapshot. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/environment.png" width=25% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/create-backup/environment.png" width=25% class="no-border" >}} 1. Click **Create Backup**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backupoptions.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/create-backup/backupoptions.png" class="no-border" >}} Once you have created a backup archive, you can download it by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) > **Download**. For more information, see [Downloading a Backup](/developerportal/operate/download-backup/). diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/database-size-reduction.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/database-size-reduction.md similarity index 93% rename from content/en/docs/deployment/mendix-cloud-deploy/backups/database-size-reduction.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/database-size-reduction.md index a6886799020..bdcedd972d2 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/database-size-reduction.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/database-size-reduction.md @@ -10,7 +10,7 @@ description: "Describes how to restore physical disk space by creating and resto Usually, the database of a Mendix application in Mendix Cloud grows over time. Here is a typical example: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/database-size-reduction/Untitled.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/database-size-reduction/Untitled.png" class="no-border" >}} The data grows in a steady fashion. If entities are removed in a major release, you may see a temporary decrease in the size of the database—but on average, the database size tends to increase over time. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/download-backup.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/download-backup.md similarity index 85% rename from content/en/docs/deployment/mendix-cloud-deploy/backups/download-backup.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/download-backup.md index 7935d2f37d8..5cf49a0eb6f 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/download-backup.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/download-backup.md @@ -35,16 +35,16 @@ To download a backup of a licensed app, follow these steps: 1. In the navigation pane, click **Backups**. 1. Select the environment from which you want to download the backup. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/download-backup/environment.png" width="25%" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/environment.png" width="25%" class="no-border" >}} 1. If you want to create a backup first, click **Create Backup**. 1. On the backup you want to download, click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}). Select **Download** from the drop-down list. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/download-backup/backupoptions.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/backupoptions.png" class="no-border" >}} 1. Select the backup type: **Full snapshot**, **Database only**, or **Files only**. Then click **Start**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/download-backup/backup-choice.png" alt="" width=75% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/backup-choice.png" alt="" width=75% class="no-border" >}} {{% alert color="info" %}}If a backup archive has been prepared recently, the **Show URL** and **Download** buttons will be active. In this case, you can download the backup archive immediately.{{% /alert %}} diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup-locally.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally.md similarity index 83% rename from content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup-locally.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally.md index 1643b95dea4..72ef6860e94 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup-locally.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally.md @@ -44,19 +44,19 @@ If you have downloaded a full backup, this will also have been archived as a *.t 2. Click the **+** in the **Browser** pane to open the **Servers > PostgreSQL 9.6** menu. 3. Right-click **Databases** and **Create** a new database. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/add-database.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/add-database.png" class="no-border" >}} 4. Fill in the **Database** name. 5. Select the correct owner (the default is **postgres**) and click **Save**. 6. Right-click the newly created database and click **Restore**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/restore-database.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/restore-database.png" class="no-border" >}} 7. Select the **.backup** file you downloaded from the Team Server. 8. Click the **Restore options** tab. 9. Under **Do not save**, set **Owner** to **Yes**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/restore-options.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/restore-options.png" class="no-border" >}} 10. Click **Restore**. 11. Wait until you see a message that the backup is "Successfully completed." This message appears in the right corner of the screen. @@ -68,11 +68,11 @@ After the backup has been restored as a local Postgres database, you have to lin 1. Open your app in **Studio Pro**. 2. Open **App > Settings** from the **App Explorer**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/app-settings.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/app-settings.png" class="no-border" >}} 3. Under the tab **Configurations**, click **New**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/add-configuration.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/add-configuration.png" class="no-border" >}} 4. Fill in the database information: * **Name**: *{a unique name}* @@ -97,11 +97,11 @@ If you also want to restore the **FileDocuments**, follow these steps: 1. Download a **Full Snapshot**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/backup-choice.png" width=75% alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/backup-choice.png" width=75% alt="" class="no-border" >}} 2. Select **App** > **Show App Directory in Explorer** from the Studio Pro menu: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/project-directory.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/project-directory.png" class="no-border" >}} 3. Navigate to the **deployment/data/files** folder within your app. 4. Extract the *{backup name}.tar* file from the *.gz* archive using a program like **7-zip**. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup.md similarity index 94% rename from content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup.md index c8100da6dde..5de11ddc6db 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup.md @@ -42,15 +42,15 @@ If you want to restore a backup to a different cloud node, or have your backup s 1. Use the navigation panel to go to your app's **Backups** page. 1. In the upper-right corner of the screen, select the environment to which the backup should be restored (for example, **Acceptance**). - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/environment.png" width=25% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/environment.png" width=25% class="no-border" >}} 1. On the backup you want to restore, click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) and select **Restore** from the drop-down list. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/backupoptions.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/backupoptions.png" class="no-border" >}} 1. Confirm the backup restore by clicking **Restore Backup**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/restore-backup.png" alt="" width=60% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/restore-backup.png" alt="" width=60% class="no-border" >}} {{% alert color="info" %}} If the app is still running, you have to stop it by clicking **Stop Application**. Then click **Restore Backup** again. @@ -123,7 +123,7 @@ The *.tar* archive within the *.tar.gz* archive (for example, *files_and_databas Here is an example: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/tar-gz-structure.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/tar-gz-structure.png" class="no-border" >}} This contains the following files: diff --git a/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/behavior-of-app.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/behavior-of-app.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/certificates.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/certificates.md similarity index 95% rename from content/en/docs/deployment/mendix-cloud-deploy/certificates.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/certificates.md index 92878d83375..3a579553efe 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/certificates.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/certificates.md @@ -66,13 +66,13 @@ You can upload a PKCS12 file by following these steps: 1. Select the **Network** tab of an application environment. 1. Below **Outgoing Connections Certificates**, click **Add Client Certificate**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/certificates/certificate.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/certificates/certificate.png" class="no-border" >}} 1. Upload the client certificate as a PKCS12 (pfx) container. 1. Enter the password to unlock the certificate container. 1. If you are using a custom certificate when setting your Client certificate in your [Call REST Service](/refguide/call-rest-action/#client-certificate) or [Call Web Service](/refguide/call-web-service-action/#client-certificate) action, set a **Web Service Call Name** and use it to pin the certificate by setting the call's **Client certificate identifier** to the **Web Service Call Name**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/certificates/certificate-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/certificates/certificate-details.png" class="no-border" >}} {{% alert color="info" %}} Changes to certificate settings do not go into effect until you restart the app. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/custom-domains.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/custom-domains.md similarity index 87% rename from content/en/docs/deployment/mendix-cloud-deploy/custom-domains.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/custom-domains.md index 9cc56383a11..69ec24ef143 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/custom-domains.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/custom-domains.md @@ -68,14 +68,14 @@ You can have more than one certificate for an application. For example, when you You can choose which certificate to use when you configure a custom domain for an environment (test, acceptance, or production). -{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/app-env-certificates.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/app-env-certificates.png" class="no-border" >}} To manage custom domains, follow these steps: 1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app. 1. Switch to the **Custom Domains** tab. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domains-tab.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/custom-domains-tab.png" class="no-border" >}} If you already have a signed SSL/TLS certificate, skip to [Uploading Your Own Custom Domain Certificate](#Uploading), below. @@ -95,17 +95,17 @@ To create a CSR and an RSA (Rivest–Shamir–Adleman) encryption key, follow th 2. Click **Create a Certificate Request**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-custom-domain.png" alt="" width=75% >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-custom-domain.png" alt="" width=75% >}} 3. Fill in the required fields. 4. Click **Generate**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/generate-cert-req.png" width=60% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/generate-cert-req.png" width=60% class="no-border" >}} An SSL/TLS private key and a certificate request is generated. The certificate request will be shown in PEM (Privacy-Enhanced Mail) format. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/pem-format.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/pem-format.png" class="no-border" >}} {{% alert color="info" %}}The SSL/TLS private key will be hidden after you upload it. To keep the key secure, it will be stored in Mendix Cloud's secure keystore; it will not be available for download, and it cannot be obtained by Mendix Support.{{% /alert %}} @@ -119,7 +119,7 @@ Once you have a signed SSL/TLS certificate, you can upload it by following these 2. Click **Upload Signed Certificate**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate.png" class="no-border" >}} 3. Add a **Description** of your certificate. @@ -127,7 +127,7 @@ Once you have a signed SSL/TLS certificate, you can upload it by following these 5. Paste an **Intermediate Certificate Chain**. This is optional, but highly recommended. The intermediate certificate chain is provided by your certificate authority. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/signed-certificate.png" width=80% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/signed-certificate.png" width=80% class="no-border" >}} {{% alert color="warning" %}}The intermediate certificates of the main certificate authorities are included in the built-in CA databases of modern browsers. Therefore, you do not need to include an intermediate certificate to serve your website through SSL/TLS to users of modern browsers. However, you cannot predict how your users will attempt to connect to your website; not including an intermediate certificate may result in connection issues for some users. Tools such as cURL do not recognize intermediate certificates automatically. Because of this, intermediate certificates are highly recommended but optional.{{% /alert %}} @@ -147,7 +147,7 @@ To upload the custom domain certificate, follow these steps: 2. Click **Upload Certificate, Chain and Key**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-custom-domain.png" width=75% alt="" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-custom-domain.png" width=75% alt="" >}} 3. Type a **Description** for the certificate. @@ -157,7 +157,7 @@ To upload the custom domain certificate, follow these steps: 6. Paste an **Intermediate Certificate Chain**. This is optional, but most browsers require it. The intermediate certificate chain is provided by your certificate authority. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-certificate.png" width=60% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-certificate.png" width=60% class="no-border" >}} 7. Click **Save** to save your new custom domain certificate. It will be uploaded to Mendix Cloud automatically. @@ -167,7 +167,7 @@ You can now configure your custom domain. For details, see [Configuring a Custom You can add as many certificates as you need. Each certificate will be listed with the description you gave it. Make sure to give them meaningful names so that you can identify them easily. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-list.png" alt="List of certificates" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate-list.png" alt="List of certificates" class="no-border" >}} ## 6 Renewing a Custom Domain Certificate @@ -195,7 +195,7 @@ If you are rotating a certificate, you do not need to remove the current domain You can also edit an existing custom domain certificate. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-edit.png" alt="Edit a certificate" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate-edit.png" alt="Edit a certificate" class="no-border" >}} {{% alert color="warning" %}} For this, you need access to the certificate request that you created for the current certificate. @@ -211,11 +211,11 @@ To configure a custom domain for your application environment, follow these step 2. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the environment you want to configure. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/environment-details.png" alt="The Details icon" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/environment-details.png" alt="The Details icon" >}} 3. Go to the **Network** tab. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/network.png" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/network.png" >}} 4. In the **Custom Domains** section, you can manage your custom domains. @@ -227,7 +227,7 @@ To configure a custom domain for your application environment, follow these step 8. Click **Save** to save your custom domain. It will be configured for your application environment automatically. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domain.png" alt="" width=80% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/custom-domain.png" alt="" width=80% class="no-border" >}} {{% alert color="info" %}} Make sure you have configured a CNAME record for your custom domain with your domain registrar/DNS provider (for details, see [Create and Configure a CNAME Record](#DNS)), above. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/deploying-to-mendix-cloud.md similarity index 92% rename from content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/deploying-to-mendix-cloud.md index 49efc5ec4a0..90be979ae07 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/deploying-to-mendix-cloud.md @@ -80,12 +80,12 @@ The previous steps explained how to deploy a deployment package to Mendix Cloud, 1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app. 1. In the **Deployment Package Repository**, choose your preferred deployment package and click **Deploy** ({{% icon name="deploy" %}}). - {{< figure src="/attachments/deployment/mendix-cloud-deploy/deploy-package.png" alt="" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/deploy-package.png" alt="" >}} 1. Select the environment to which you want to deploy the package. 1. Click **Transport**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/transport-to-flex.png" alt="The Transport menu" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/transport-to-flex.png" alt="The Transport menu" >}} 1. If prompted, clean the environment. 1. Review the [constants](/refguide/constants/) in the **Constants** tab. Double-click any constant to view more details and edit the value if desired. @@ -113,11 +113,11 @@ With a Free App, you can deploy your app to Mendix Cloud from Studio Pro by usin * In the top bar of Studio Pro, click **Run** > **Publish**. This automatically deploys your app to a Free App environment. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/runapp2.png" alt="The Run menu with the Publish option selected" max-width=60% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/runapp2.png" alt="The Run menu with the Publish option selected" max-width=60% class="no-border" >}} * Alternatively, in the top bar of Studio Pro, click **Publish**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/runapp.png" alt="The Publish button" max-width=20% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/runapp.png" alt="The Publish button" max-width=20% class="no-border" >}} ## 4 Deployment Status and Troubleshooting diff --git a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments-details.md similarity index 91% rename from content/en/docs/deployment/mendix-cloud-deploy/environments-details.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments-details.md index 60996718b32..aa510c9587b 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments-details.md @@ -12,7 +12,7 @@ description: "Describes the environmental details of your app and how to manage To open the **Environment Details** page, go to [Apps](https://sprintr.home.mendix.com) and click **Environments** on your licensed app. Then click **Details** ({{% icon name="notes-paper-edit" %}}) by the environment you want to view. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/environment-details.png" alt="The Details icon is on the right side of the row" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/environment-details.png" alt="The Details icon is on the right side of the row" >}} {{% alert color="info" %}}You must have permissions for **Transport Rights** or **Access to Monitoring** to view the **Environment Details** page. For details on configuring permissions, see [Node Permissions](/developerportal/deploy/node-permissions/).{{% /alert %}} @@ -52,7 +52,7 @@ On the right side of the screen in the **General** tab, there are buttons that y When your app is running, you can see the following action buttons: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/actions-v5.png" alt="Available actions when the app is running" max-width=40% class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/actions-v5.png" alt="Available actions when the app is running" max-width=40% class="no-border" >}} * **Restart Application** – This stops the running application and starts it again. Restarting your app is required for applying new constant values or scheduled events to the environment. * **Stop Application** – This stops the application. @@ -64,7 +64,7 @@ When your app is running, you can see the following action buttons: When your app is stopped, you see this set of action buttons instead: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/actions-stopped.png" alt="Available actions when the app is stopped" max-width=40% class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/actions-stopped.png" alt="Available actions when the app is stopped" max-width=40% class="no-border" >}} * **Start Application** – This starts the application. * **Stop Application** – This stops the application. @@ -92,7 +92,7 @@ To clear your environment, follow these steps: 3. Confirm that you want to clear your environment by typing the indicated text (*clear database* or *clear model and database*, depending on which option you selected). 4. Click **Clear Environment**. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/clear-environment.png" +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/clear-environment.png" alt="Clear Environment options and confirmation" max-width=70% >}} @@ -117,11 +117,11 @@ After you rename an environment, it may take up to 15 minutes before you can acc To see the options for changing scaling, scroll down to the **Instances** section of the **General** tab and click **Change scaling**. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/change-scaling.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/change-scaling.png" alt="" class="no-border" >}} In the **Change scaling** dialog box, there are two sliders that you can control: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/scale.png" alt="A sample view of the Scaling page" width=400 class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/scale.png" alt="A sample view of the Scaling page" width=400 class="no-border" >}} * Use the **Instances** slider to increase or decrease the number of instances * The instances are meant for improved resiliency and increased processing power @@ -166,7 +166,7 @@ The license overview contains the following information: On this tab, you can edit the following model options: scheduled events and constants. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/model-options.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/model-options.png" class="no-border" >}} ### 3.1 Scheduled Events @@ -192,7 +192,7 @@ In the **Edit Constant** dialog box, you can change the constant value using the You can also set **Mask** to **Yes**. This changes the display settings for **Current value** and **New value**; if masking is enabled, all screens in the Mendix Portal (and in Excel if you export the constants) conceal these values and display a string of asterisks in their place. This lets you keep your constants secret from users who do not have edit rights. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/edit-constant.png" alt="Edit Constants Pop-up window" width="60%" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/edit-constant.png" alt="Edit Constants Pop-up window" width="60%" class="no-border" >}} {{% alert color="info" %}} For the changes to take effect, you must restart your application. @@ -208,7 +208,7 @@ For more information, see [Constants](/refguide/constants/). On the **Network** tab, you can manage the elements described below. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/network1.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/network1.png" alt="" class="no-border" >}} ### 4.1 Custom Domains {#custom-domains} @@ -249,15 +249,15 @@ There are three types of values for these headers: * Choose a value from a drop-down menu: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-dropdown.png" alt="Selecting a value" width=350 class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-dropdown.png" alt="Selecting a value" width=350 class="no-border" >}} * Choose a value from a drop-down menu and specify a URL: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-url.png" alt="Specifying a URL" width=350 class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-url.png" alt="Specifying a URL" width=350 class="no-border" >}} * Enter the required values as a string: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-string.png" alt="Entering a value" width=350 class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-string.png" alt="Entering a value" width=350 class="no-border" >}} The changes to the headers are implemented when the app is redeployed. @@ -326,7 +326,7 @@ If you have issues that appear to be related to a content security policy, you c ### 4.3 Outgoing Connections Safelisting (Mendix Cloud Dedicated) {#connection-safelist} -If you are deploying your apps to [Mendix Cloud Dedicated](/deployment/#mendix-cloud-dedicated), all outgoing IP addresses are allowed by default. +If you are deploying your apps to [Mendix Cloud Dedicated](/developerportal/deploy/#mendix-cloud-dedicated), all outgoing IP addresses are allowed by default. If you clear the **Allow all outgoing connections** checkbox, you can define which IP addresses and ports can be used for outgoing connections. @@ -392,14 +392,14 @@ Add client certificates (in the PKCS12 format) or certificate authorities (in th Log levels are used to distinguish the log messages. Log levels highlight the highest-priority log messages so that they can be prioritized accordingly. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/loglevels-tab.png" alt="Viewing the log levels" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/loglevels-tab.png" alt="Viewing the log levels" class="no-border" >}} Custom log nodes appear in the list only after a message has been logged to them. For more information, see [Log Message](/refguide/log-message/#log-node-name). On this tab, you can perform the following actions: * Change the log level by selecting a node, clicking **Change level**, and modifying the level in the **Change log level** dialog box - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/loglevels.png" alt="Selecting the log level type" width=50% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/loglevels.png" alt="Selecting the log level type" width=50% class="no-border" >}} * Click **Set all to Info** to revert all the changes When using the **Log Levels** tab, bear in mind the following considerations: @@ -429,7 +429,7 @@ For more information about log levels, see [How to Set Log Levels](/howto/monito On the **Runtime** tab, you can add **Custom Runtime Settings** and **Custom Environment Variables**. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/runtime.png" alt="Viewing the Runtime tab" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/runtime.png" alt="Viewing the Runtime tab" class="no-border" >}} ### 6.1 Custom Runtime Settings {#custom-runtime-settings} @@ -492,7 +492,7 @@ To support features that are in beta, click **Add** and select **Unsupported**. You can use the **Maintenance** tab to view information about planned maintenance. You can also configure your preferred maintenance window. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/maintenance.png" alt="Viewing the Maintenance tab" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/maintenance.png" alt="Viewing the Maintenance tab" class="no-border" >}} There are two types of maintenance: @@ -513,7 +513,7 @@ When a maintenance operation is planned, it appears under **Planned Maintenance* You can set tags on your environment. Tags are arbitrary strings that are not interpreted by the Mendix Portal. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details/tags.png" alt="Viewing the Tags tab" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/tags.png" alt="Viewing the Tags tab" class="no-border" >}} Tags serve two purposes: diff --git a/content/en/docs/deployment/mendix-cloud-deploy/environments.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments.md similarity index 93% rename from content/en/docs/deployment/mendix-cloud-deploy/environments.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments.md index 4d3f624b4df..d2078868ae4 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/environments.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments.md @@ -26,7 +26,7 @@ In the **Deploy** tab, you can view information about your environments. You can The **Deployment Package Repository** section has an overview of your deployment packages. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments/deployment-package.png" alt="The Deployment Package Repository section" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deployment-package.png" alt="The Deployment Package Repository section" >}} You can perform the following actions in this section: @@ -46,14 +46,14 @@ You can also see information and perform actions on the existing deployment pack To deploy a package, transporting it from the Team Server to an environment where you can run your app, click **Deploy** ({{% icon name="deploy" %}}). -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments/deploy-icon.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deploy-icon.png" alt="" >}} If you click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) on a package, you can do the following: * View details, including the package size, description, build output, and an overview of the environments that are running the package * Delete the package -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments/deployment-package-options.png" alt="More Options" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deployment-package-options.png" alt="More Options" >}} ### 2.2 Environments @@ -82,7 +82,7 @@ You can perform the following actions in this section: * View an environment's details – Click **Details** ({{% icon name="notes-paper-edit" %}}) to go to the [Environment Details](/developerportal/deploy/environments-details/) page. * Transport an environment – If you have [Transport rights](/developerportal/deploy/node-permissions/#transport-rights) enabled, you will see a **More Options** button ({{% icon name="three-dots-menu-horizontal" %}}) that you can click to stage an environment to acceptance or production. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments/transport-to.png" alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments/transport-to.png" alt="" class="no-border" >}} * Set up deployment – If you are the [Technical Contact](/developerportal/general/app-roles/#technical-contact), you will see a **Setup Studio Pro Deployment** button. You can use this to set the target environment to which apps are deployed from Studio Pro; for more information, see [Studio Pro Deployment Settings](/developerportal/deploy/studio-deployment-settings/). @@ -113,7 +113,7 @@ You can perform the following actions in this section: * Set up deployment – If you are the [Technical Contact](/developerportal/general/app-roles/#technical-contact), you will see a **Setup Studio Pro Deployment** button. You can use this to set the target environment to which apps are deployed from Studio Pro; for more information, see [Studio Pro Deployment Settings](/developerportal/deploy/studio-deployment-settings/). * Reorder environments – If you are the Technical Contact, you can reorder the environments by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) and selecting **Move Up** or **Move Down**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments/reorder-environments.png" alt="Move Up and Move Down options" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments/reorder-environments.png" alt="Move Up and Move Down options" >}} {{% alert color="info" %}}The button to transport an environment is not available when flexible environments are enabled. This is because you must choose your deployment target each time you deploy when you have flexible environments. To deploy, click **Deploy** ({{% icon name="deploy" %}}) in the [Deployment Package Repository](/developerportal/deploy/environments/#package-repository) section, as described above.{{% /alert %}} @@ -121,7 +121,7 @@ You can perform the following actions in this section: In the **Activity** section, you can view a log of deployment activities performed on your environments. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments/activity.png" alt="Sample activity log" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/environments/activity.png" alt="Sample activity log" >}} {{% alert color="info" %}} Operations performed on a customer's behalf through an authorized Mendix support ticket are not logged in the activity log. @@ -169,7 +169,7 @@ Once a service has been enabled for an app, Technical Contacts can selectively e ## 7 Read More -* [Deployment](/deployment/) +* [Deployment](/developerportal/deploy/) * [Environment Details](/developerportal/deploy/environments-details/) * [How to Receive Environment Status Alerts](/developerportal/operate/receive-alerts/) * [How to Restrict Access for Incoming Requests](/developerportal/deploy/access-restrictions/) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/_index.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/_index.md similarity index 91% rename from content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/_index.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/_index.md index 5ac9ba6bbdc..f5bcb970679 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/_index.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/_index.md @@ -107,15 +107,15 @@ To unlink a Free App, do the following: 1. If the page shows the following message, then your app is not currently linked to a node. In that case, you can go straight to the [Connecting Your App to a Licensed Node](#connect-app) section. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/link-node.png" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/link-node.png" >}} 1. Click **Unlink your app**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/unlink-free-app.png" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/unlink-free-app.png" >}} 1. Click **Yes, delete all data and unlink this app** to confirm. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/confirm-unlink.png" max-width=70% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/confirm-unlink.png" max-width=70% class="no-border" >}} 1. If prompted, authenticate yourself with [two-factor authentication](/developerportal/deploy/two-factor-authentication/). @@ -149,15 +149,15 @@ To connect your app to a licensed node, do the following: 1. Click **Select a node**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/link-node.png" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/link-node.png" >}} 1. Click **Use this Node**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/choose-node.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/choose-node.png" class="no-border" >}} 1. If there is already an app linked to the node, you will be prompted to confirm that you want to replace it. Click **Continue** to confirm. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/confirm-replace.png" max-width=70% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/confirm-replace.png" max-width=70% class="no-border" >}} 1. If prompted, authenticate yourself with [two-factor authentication](/developerportal/deploy/two-factor-authentication/). @@ -195,7 +195,7 @@ To link **App A** to **Node 2** and **App B** to **Node 1**, follow these steps: 4. **App B** no longer has a node. So, you can link **App B** to **Node 1**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/exchange-apps.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/exchange-apps.png" class="no-border" >}} You have now swapped **App A** and **App B** between nodes. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/basic-package.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package.md similarity index 92% rename from content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/basic-package.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package.md index 70fc5318cd6..1b11e2721e9 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/basic-package.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package.md @@ -40,7 +40,7 @@ From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of When you view your Free App environment, you will see a banner showing that you are using a Free App. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/free-app-message.png" alt="Free App banner" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/free-app-message.png" alt="Free App banner" class="no-border" >}} To order your Mendix Basic package, do the following: @@ -55,7 +55,7 @@ To order your Mendix Basic package, do the following: * **Deployment Region** – Choose your preferred region. Mendix recommends selecting the region where you expect to receive the most visitors. The available regions correspond to AWS regions. * **Number of Users** – The cost of your Basic package depends on the number of users. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/configure-basic-package.png" alt="Configuration screen" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/configure-basic-package.png" alt="Configuration screen" class="no-border" >}} You can see a summary of your Basic package on the right side of the screen. @@ -98,7 +98,7 @@ Your plan automatically renews 12 months from the date of provision. You can opt Before renewing the licenses for your company, Mendix checks if your company's payment method is still valid. If it is expired, you will receive an email that asks you to update your company's payment method on the **Billing Accounts** page. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/billing-accounts-page.png" alt="billing accounts page" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/billing-accounts-page.png" alt="billing accounts page" class="no-border" >}} The **Billing Accounts** page shows the details of your company's existing billing accounts. These accounts are on the company level. If your company has multiple billing accounts, you can select a billing account from the drop-down list on the page. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic.md similarity index 84% rename from content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic.md index dc7f7aec5cc..075ce5f19e3 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic.md @@ -40,7 +40,7 @@ To migrate your Free App and its database to your Mendix Basic environment, foll 1. Make sure **Full Snapshot** is selected, then click **Start** to prepare the download. 1. Once the backup is ready, click **Download**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/download-backup.png" alt="" width=75% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/download-backup.png" alt="" width=75% class="no-border" >}} 1. Close the **Download Backup** dialog box. @@ -50,15 +50,15 @@ To migrate your Free App and its database to your Mendix Basic environment, foll 1. Click **Unlink your app**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/unlink-free-app.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/unlink-free-app.png" class="no-border" >}} If you see the following message, your app has already been unlinked. In that case, you can skip ahead to [Link Your App to the New Node](#link-app-to-node). - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png" class="no-border" >}} 1. In the **Confirmation** pop-up, click **Yes, delete all data and unlink this app**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/confirm-unlink.png" alt="" width=75% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/confirm-unlink.png" alt="" width=75% class="no-border" >}} {{% alert color="info" %}}Before your environment is deleted, you may be prompted to authenticate with [two-factor authentication](/developerportal/deploy/two-factor-authentication/).{{% /alert %}} @@ -66,7 +66,7 @@ To migrate your Free App and its database to your Mendix Basic environment, foll 1. In the banner at the top of the **Environments** page, click **Select a node**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png" class="no-border" >}} 2. Click **Use this node** for the node you just licensed. You may have to confirm and authenticate this with two-factor authentication again. @@ -97,7 +97,7 @@ The final step is restoring your data. You must do this after you've deployed yo {{% alert color="info" %}}If your app is running, you will be prompted to stop the application before continuing the restoration process. If prompted, stop your application by clicking **Stop application**. Then click **Restore Backup** again.{{% /alert %}} - {{< figure src="/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/restore-backup.png" alt="" width=75% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/restore-backup.png" alt="" width=75% >}} 1. You will see a dialog stating that your backup restore has been scheduled and will be completed shortly. Click **Okay**. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/logs.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/logs.md similarity index 87% rename from content/en/docs/deployment/mendix-cloud-deploy/logs.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/logs.md index d4ead2f6f9e..c32b6941f45 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/logs.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/logs.md @@ -28,7 +28,7 @@ To view logs, you must have **Access to Monitoring** permission. For more inform When your app is deployed to Mendix Cloud, it automatically creates daily app and access logs. On the **Logs** page, you can view archived logs, view the live log, and view log access activity. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/logs/logs-archives.png" alt="Logs Page" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/logs/logs-archives.png" alt="Logs Page" class="no-border" >}} For apps deployed to Mendix Cloud, you can select which environment you want logs for. Viewing production logs requires [two-factor authentication](/developerportal/deploy/two-factor-authentication/). @@ -46,13 +46,13 @@ File sizes are displayed for archived logs, but in-progress logs show the label By default, archived logs are sorted by date; the current log is the first one listed. You can manually click through the archived logs or use the search field to find logs for a specific date. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/logs/logs-filter.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/logs/logs-filter.png" alt="" class="no-border" >}} ### 2.2 Live Log Click **View Live Log** to access your app's log in real time. You can use the drop-down menus to adjust the log sources and log levels that appear in the live log. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/logs/live-log.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/logs/live-log.png" alt="" class="no-border" >}} {{% alert color="info" %}} The live log displays in the local time of the browser. All other logs have timestamps in UTC. @@ -66,12 +66,12 @@ At the bottom of the **Logs** page, there is an activity log. This section repor The activity log records access by team members as well as members of Mendix Support, who may view or download your app's logs in connection with any support tickets you have open. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/logs/activity-log.png" alt="Activity log" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/logs/activity-log.png" alt="Activity log" >}} ## 3 Free App Archived logs are not available for Free Apps. The **Logs** page displays sample data instead of archived data for your app. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/logs/free-app.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/logs/free-app.png" alt="" class="no-border" >}} You can still interact with the sample data, and you can click **View Live Log** to access a live log of your deployed Free App. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/maintenance-windows.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/maintenance-windows.md similarity index 94% rename from content/en/docs/deployment/mendix-cloud-deploy/maintenance-windows.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/maintenance-windows.md index 21a14dd645f..67984c41917 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/maintenance-windows.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/maintenance-windows.md @@ -49,11 +49,11 @@ Follow the instructions below to configure a maintenance window. 1. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the environment that you want to configure. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/maintenance-windows/environment-details.png" alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/maintenance-windows/environment-details.png" alt="" class="no-border" >}} 1. Go to the **Maintenance** tab. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/maintenance-windows/maintenance.png" alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/maintenance-windows/maintenance.png" alt="" class="no-border" >}} 1. Click **Change** to modify the preferred maintenance window of your environment. To modify the window, you must have [transport rights](/developerportal/deploy/node-permissions/#transport-rights) for the environment. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-request-headers.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-cloud-request-headers.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-request-headers.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-cloud-request-headers.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-status.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-cloud-status.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-status.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-cloud-status.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/mendix-ip-addresses.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-ip-addresses.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/mendix-ip-addresses.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-ip-addresses.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/mendix-sso.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-sso.md similarity index 87% rename from content/en/docs/deployment/mendix-cloud-deploy/mendix-sso.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-sso.md index 83e7b896735..5603b62a1bc 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/mendix-sso.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-sso.md @@ -38,13 +38,13 @@ Mendix Single Sign-On is only activated when your app is deployed to Mendix Clou As an end-user, you will see the Mendix SSO screen when you open an app if this is your first time visiting the app environment or if you have not opened the app recently. From this screen, you can choose to sign in with local user credentials, or you can click **Mendix Account** to use your Mendix account with Mendix SSO. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/mendix-sso/sso-sign-on.png" alt="Mendix SSO sign-on screen" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/sso-sign-on.png" alt="Mendix SSO sign-on screen" class="no-border" >}} Apps implementing Mendix SSO require access to some of your profile information, such as your account identifier and your display name. So, the first time you sign in to an environment (for example, myapp running in acceptance) as an end-user using Mendix SSO, the app will ask you to authorize access. Authorizing access allows the app to access certain information from your Mendix profile, as specified on the authorization page. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/mendix-sso/authorize-access.png" alt="Authorization screen" width=50% class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/authorize-access.png" alt="Authorization screen" width=50% class="no-border" >}} Click **Authorize** to continue using Mendix SSO with the app. Authorizing the app automatically signs you in to the app. @@ -52,7 +52,7 @@ Click **Authorize** to continue using Mendix SSO with the app. Authorizing the a To give end-users access to your app, use the [Access Management](/developerportal/collaborate/general-settings/#managing-app-users) tab on the **Settings** page after opening your app in **Apps**. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/mendix-sso/access-management-tab.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/access-management-tab.png" alt="" class="no-border" >}} {{% alert color="warning" %}} Do not attempt to add or delete Mendix SSO users using administration functions within the app. User access to your app can only be changed through the Mendix Portal. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/metrics.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/metrics.md similarity index 92% rename from content/en/docs/deployment/mendix-cloud-deploy/metrics.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/metrics.md index d0d62a831ab..efb2c1c85e2 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/metrics.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/metrics.md @@ -34,7 +34,7 @@ If you meet the above conditions, you can find the graphs by following these ste 1. Use the drop-down menu in the upper-right corner to select the environment you want to monitor. 1. Use the **Period** and **Group** drop-down menus to choose the time period (day, week, month, or quarter) and the group (application, database, or all) for the graphs that you want to view. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/metrics-selection.png" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/metrics-selection.png" >}} 1. To view more information about any of the metrics, click **Documentation** ({{% icon name="info-circle" %}}) next to the relevant graph. To quickly scroll to the top of the page, click **Scroll to top** ({{% icon name="arrow-circle-up" %}}). @@ -67,7 +67,7 @@ This section explains the metrics that represent the current status and statisti The **Number of handled external requests** graph shows the number of requests that are sent from the client and systems that integrate with your application using web services. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-ext-requests.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-ext-requests.png" >}} The number of requests per second is split up by request handlers. These are the key ones: @@ -101,7 +101,7 @@ Additional information about request handlers is available on the following page The **User accounts and login sessions** graph shows the number of logged-in user sessions for your application. It includes both named and anonymous users accounts. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-accounts-logins.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-accounts-logins.png" >}} These are the user types: @@ -115,7 +115,7 @@ These are the user types: The **JVM Object Heap** graph shows the internal distribution of allocated memory inside the application process for Java objects. Java objects are created in Java actions, but they also include all objects that are used by microflows running in your app at runtime. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-heap.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-heap.png" >}} Note that the JVM does not immediately clean up objects that are no longer in use. This graph shows unused memory as still in use until the garbage collector—which analyzes the memory to free up space—is run. So, before a garbage collection, you cannot see how much of the JVM memory will be available after the garbage collection cycle. This is because the garbage collection process only finds that out when it actually runs. @@ -138,7 +138,7 @@ If a garbage collection is triggered when the percentage reaches two-thirds of t The **JVM Process Memory Usage** graph is similar to the [JVM Object Heap](#Trends-appmxruntimejvmheap) graph described above. It shows a more complete view of the actual size and composition of the operating system memory that is in use by the JVM process. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-memory.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-memory.png" >}} This graph is included to provide more insight into situations where the part of the real used memory outside the JVM Object Heap is growing too much and causing problems with memory shortage in the operating system. @@ -163,7 +163,7 @@ These are the types: The **Memory usage** graph shows the distribution of operating system memory that is available for this server. It is measured in gibibytes. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-memory-usage.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-memory-usage.png" >}} Performance issues can arise if the app's memory takes up too much of the operating system memory. @@ -174,7 +174,7 @@ The **Threadpool for handling external requests** graph shows the number of conc * When they are initiated by a remote API (the way the normal web-based client communicates) * When they are initiated by calling web services -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-threadpool.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-threadpool.png" >}} Creating a new thread that can concurrently process a request is an expensive operation. So, Mendix holds a pool of threads that can quickly start processing new incoming requests. This pool automatically grows and shrinks according to the number of requests that are flowing through the application. @@ -191,7 +191,7 @@ The values shown by the graph are as follows: The **Total number of threads in the JVM process** graph shows the total number of threads that exist inside the running JVM process. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-thread-count.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-thread-count.png" >}} In addition to the threadpool that is used for external HTTP requests (described above), this includes the threadpool used for the following: @@ -203,7 +203,7 @@ In addition to the threadpool that is used for external HTTP requests (described The **CPU usage** graph shows the app's CPU utilization, as a percentage. The graph's y-axis scales dynamically based on the data, ranging from 0 to the maximum data point included in the request. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-cpu-usage.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-cpu-usage.png" >}} {{% alert color="info" %}} CPU usage of the database is shown in [Database Node CPU Usage](#Trends-dbcpu), below. @@ -219,7 +219,7 @@ Your app can always access at least the amount of CPU specified for your contain The **Disk usage** graph shows the relative amounts of application node data stored on disk, displayed as a percentage. The graph's y-axis scales dynamically based on the data. If the app's disk usage is below 100%, then the y-axis ranges from 0 to the maximum data point included in the request. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-disk-usage.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-disk-usage.png" >}} Interpret this graph in combination with other graphs. For more information, see [Combining Information](#combine-info), above. @@ -229,7 +229,7 @@ The disk usage graph shows only the disk usage inside the container. This is usu The **Storage – Number of Files** graph shows the number of files created by entities that are based on `FileDocument` generalizations. These are stored in S3 file storage. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-number-of-files.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-number-of-files.png" >}} ### 4.11 Storage – Size of Files{#Trends-appsizeoffiles} @@ -239,7 +239,7 @@ This metric was added on January 21, 2022, with the release [4.25.0](https://git The **Storage – Size of Files** graph shows the size of files (in bytes) that are stored in file storage. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/app-size-of-files.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-size-of-files.png" >}} ## 5 Database Statistics @@ -253,7 +253,7 @@ If you are using the [Basic License](/developerportal/deploy/basic-package/), yo The **Number of database queries being executed** graph shows the number of database queries per second that are executed by your Mendix application. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-queries-no.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-queries-no.png" >}} The queries are broken down into queries that modify data (**insert**, **update**, and **delete**) and queries that fetch data (**select**). It also includes the number of SQL transactions per second. @@ -271,7 +271,7 @@ These are the types of queries: The **Database table vs. index size** graph shows the distribution between disk space used for storing indexes and actual data. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-table-vs-index.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-table-vs-index.png" >}} Remember, indexes actually occupy memory space and disk storage. This is because they are just copies of parts of your data stored and sorted in another way! Besides the data you are processing, the relevant parts of the indexes also have to be read into system memory to be able to use them. @@ -286,7 +286,7 @@ These are the values: The **Database transactions and mutations** graph shows the number of database objects that were changed by database queries from the application. It is measured in operations per second. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-mutations.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-mutations.png" >}} For a single database operation that affects more than one object, this graph shows the number of objects actually changed, as measured from inside the database. However, the [Number of database queries being executed](#Trends-dbmxruntimeconnectionbus) graph only shows a single database query for the same operation. @@ -312,7 +312,7 @@ The **Connections to the database** graph shows the number of connections to the You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-connections-no.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-connections-no.png" >}} The number of connections goes up and down with the usage of the application. The database can reuse open connections and will not open more connections than it needs. @@ -326,7 +326,7 @@ The **Database memory** graph shows the distribution of operating system memory, You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-memory.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-memory.png" >}} Parts of the database data and indexes that are referenced frequently must always be available in the working memory of the server. This is crucial for application performance. @@ -350,7 +350,7 @@ This graph is normalized so that 100% is the full capacity of the database node. You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-cpu-usage.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-cpu-usage.png" >}} ### 5.7 Database Throughput{#Trends-dbdiskstatsthroughput} @@ -360,7 +360,7 @@ The **Database throughput** graph shows the amount of data that is being read fr You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-throughput.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-throughput.png" >}} If you see large values here that do not immediately drop back again, it may indicate that your app is continually swapping data to disk. This could be caused by inefficient queries; for example, it could be caused by queries that require sorting within the app. @@ -375,7 +375,7 @@ The value for used storage also includes space that is used to store transaction You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-disk-usage.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-disk-usage.png" >}} ### 5.9 Database IOPS {#Trends-dbdiskstatsiops} @@ -385,7 +385,7 @@ The **Database IOPS** graph, also called the database input/output operations pe You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-iops.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-iops.png" >}} There are two sets of values: @@ -402,7 +402,7 @@ The **Database IO latency** graph shows the average waiting times, in seconds, f You will not see this if you are using the [Basic License](/developerportal/deploy/basic-package/) because you are using a private schema on a shared database server. {{% /alert %}} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-io-latency.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-io-latency.png" >}} Interpret the values in this graph in combination with the other disk stats graphs and the type of requests that were made. Sequential or random reads and writes can create a different burden for disk storage. @@ -425,7 +425,7 @@ You will not see this graph if you are using the [Basic License](/developerporta The **Database IOPS burst balance** graph shows the number of IOPS credits accrued to support burstable performance. The metric is expressed as a percentage; 100% means that the volume has accumulated the maximum number of credits. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/db-iops-burst-balance.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-iops-burst-balance.png" >}} Apps running on Mendix Cloud use AWS databases to store their data. These databases are burstable, which means that they have a specified performance baseline. Burstable performance means that if you use fewer IOPS than is required for baseline performance (such as when the app is idle), the unspent IOPS credits accrue until they reach a maximum. If a burstable performance instance needs to burst above the baseline performance level, it spends the accrued credits. The more credits that a burstable performance instance has accrued, the more time it can burst beyond its baseline when more performance is needed. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/migrating-to-different-cloud.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/migrating-to-different-cloud.md similarity index 94% rename from content/en/docs/deployment/mendix-cloud-deploy/migrating-to-different-cloud.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/migrating-to-different-cloud.md index 605432cfdf6..1fff2310d2b 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/migrating-to-different-cloud.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/migrating-to-different-cloud.md @@ -43,7 +43,7 @@ Before following the steps described on this page, make sure that you have met t To manually migrate your app to a new node, follow the steps in the sections below. Those steps are summarized in this graphic: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/migrating/migratev4.png" alt="" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/migratev4.png" alt="" class="no-border" >}} ### 4.1 Linking a Temporary Free App to the Target Cloud Node @@ -55,7 +55,7 @@ First, link one of the new temporary apps to the target node. 3. Click **Select a node**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/migrating/select-a-node.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/select-a-node.png" class="no-border" >}} 4. Select the target node by clicking **Use this Node**. Link it to your app. @@ -77,7 +77,7 @@ To download a deployment package, follow these steps: 2. Click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) > **Details** for a deployment package. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/migrating/deployment-details.png" alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/deployment-details.png" alt="" class="no-border" >}} 3. In the resulting **MDA Details** dialog box, click **Download**. @@ -87,7 +87,7 @@ To upload the deployment package, follow these steps: 2. In the **Deployment Package Repository** section, click **Upload**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/migrating/upload-package.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/upload-package.png" class="no-border" >}} 3. Browse and select the downloaded deployment package from your device. @@ -182,7 +182,7 @@ Or, if you made a certificate request to Mendix, the private key is stored in th The two custom domain certificate options are shown below: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/migrating/tls-certificates.png" alt="" width=75% >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/tls-certificates.png" alt="" width=75% >}} ### 4.7 Offboarding the Source Node diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/_index.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/_index.md similarity index 96% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/_index.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/_index.md index a3f3b3a640a..bcab2af340e 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/_index.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/_index.md @@ -33,11 +33,11 @@ Mendix Cloud automatically monitors the health and status of apps that are deplo 1. From [Apps](https://sprintr.home.mendix.com), open the app that you want to monitor. 1. In the [navigation pane](/developerportal/#navigation-pane), click **Alerts**. This displays the status of your app node in various categories. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/application-status.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/application-status.png" class="no-border" >}} 1. To view more details about a specific alert, click it. Detailed information about that alert will appear below the alert status table. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/alert-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/alert-details.png" class="no-border" >}} You may be able to use this information to resolve the issue yourself; otherwise, include this information when submitting a support request to [Mendix Support](https://support.mendix.com). You can download a log of the alerts on the [Logs](/developerportal/operate/logs/) page. @@ -159,7 +159,7 @@ To access the history of the alerts from your app, follow these steps: 2. Select the environment that you wish to see alert history for. 3. You will see an overview of all alerts that have been sent for this application. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/alerts-history.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/alerts-history.png" class="no-border" >}} The overview shows alert types and details, including date and time. The alert types provide a broad indication of the type of error that occurred, such as critical log messages or failures of the health check microflow. Recovery notifications are also shown here. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts.md similarity index 91% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts.md index 470f7a64dea..2e82ba19a6f 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts.md @@ -27,7 +27,7 @@ If you are the Technical Contact for an app, you can grant team members the **Re 1. Switch to the **Permissions** tab. 1. Select the checkbox below **Receive Alerts** for the user (or users) who should receive alerts. Your changes will save automatically. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts/receive-alerts.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts/receive-alerts.png" class="no-border" >}} ### 2.2 Alerts Page @@ -40,7 +40,7 @@ To enable email alerts, follow these steps: 1. Select the environment for which you want to set the alerts from the drop-down list at the top of the page. It is possible to set this option separately for each environment. 1. Select the **Email Alerts** checkbox. Your changes will save automatically. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts/email-alerts.png" alt="The Email Alerts checkbox" width="70%" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts/email-alerts.png" alt="The Email Alerts checkbox" width="70%" class="no-border" >}} ## 3 Alerts Using Webhooks diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/_index.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/_index.md similarity index 98% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/_index.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/_index.md index fb4e0f22ed1..a0aff7e6942 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/_index.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/_index.md @@ -267,7 +267,7 @@ You pass the configuration to the metrics agent by adding a custom runtime setti 2. Click **Details** next to the environment you have configured for Datadog. 3. In the **Custom Environment Variable** section, add a `METRICS_AGENT_CONFIG` variable with the value of the JSON required for your configuration. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/metrics-agent-config.png" width=400 class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/metrics-agent-config.png" width=400 class="no-border" >}} 4. Click **Save**. 5. Restart your app to apply the new settings if you have already connected your node to your data analytics. If you are in the process of connecting your node, you must redeploy your application to apply the changes. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/appdynamics-metrics.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/appdynamics-metrics.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/appdynamics-metrics.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/appdynamics-metrics.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md similarity index 89% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md index dac39dff8e5..e50c8f4a6f4 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md @@ -42,7 +42,7 @@ To set up a new Datadog account and access your API key as a new Datadog user, f 2. Complete the account setup steps: enter your desired account details, describe your stack, and install a Datadog agent. You must set up an agent to continue, so select one of the installation options presented on the *Install Your First Datadog Agent* page. 3. Copy the value of the API key shown in the installation script. The key name varies depending on the agent you are installing, but it will be something like `api-key`, `datadog_api_key`, or `DD_API_KEY`. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/dd-api-key.png" alt="Agent script shows your API key" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/dd-api-key.png" alt="Agent script shows your API key" class="no-border" >}} 4. Follow the instructions in [Connecting Your Node to Datadog](#connect-node), below, to start using the API key with your app. @@ -53,11 +53,11 @@ To find your existing API key or to request a new key for your app as an existin 1. Log in to your Datadog account. 2. In the navigation menu, click **Go to** to launch the search dialog box. Search for *API Keys*. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-integrations-api.png" alt="API Keys search results" width=400 class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-integrations-api.png" alt="API Keys search results" width=400 class="no-border" >}} 3. Copy an existing API key or create a new one. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-api-keys.png" alt="Datadog site: API Keys page" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-api-keys.png" alt="Datadog site: API Keys page" class="no-border" >}} 4. Follow the instructions in [Connecting Your Node to Datadog](#connect-node), below, to start using the API key with your app. @@ -70,7 +70,7 @@ To send your runtime information to Datadog, you need to provide the Datadog API 1. Switch to the **Runtime** tab. 1. Click **Add** in the **Custom Environment Variables** section. 1. In the **Name** field, select **DD_API_KEY**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/environment-variable-dd-api-key.png" alt="Drop-down list containing custom environment variable names" width=400 class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/environment-variable-dd-api-key.png" alt="Drop-down list containing custom environment variable names" width=400 class="no-border" >}} 1. In the **Value** field, enter the Datadog API key that you obtained in the [Datadog API Key](#datadog-api-key) section, above. 1. Click **Save**. @@ -87,13 +87,13 @@ Once you have connected your node to Datadog, you can install the Mendix integra 1. Sign in to your Datadog account. 2. Go to **Integrations** and search for *Mendix*. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-mendix-integration.png" alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-mendix-integration.png" alt="" class="no-border" >}} 3. Install the Mendix integration. 4. Go to **Dashboards** > **Dashboard List** and open the **Mendix Application Overview** dashboard. 5. To view data on the dashboard, use the drop-down lists to select a Mendix app, environment, and instance. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/mendix-application-overview.png" alt="" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/mendix-application-overview.png" alt="" class="no-border" >}} If you want to customize the dashboard, clone it and modify the clone. Alternatively, you can build your own dashboard from scratch. @@ -150,13 +150,13 @@ To set these tags, do the following: 1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app. 1. Click **Details** on an environment you are monitoring with Datadog. 1. Switch to the **Tags** tab - {{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/set-tags.png" alt="Example metric showing tags in Datadog" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/set-tags.png" alt="Example metric showing tags in Datadog" class="no-border" >}} 1. Click **Add** and type in a string to be sent to Datadog as a tag. 1. Restart your app. Setting these values for your app causes all metrics from this environment of your app to have these tags. For example, the tags for `mx.microflow.time.avg` for this set of metrics include `app:customermanagement` and `env:accp`. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-summary-tags.png" alt="Example metric showing tags in Datadog" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-summary-tags.png" alt="Example metric showing tags in Datadog" class="no-border" >}} {{% alert color="info" %}} You can add more tags if you want, but note that Datadog may charge for custom metrics. For more information, see [Custom Metrics Billing](https://docs.datadoghq.com/account_management/billing/custom_metrics) on the Datadog site. @@ -171,7 +171,7 @@ To view metrics for multiple instances of an application on the Datadog dashboar 3. In the **from** field, specify your desired app environment's **Environment ID**. Use the format `application_name:`. 4. In the **avg by** field, select **instance_index**. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png" alt="Metrics Explorer search form" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png" alt="Metrics Explorer search form" class="no-border" >}} If the app has more than one instance, you will see lines on the graph for each instance. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md diff --git a/content/en/docs/deployment/mendix-cloud-deploy/node-permissions.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/node-permissions.md similarity index 91% rename from content/en/docs/deployment/mendix-cloud-deploy/node-permissions.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/node-permissions.md index 7f85c63ce9a..80f0fc4c81d 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/node-permissions.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/node-permissions.md @@ -20,7 +20,7 @@ To find a list of all Mendix Cloud licensed nodes that you have access to, open You will see a list of all your licensed nodes: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/node-permissions/nodes-list.png" alt="Licensed Mendix Cloud nodes" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/nodes-list.png" alt="Licensed Mendix Cloud nodes" class="no-border" >}} To go to the [Environments](/developerportal/deploy/environments/) page for the app that is deployed to a node, click **Environments** on that node. @@ -51,11 +51,11 @@ To access the node permissions, do the following: 1. Click **Environments** for your app. 2. Switch to the **Permissions** tab. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/node-permissions/permissions-tab.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/permissions-tab.png" class="no-border" >}} 3. From the drop-down list in the upper-right corner, select the environment for which you want to change permissions. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/node-permissions/change-environments.png" alt="" width=25% class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/change-environments.png" alt="" width=25% class="no-border" >}} 4. If prompted, complete two-factor authentication. @@ -63,7 +63,7 @@ To access the node permissions, do the following: The Technical Contact can enable and disable **Manage Permissions** for the other team members. Any team members with **Manage Permissions** enabled can set the following node permissions: **Transport Rights**, **Access to Backups**, **Receive Alerts**, **API Rights**, and **Access to Monitoring**. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/node-permissions/node-permission.png" alt="Node permissions dashboard" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/node-permission.png" alt="Node permissions dashboard" class="no-border" >}} #### 3.3.1 Manage Permissions diff --git a/content/en/docs/deployment/mendix-cloud-deploy/pipelines.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/pipelines.md similarity index 96% rename from content/en/docs/deployment/mendix-cloud-deploy/pipelines.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/pipelines.md index 588a90acaf3..912bdd1b82c 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/pipelines.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/pipelines.md @@ -26,7 +26,7 @@ If you need to configure your user settings so that you can run a pipeline for t ## 2 The Runs Tab{#runs-tab} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/pipelines/runs-tab.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/runs-tab.png" alt="" >}} For each run, you can view the following information: @@ -52,7 +52,7 @@ The search and filter options allow you to review specific run types. You can do To see the results of a particular run, click **Results** ({{% icon name="paper-clipboard" %}}). -{{< figure src="/attachments/deployment/mendix-cloud-deploy/pipelines/run-details.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/run-details.png" alt="" >}} From this page, you can view an overview of the run. You can also expand each executed step to see more information about it; this is especially useful for debugging when a pipeline run fails. When you expand a step, you can also see a **View Parameters** button, which you can use to view the input and output parameters as well as the values of the step. @@ -74,7 +74,7 @@ If a system-level error occurs, the card in the upper-left corner of the **Resul ## 3 The Designs Tab{#designs-tab} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/pipelines/designs-tab.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/designs-tab.png" alt="" >}} On the **Designs** tab, you can see all existing pipeline designs. @@ -115,7 +115,7 @@ Give your pipeline a name. You can use up to 40 alphanumeric characters in the n From your pipeline design's **Details** page, you can add, remove, and configure the steps in your pipeline. You can also click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) next to the pipeline name to edit the name. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/pipelines/pipeline-design.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/pipeline-design.png" alt="" >}} {{% alert color="info" %}} Active pipelines cannot be edited; if you want to edit an existing pipeline, make sure it is deactivated. @@ -199,7 +199,7 @@ The pipeline design's status (**Active** or **Inactive**) is displayed in the ov ## 4 The Settings Tab{#settings-tab} -{{< figure src="/attachments/deployment/mendix-cloud-deploy/pipelines/settings-tab.png" alt="" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/settings-tab.png" alt="" >}} The **Settings** tab lets you configure user settings. You must add your API key and personal access token (PAT) before you can activate or run your first pipeline. If you still need to configure these user settings, the **Settings** tab is marked with an alert icon ({{% icon name="alert-circle-filled" color="red" %}}). diff --git a/content/en/docs/deployment/mendix-cloud-deploy/scale-environment.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/scale-environment.md similarity index 88% rename from content/en/docs/deployment/mendix-cloud-deploy/scale-environment.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/scale-environment.md index d57b7366ccb..97c6ac5b934 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/scale-environment.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/scale-environment.md @@ -34,13 +34,13 @@ To scale your licensed app in Mendix Cloud, follow these steps: 1. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the environment you want to scale. 1. On the **General** tab, scroll down to the **Instances** row. Click **Change scaling**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/scale-environment/change-scaling.png" alt="" >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/change-scaling.png" alt="" >}} 1. To set the **Memory per instance** that you want to use, drag the **Memory per instance** indicator bar. 1. To set the number of **Instances** you want to use, drag the **Instances** indicator bar. 1. Click **Apply**. This restarts your environment to apply the changes. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/scale-environment/scale.png" alt="Scaling dashboard" max-width=75% >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/scale.png" alt="Scaling dashboard" max-width=75% >}} ### 3.1 Scaling Notes @@ -62,10 +62,10 @@ You do not need to allocate all the available memory at once. You can just alloc For example, you can use one instance with 2 GiB RAM. The remaining 6 GiB in your cloud resource pack will be unused. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/scale-environment/scaling-example.png" alt="Scaling dashboard with 2 out of 8 GB of total allocated memory used" max-width=75% >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/scaling-example.png" alt="Scaling dashboard with 2 out of 8 GB of total allocated memory used" max-width=75% >}} ## 5 Read More -* [Deployment](/deployment/) +* [Deployment](/developerportal/deploy/) * [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/) * [About Mendix Cloud](/developerportal/deploy/mxcloudv4/) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/sending-email.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/sending-email.md similarity index 100% rename from content/en/docs/deployment/mendix-cloud-deploy/sending-email.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/sending-email.md diff --git a/content/en/docs/deployment/general/software-composition.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/software-composition.md similarity index 76% rename from content/en/docs/deployment/general/software-composition.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/software-composition.md index fd8793dc021..5feb8ae1336 100644 --- a/content/en/docs/deployment/general/software-composition.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/software-composition.md @@ -2,7 +2,7 @@ title: "Software Composition" url: /developerportal/deploy/software-composition/ description: "Describes the Software Composition page in Apps." -weight: 3 +weight: 9 beta: true --- @@ -14,7 +14,7 @@ This feature is in beta. For more information, see [Beta Releases](/releasenotes A Mendix app can consist of the Mendix Model (which includes pages, domain model, microflows, etc.), custom Java, and JavaScript. Additionally, it can use reusable components such as standard marketplace modules, widgets, Java libraries, npm packages, and the runtime version. These reusable components are dependencies, namely, components you are dependent on for your Mendix app to run. -Over time, these dependencies can become deprecated, outdated, or vulnerable. Enterprises also have policies on which of these reusable components can or cannot be used based on support, license, etc. It is important to have an easily accessible, clear view of component dependencies through the development lifecycle in order to address any security finding raised by your admins or security teams. +Over time, these dependencies can become deprecated, outdated. or vulnerable. Enterprises also have policies on which of these reusable components can or cannot be used based on support, license, etc. It is important to have an easily accessible, clear view of component dependencies through the development lifecycle in order to address any security finding raised by your admins or security teams. To enable this, the **Software Composition** page in **Apps** provides visibility into the component dependencies of each deployment package. The components displayed here will be based on the [Software Bill of Materials (SBOM)](/refguide/sbom-generation/). @@ -28,7 +28,7 @@ After the creation of a deployment package, it may take up to a day for the **So To be able to see the software composition information, make sure that you meet the following prerequisites: -* Component details and related actions are available for apps made with Studio Pro versions [9.24.22](/releasenotes/studio-pro/9.24/#92422) and above, [10.6.9](/releasenotes/studio-pro/10.6/#1069) and above, and [10.10.0](/releasenotes/studio-pro/10.10/#10100) and above; therefore, they are not available for apps made with Studio Pro versions below 9.24.22 and 10.6.9, as well as versions 10.7, 10.8, and 10.9. +* Component details and related actions are available for apps made with Studio Pro versions [9.24.22](/releasenotes/studio-pro/9.24/#92422) and above, [10.6.9](/releasenotes/studio-pro/10.6/#1069) and above, and [10.10.0](/releasenotes/studio-pro/10.10/#10100) and above, therefore, not available for apps made with Studio Pro versions below 9.24.22 and 10.6.9, as well as versions 10.7, 10.8, and 10.9. {{% alert color="info" %}}With Mendix versions 9.24.22 and above, only unmanaged Java dependencies or jars are shown. With Mendix versions 10.6.9 and above, both managed and unmanaged Java dependencies or jars will be shown.{{% /alert %}} @@ -44,13 +44,13 @@ Components are identified in the following manner: First, when a new deployment package is created via the Mendix Portal with the compatible Mendix Runtime version, a software bill of material (SBOM) is generated along with it. The log details can be viewed by clicking **View build output** in the deployment package details in the Mendix Portal. For details on SBOM generation, see [SBOM Generation](/refguide/sbom-generation/). -The component dependencies for each non-expired deployment package are available in the **Software Composition** page in **Apps**. +The component dependencies for each non-expired, deployment package are available in the **Software Composition** page in **Apps**. ## 2 Overview {#overview} On the **Overview** tab, you can see a list of all the deployed packages and their environments, if applicable. -{{< figure src="/attachments/deployment/general/software-composition/overview.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/overview.png" >}} Above the list, you can use the search box to search for information in the list. Next to the search box, you can filter apps by selecting the environment type or the Mendix Runtime version. You can click {{% icon name="office-sheet" %}}**Export all** on the right side above the list to export all the information in the list to an Excel file. @@ -61,13 +61,13 @@ The list contains the following information: * **Runtime**: This shows the Mendix Runtime version. * **Version**: This shows the version of the deployment package on this app environment. * Column customization ({{% icon name="view" %}}): You can customize the columns of the list by clicking the {{% icon name="view" %}} icon and adjusting the selection of the check boxes. -* **View details**: Clicking this opens the [Component Summary](#component-summary) page, if it is available. The **View details** button is grayed out when an SBOM is not available for the selected deployment package. Ensure you are on a compatible runtime version and create a new deployment package in order to get component visibility here. +* **View details**: Click this opens the [Component Summary](#component-summary) page, if it is available. The **View details** button is grayed out when an SBOM is not available for the selected deployment package. Ensure you are on a compatible runtime version and create a new deployment package in order to get component visibility here. ### 2.1 Component Summary {#component-summary} On the **Overview** tab, if you click **View Details** for a deployment package in the list, the **Component Summary** page opens. -{{< figure src="/attachments/deployment/general/software-composition/component-summary.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/component-summary.png" >}} On the top of the page, you can find the name of the deployment package, the environment name, the Mendix Runtime version, and the version of the deployment package. @@ -75,9 +75,9 @@ For details on the information in the list and how to search, filter, and export #### 2.1.1 Downloading the Software Bill of Materials {#download-software-bill-of-materials} -A software bill of materials (SBOM) is a *.json* file in the CycloneDX format. It contains a description of the Mendix app and the components (dependencies) put into it. For more information, see [SBOM Generation](/refguide/sbom-generation/). +A software bill of materials (SBOM) is a *.json* file in the CycloneDX format. It contains a description about the Mendix app and the components (dependencies) put into it. For more information, see [SBOM Generation](/refguide/sbom-generation/). -In the list on the **Overview** tab, you can click the {{% icon name="download-bottom" %}} icon in the **Action** column to download the SBOM. Different versions of Studio Pro support different component dependencies. For details on component dependencies supported per version, see the [Supported Features](/refguide/sbom-generation/#supported-features) section in *SBOM Generation*. +In the list on the **Overview** tab, you can click {{% icon name="download-bottom" %}} icon in the **Action** column to download the SBOM. Different versions of Studio Pro support different component dependencies. For details on component dependencies supported per version, see the [Supported Features](/refguide/sbom-generation/#supported-features) section in *SBOM Generation*. ## 3 All Components {#all-components} @@ -85,7 +85,7 @@ The **All Components** tab gives an overview of all the components used across y {{% alert color="info" %}}To be able to see the software composition information, make sure that you meet the prerequisites. For more information, see the [Prerequisites](#prerequisites) section.{{% /alert %}} -{{< figure src="/attachments/deployment/general/software-composition/all-components.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/all-components.png" >}} Above the list, you can use the search box to search for a component. Next to the search box, you can filter components by selecting the component type. You can click {{% icon name="office-sheet" %}}**Export all to Excel** on the right side above the list to export all the information in the list to an Excel file. @@ -94,15 +94,15 @@ The list shows the following information about the component: * **Component**: This is the name of the component. * **Version**: This is the component version. * **Type**: This shows the type of the component. -* Column customization ({{% icon name="view" %}}): You can customize the columns of the list by clicking the {{% icon name="view" %}} icon and adjusting the selection of the checkboxes. -* **View details**: Clicking this opens the [Component Usage](#component-usage) page. +* Column customization ({{% icon name="view" %}}): You can customize the columns of the list by clicking the {{% icon name="view" %}} icon and adjusting the selection of the check boxes. +* **View details**: Click this opens the [Component Usage](#component-usage) page. ### 3.1 Component Usage {#component-usage} -On the **All Components** tab, if you click **View details** for an item, the **Component Usage** page opens. This page lists the environments where the selected component is being used. If a security vulnerability is found in one of the components, then the component usage tab can be used to assess the impact radius. +On the **All Components** tab, if you click **View details** for an item, the **Component Usage** page opens. This page lists the environments where the selected component is being used. If a security vulnerabilities is found in one of the components, then the component usage tab can be used to assess the impact radius. -{{< figure src="/attachments/deployment/general/software-composition/component-usage.png" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/component-usage.png" >}} On the top of the page, you can find the component name, the component version, and the component type. -For details on the information in the list and how to search, filter, and export information in the list, see the [Overview](#overview) section. +For details on the information in the list and how to search, filter, and export information in the list, see the [Overview](#overview) section. \ No newline at end of file diff --git a/content/en/docs/deployment/mendix-cloud-deploy/studio-deployment-settings.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/studio-deployment-settings.md similarity index 89% rename from content/en/docs/deployment/mendix-cloud-deploy/studio-deployment-settings.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/studio-deployment-settings.md index 6f3889af38f..79aaf15e66c 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/studio-deployment-settings.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/studio-deployment-settings.md @@ -29,7 +29,7 @@ To select a target environment for Studio Pro deployment, do the following: 3. In the **Setup Studio Pro Deployment** dialog box, select your desired target environment from the **Select target environment** menu. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/studio-deployment-settings/setup-studio-pro-deployment.png" alt="Select Studio Pro Target Dialog" max-width=80% >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/studio-deployment-settings/setup-studio-pro-deployment.png" alt="Select Studio Pro Target Dialog" max-width=80% >}} 4. Click **Save**. @@ -42,7 +42,7 @@ Once the app has a target deployment environment, you can directly deploy your a 1. Open the licensed app in [Studio Pro](https://marketplace.mendix.com/link/studiopro/). 1. In the top menu bar, click **App** > **Deploy to Licensed Cloud Node**. - {{< figure src="/attachments/deployment/mendix-cloud-deploy/deploy-to-cloud-node.png" alt="The App menu with the Deploy to Licensed Cloud Node option selected" width=50% >}} + {{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/deploy-to-cloud-node.png" alt="The App menu with the Deploy to Licensed Cloud Node option selected" width=50% >}} 1. In the **Deploy to the cloud** dialog box, click **Deploy**. 1. You will see a dialog box with the following message: "Successfully started cloud deployment." It will automatically upload your MDA to the Mendix Portal, deploy it to the target environment, and restart the target environment. diff --git a/content/en/docs/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow.md b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow.md similarity index 83% rename from content/en/docs/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow.md rename to content/en/docs/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow.md index a71cdbe5f31..2ea12e22451 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow.md +++ b/content/en/docs/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow.md @@ -16,15 +16,15 @@ You must have **Access to Monitoring** enabled to launch the **Running Now** dia The **Running Now** dialog box shows all actions currently running in the environment. It also shows some general information about each action. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/dialog-box.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/dialog-box.png" class="no-border" >}} The **Details** button lets you zoom in on a selected action: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/running-request-details.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/running-request-details.png" class="no-border" >}} You can also zoom in on a stack: -{{< figure src="/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/stack.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/stack.png" class="no-border" >}} **Kill request** lets you try to stop the action. If successful, that leads to an error for the user executing the action. diff --git a/content/en/docs/deployment/mobileapp.md b/content/en/docs/developerportal/deploy/mobileapp.md similarity index 97% rename from content/en/docs/deployment/mobileapp.md rename to content/en/docs/developerportal/deploy/mobileapp.md index d497d59883a..f301878f195 100644 --- a/content/en/docs/deployment/mobileapp.md +++ b/content/en/docs/developerportal/deploy/mobileapp.md @@ -94,7 +94,7 @@ Take note of the required resolutions and file types for the image files, as the ## 4 Doing It Yourself {#doing-it-yourself} -Once you begin the app building wizard and choose the correct environment, click **Download a customizable package**. The package contains all your settings, icons, and splash screens. It allows you to easily make changes, create local builds, and run on emulators. +Once you begin the app buliding wizard and choose the correct environment, click **Download a customizable package**. The package contains all your settings, icons, and splash screens. It allows you to easily make changes, create local builds, and run on emulators. For iOS please follow the instructions in the [Building Your iOS App Locally](/howto8/mobile/build-hybrid-locally/#building-ios-locally) section of *How to Build a Mendix Hybrid App Locally*. @@ -102,6 +102,6 @@ For Android please follow the instructions in the [Building Your Android App Loc ## 5 Read More -* [Deployment](/deployment/) +* [Deploy and Manage Guide](/developerportal/deploy/) * [Offline Reference Guide](/refguide/offline-first/) * [Apache Cordova Reference Config.xml](https://cordova.apache.org/docs/en/latest/config_ref/) diff --git a/content/en/docs/deployment/on-premises-design/_index.md b/content/en/docs/developerportal/deploy/on-premises-design/_index.md similarity index 89% rename from content/en/docs/deployment/on-premises-design/_index.md rename to content/en/docs/developerportal/deploy/on-premises-design/_index.md index 001416bc5a3..e387d9b4d16 100644 --- a/content/en/docs/deployment/on-premises-design/_index.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/_index.md @@ -25,11 +25,11 @@ This how-to teaches you how to do the following: This is the simplest solution with the fewest configuration and connection problems. This configuration is used in Mendix Cloud as well, except the cloud is Linux-based, with NGINX used instead of IIS and PostgreSQL used as the database server. -{{< figure src="/attachments/deployment/on-premises-design/18580719.jpg" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/18580719.jpg" class="no-border" >}} ### 2.2 Hosting with a Separate Database Server (Option 2){#Option2} -{{< figure src="/attachments/deployment/on-premises-design/18580718.jpg" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/18580718.jpg" class="no-border" >}} ### 2.3 Separate Database Server and a Separate Web Server (Option 3) @@ -37,11 +37,11 @@ This option is the most difficult to maintain, and every update has to be perfor You should avoid using this option if possible. -{{< figure src="/attachments/deployment/on-premises-design/18580717.jpg" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/18580717.jpg" class="no-border" >}} ### 2.4 Separate Mendix Web Server in a DMZ (Option 4) -{{< figure src="/attachments/deployment/on-premises-design/18580720.jpg" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/18580720.jpg" class="no-border" >}} ## 3 Load Balancing Support and Configuration diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/_index.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/_index.md similarity index 95% rename from content/en/docs/deployment/on-premises-design/ms-windows/_index.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/_index.md index c415897e4a7..8cf39bc5bba 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/_index.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/_index.md @@ -23,7 +23,7 @@ This document describes the installation and configuration of Mendix software on To set up an environment to run Mendix applications, you will need to install the Mendix software. For each Mendix application that will be run, a separate user (service) account is required. This section presents an overview of the setup. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/18580733.png" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/18580733.png" >}} Before starting this how-to, make sure you have the following prerequisites: @@ -53,17 +53,17 @@ To download and install the Mendix Service Console, follow these steps: 1. Download the latest version of the [Mendix Service Console](https://marketplace.mendix.com/link/component/223425) module from the Marketplace. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/service_console_download.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_download.png" >}} 2. Install the Mendix Service Console by following the installation wizard. 3. Start the Mendix Service Console after completing the installation. The first time you launch the application, a popup will be shown (it will always be shown if no valid location is configured for the apps and server files): - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/service_console_first_run.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_first_run.png" >}} 4. Click **Yes**. The **Preferences** dialog box will be shown: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/18580730.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/18580730.png" >}} 5. In the **Preferences** dialog box, enter a **Location of apps and server files**. This location is used for storing your app files and Mendix server files. Mendix recommends using a directory: @@ -95,11 +95,11 @@ To deploy a Mendix app using the Mendix Service Console, follow these steps: 4. Click **Next >**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/18580728.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/18580728.png" >}} 5. On the **Project Files** screen, click **Select app…**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/service_console_selectapp.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_selectapp.png" >}} 6. Now select the **MDA** file that was [created in Studio Pro](/refguide/create-deployment-package-dialog/) and contains your application logic. After the installation of your MDA file, you will see which Mendix server (Mendix Runtime) version is needed. @@ -112,7 +112,7 @@ To deploy a Mendix app using the Mendix Service Console, follow these steps: 8. Click **Next >**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/18580726.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/18580726.png" >}} 9. On the **Common Configuration** screen, keep the default settings. These settings should only be changed if this is needed for your application setup. @@ -158,7 +158,7 @@ To create a website, follow these steps: 7. Select the certificate for the website either in the dropdown box or through the **Select...** dialog. 8. Click **OK**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/iis_add_https_binding.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/iis_add_https_binding.png" >}} ### 5.4 Configuring the MIME Types @@ -288,7 +288,7 @@ If HTTPS was configured at step 5.3 it is recommended to redirect all unencrypte 4. Make sure the *Immediately* radio button is selected. 5. Click **OK**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/iis_response_headers.png" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/iis_response_headers.png" >}} Afterwards, the contents of the *web.config* file will be similar to the following example: diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows.md similarity index 79% rename from content/en/docs/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows.md index 2454166d61e..900c70a9442 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows.md @@ -30,12 +30,12 @@ In this section, you will retrieve the server ID from your Mendix server, which 1. Start the Mendix Service Console. 2. Select your app in the overview on the left side of the console. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398813.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398813.png" class="no-border" >}} 3. The app needs to be running in order for you to be able to activate the license. If the app is not running, click **Start service** to start the app. 4. Click **Advanced** and select the **Show or add license...** option. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png" class="no-border" >}} 5. Next to **Server ID**, click **Copy to clipboard**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398815.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398815.png" class="no-border" >}} ## 4 Obtain a License Key from Mendix Support @@ -52,11 +52,11 @@ In this section, you will submit your server ID in the Mendix Support Portal to In this section, you will enter the license key into the Mendix server, thus completing the license activation process. 1. Return to the Mendix Service Console **License** dialog box (as described in [Retrieve the Server ID](#retrieve-the-server-id) section). - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png" class="no-border" >}} 2. Paste your license key into the **License key** text box. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398816.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398816.png" class="no-border" >}} 3. Click **Activate license**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398817.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398817.png" class="no-border" >}} 4. Congratulations! Your license has been activated. ## 6 Read More diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/automate-mendix-deployment-on-microsoft-windows.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/automate-mendix-deployment-on-microsoft-windows.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/ms-windows/automate-mendix-deployment-on-microsoft-windows.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/automate-mendix-deployment-on-microsoft-windows.md diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure.md similarity index 86% rename from content/en/docs/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure.md index d02b5d5c41c..8055bad0113 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure.md @@ -39,15 +39,15 @@ In a clustered environment there are some tasks (for example, cleaning up expire 1. Select your app and click **Configuration**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_configuration.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_configuration.png" class="no-border" >}} 2. In the Configuration screen, click **Advanced...**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_advanced.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_advanced.png" class="no-border" >}} 3. In the Advanced screen add a line to Custom Mendix Settings with **Name** *com.mendix.core.isClusterSlave* and **Value** *true*. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_add_setting.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_add_setting.png" class="no-border" >}} 4. Click **Close** on both screens to return to the Service Console. @@ -62,7 +62,7 @@ More information regarding the configuration of Azure Load Balancers is availabl Go to the Azure Portal to retrieve the Azure Storage account name and an access key: -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/azure_storage_keys.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/azure_storage_keys.png" class="no-border" >}} Then select your application, click **Configuration** and then **Advanced...**. In the **Advanced Settings** screen, add the following **Custom Mendix settings**: @@ -74,7 +74,7 @@ Then select your application, click **Configuration** and then **Advanced...**. * **Name**: *com.mendix.storage.azure.Container*, **Value**: `` - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/application_storage_settings.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/application_storage_settings.png" class="no-border" >}} By default, the container will be created in the blob storage if it does not yet exist. More information about the configuration options for Azure Blob Storage in the Mendix Runtime is available in the [Microsoft Azure Blob Storage Settings](/refguide/custom-settings/#azure-blob) section of *Runtime Customization*. diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/_index.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/_index.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/_index.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/_index.md diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans.md similarity index 68% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans.md index fa6ec7cfd91..605c93bb0f6 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans.md @@ -21,7 +21,7 @@ Before starting this how-to, make sure you have completed the following prerequi * For the purpose of this how-to, the following Mendix SQL data structure will be used, so please adapt the folder tree according to your organization's data structure: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580650.jpg" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580650.jpg" class="no-border" >}} * Make sure the SQL Server Agent Service is running, preferably using the Mendix service account for authentication * Consider the amount of soft backups that need to be kept @@ -37,12 +37,12 @@ To add a task step, follow these steps: 1. Drag the corresponding item from the **Maintenance Plan Tasks** toolbox: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580649.jpg" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580649.jpg" class="no-border" >}} 2. Drag connecting lines between the items to initiate a sequence of events. 3. To change a notification job from **Success** (which is the default connector) to **Failure**, right-click the connecting line and choose **Failure**: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580648.jpg" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580648.jpg" class="no-border" >}} ### 3.2 Notifications @@ -52,20 +52,20 @@ To configure notifications, follow these steps: 2. Create an SQL operator (SQL Server Agent). The operator will receive maintenance notifications. 3. Right-click **DatabaseMail** and select **Configure Database Mail**: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580653.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580653.png" class="no-border" >}} 4. Choose a valid email sender address (for example, *mendix_sql@yourdomainname.com*) 5. Make sure the email profile is set to both **Public** and **Default Profile**: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580663.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580663.png" class="no-border" >}} 6. Verify your email configuration by sending a test email: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580662.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580662.png" class="no-border" >}} 7. Next, create two maintenance plans: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580661.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580661.png" class="no-border" >}} For the sake of uniformity, the plan names **MP_SYSDB** and **MP_USERDB** will be used throughout this document. Changing the plan names to a different convention will not influence the functionality of the plan. @@ -82,12 +82,12 @@ This is the pattern for a notification: In this section, you are going to create a new maintenance plan called **MP_USERDB** containing subplans: -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580660.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580660.png" class="no-border" >}} 1. Create a subplan called **backup database (full)**. 2. Schedule the plan to run every working day at 22:00 (or whatever time does not conflict with your external backup application): - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580667.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580667.png" class="no-border" >}} 3. Choose to back up to disk. 4. Back up to *X:\sqldata\backup*. @@ -98,7 +98,7 @@ In this section, you are going to create a new maintenance plan called **MP_USER 9. Create a subplan called **backup database (trn)**. 10. Schedule the plan to run every working day, as often as is necessary. If hourly backups are run, database recovery will be possible per hour. When run with a smaller interval, database recovery to a more recent point in time will be possible. High volume databases that perform many hourly transactions should back up more often than lesser-used databases. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580666.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580666.png" class="no-border" >}} 11. Choose **Transaction Log** for the backup **Type**. 12. Choose to back up to disk. @@ -110,18 +110,18 @@ In this section, you are going to create a new maintenance plan called **MP_USER 18. Create a subplan called **weekly maintenance**. 19. Schedule the plan to run every Sunday at 01:00 (or whatever time the application is least used): - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580665.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580665.png" class="no-border" >}} 20. Set **Change free space per page percentage to: 10%** and select **Keep index online while reindexing** (please note that this option will only work in enterprise versions of Microsoft SQL server): - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580659.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580659.png" class="no-border" >}} 21. Create a subplan called **daily maintenance**. 22. Schedule to run every Tuesday till Friday at 02:00 (or whatever working days apply for your organization): - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580668.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580668.png" class="no-border" >}} - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580658.png" class="no-border" >}} . + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580658.png" class="no-border" >}} . {{% alert color="info" %}} @@ -133,12 +133,12 @@ You should adapt the times set to your desired backup retention time. The cleanu In this section, you are going to create a new maintenance plan called **MP_SYSDB** containing the following subplans: -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580652.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580652.png" class="no-border" >}} 1. Create a subplan called **backup database (full)**. 2. Schedule this to run Tuesday through Friday at 02:00 (or whatever working days apply for your organization): - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580654.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580654.png" class="no-border" >}} 3. Select to back up to disk. 4. Back up to *d:\sqldata\backup*. @@ -149,11 +149,11 @@ In this section, you are going to create a new maintenance plan called **MP_SYSD 9. Create a subplan called **weekly maintenance**. 10. Schedule this to run every Sunday at 01:00: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580651.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580651.png" class="no-border" >}} 11. Set the rebuild index task to reorganize pages with the **Default free space per page** and select **Keep index online while indexing**: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580655.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580655.png" class="no-border" >}} ## 4 Read More diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/microsoft-sql-server-maintenance.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/microsoft-sql-server-maintenance.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/microsoft-sql-server-maintenance.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/microsoft-sql-server-maintenance.md diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database.md similarity index 97% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database.md index 7e950cae879..cce8f29405f 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database.md @@ -42,7 +42,7 @@ To restore the database, follow these steps: 3. Right-click the database, select **Tasks** > **Restore** > **Database**, which will open the **Restore Database** dialog box. 4. In the **Source** section of the **General Settings** page, specify the source and the location of the backup sets to restore by selecting **Device** > **Add** and then locating the backup file: - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database/18580646.jpg" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database/18580646.jpg" class="no-border" >}} 5. In the **Destination** section of the **General Settings** page, the **Database** field is automatically populated with the name of the database to be restored. To change the name of the database, enter the new name in this field. 6. In the **Restore plan** section of the **General Settings** page, leave the default as **To the last backup taken** or click **Timeline** to access the **Backup Timeline** dialog box where you can manually select a point in time to stop the recovery action. diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database.md similarity index 93% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database.md index 82ece380eea..052429736a8 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database.md @@ -19,7 +19,7 @@ Some of these steps are only required for specific versions of SQL Server or Men When setting up a new database for Mendix, you can leave most of the settings to the default configuration. When looking at the general settings, you only need to set up the database name. Set up the database files according to the [Microsoft SQL Server best practices](https://www.mssqltips.com/sqlservertip/4891/sql-server-installation-best-practices/). -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580676.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580676.png" class="no-border" >}} In the database options, the default properties need to be evaluated. When choosing a collation, pay attention to the type of collation you are going to use. Mendix uses UTF-8 for all data evaluation. Depending on your exact locale, you will most likely want to choose one of the `SQL_Latin1_General_` collations. The exact encoding depends on your OS. For an **en_US** installation, for example, the encoding is `CP1`. @@ -27,7 +27,7 @@ The last two collation arguments identify how sorting and uniqueness are interpr Mendix recommends using the **Simple** recovery model option. Mendix does not use the full functionality offered in the **Full** recovery model option; although you can successfully use the **Full** recovery model, it could increase the data usage of all the transactions and might slow down any rollbacks in case of an error. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580675.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580675.png" class="no-border" >}} After the database is created, the Mendix Runtime can initiate the initial setup and prepare all the tables and functions for usage by the platform. Some of these queries require `sysadmin` privileges. The `sysadmin` role can be temporarily assigned to the user, or these queries can be executed by the administrator. Other queries need privileges that are implicitly assigned to the `db_owner` role. If the user used by the Mendix Runtime does not have enough permissions for any of these queries, you can run them manually – see below for more information. diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-sql-server-user.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-sql-server-user.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-sql-server-user.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-sql-server-user.md diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user.md similarity index 87% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user.md index b7ecf9d1c7a..ed0fd9cc2e2 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user.md @@ -13,7 +13,7 @@ Since we are using an application to connect to the database we don’t want to Select the application database as the default database. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580674.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580674.png" class="no-border" >}} ## 2 Server Roles @@ -21,13 +21,13 @@ The user does not require any special server roles. SQL server requires every us You can find more information about the authorization level of the server roles on this page: [Server-level roles](https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/server-level-roles?view=sql-server-ver15) in the Microsoft SQL documentation. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580673.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580673.png" class="no-border" >}} ## 3 User Mapping With the User Mapping properties you can grant the user access to the different database. Mendix suggests you use one account per Mendix application. So this means that the user you are creating should only have access to one single application database. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580672.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580672.png" class="no-border" >}} The Mendix Runtime keeps the database consistent. This means that the runtime validates the database structure at the start-up and automatically generates the SQL scripts to update the table structure. The Mendix Service Console provides you with the option to execute these scripts directly on the database. The Mendix Runtime requires the usage of the schema ‘dbo’ @@ -42,7 +42,7 @@ Additionally, to start the application from a new `.mda` file the `view definiti Allow the user to connect to the database. If the user is Denied the privilege to connect to the engine you won’t be able to connect with your application. The credentials used for your application should have the privilege to access the database through a normal login. Otherwise SQL Server considers your account disabled. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580671.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580671.png" class="no-border" >}} ## 5 Read More diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/sql-server/troubleshooting-sql-server.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/troubleshooting-sql-server.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/ms-windows/sql-server/troubleshooting-sql-server.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/sql-server/troubleshooting-sql-server.md diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/troubleshooting-iis.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/troubleshooting-iis.md similarity index 98% rename from content/en/docs/deployment/on-premises-design/ms-windows/troubleshooting-iis.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/troubleshooting-iis.md index 9ff21cf161e..680a8cd46fe 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/troubleshooting-iis.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/troubleshooting-iis.md @@ -33,7 +33,7 @@ If there are issues with the Mendix app you should see error messages in the Men ### 2.2 Critical Files Not Found -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/troubleshooting-iis/18580723.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/troubleshooting-iis/18580723.png" class="no-border" >}} You can get this sort of error in two circumstances: diff --git a/content/en/docs/deployment/on-premises-design/ms-windows/updating-a-mendix-application.md b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application.md similarity index 75% rename from content/en/docs/deployment/on-premises-design/ms-windows/updating-a-mendix-application.md rename to content/en/docs/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application.md index 8ca0654f0de..de1e04c6bc7 100644 --- a/content/en/docs/deployment/on-premises-design/ms-windows/updating-a-mendix-application.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application.md @@ -19,19 +19,19 @@ Before every update it is recommended that you create a backup of your data and 1. If the app is currently running, make sure you stop it first, otherwise you will be unable to update. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/1_stop_service.png" alt="Step 1, Stop the app" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/1_stop_service.png" alt="Step 1, Stop the app" class="no-border" >}} 2. You can update the application by clicking on the button **Update app**. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/2_click_update.png" alt="Step 2, Start the update process" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/2_click_update.png" alt="Step 2, Start the update process" class="no-border" >}} 3. The **Update App** popup that appears shows you information about the current active app. The **App version** shows the release number of the deployment package that is currently running on this server. The **Mendix server version** shows the version of the server distribution being used by the app — this is the same as the Studio Pro version which which the deployment package was created. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/3_update_app.png" alt="Step 3, Release details and overview of all server versions" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/3_update_app.png" alt="Step 3, Release details and overview of all server versions" class="no-border" >}} 4. To update the application click **Update app**. Select the new deployment archive (.mda) and click **Open**. The update process will start immediately. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/4_browse_mda.png" alt="Step 4, Choose the latest .mda package" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/4_browse_mda.png" alt="Step 4, Choose the latest .mda package" class="no-border" >}} This process will copy the new version of the project software into the configured location. All models will be extracted, and a symbolic link to the `mxclientsystem` folder is automatically created so the JavaScript libraries can be easily included without any additional configuration in IIS. @@ -39,25 +39,25 @@ This process will copy the new version of the project software into the configur 1. After updating the Mendix application version, the Service Console may show the message `(missing)`. This means that the required server distribution is not installed on the server. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_missing.png" alt="Step 5, a missing Runtime version" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_missing.png" alt="Step 5, a missing Runtime version" class="no-border" >}} 2. There are two ways to install the required server distribution: 1. If you are online and have access to the Mendix Marketplace, click **Download server** and the correct server distribution will be fetched and installed. You will then see the following - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_download.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_download.png" class="no-border" >}} 2. If you are offline or automatic downloading fails, click **Add Server** and select the required server distribution (*.tar.gz*). The server distribution can be found under the **Related Downloads** from the specific Mendix Studio Pro version in the [Mendix Marketplace](https://marketplace.mendix.com/link/studiopro/). The server distribution is a *tar.gz* file. The Service Console will extract the server distribution to the same folder as the other server distributions. After the server distribution has been updated you will be able to start the Service using the new project and Mendix Runtime version. - {{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_select.png" alt="Step 6, Choose the correct server distribution (.tar.gz)" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_select.png" alt="Step 6, Choose the correct server distribution (.tar.gz)" class="no-border" >}} ### 3.1 Location of the Mendix Server Distributions In the Preferences of the Mendix Service Console you can configure the main directory for all applications and server distributions. You can find the installed platform version in the folder `/Servers`. This folder is located directly in the configured base path from the service console. -{{< figure src="/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/18580698.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/18580698.png" class="no-border" >}} This should be something like: diff --git a/content/en/docs/deployment/on-premises-design/security-checklist-for-your-on-premises-installation.md b/content/en/docs/developerportal/deploy/on-premises-design/security-checklist-for-your-on-premises-installation.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/security-checklist-for-your-on-premises-installation.md rename to content/en/docs/developerportal/deploy/on-premises-design/security-checklist-for-your-on-premises-installation.md diff --git a/content/en/docs/deployment/on-premises-design/setting-up-monitoring-with-new-relic.md b/content/en/docs/developerportal/deploy/on-premises-design/setting-up-monitoring-with-new-relic.md similarity index 94% rename from content/en/docs/deployment/on-premises-design/setting-up-monitoring-with-new-relic.md rename to content/en/docs/developerportal/deploy/on-premises-design/setting-up-monitoring-with-new-relic.md index 443ddca7762..2d896e8ed1d 100644 --- a/content/en/docs/deployment/on-premises-design/setting-up-monitoring-with-new-relic.md +++ b/content/en/docs/developerportal/deploy/on-premises-design/setting-up-monitoring-with-new-relic.md @@ -38,7 +38,7 @@ The configuration section in *m2ee.yaml* should look like this: Add `-javaagent:/PATH/TO/NEWRELIC.JAR` to your Java arguments in the Windows Service Console: -{{< figure src="/attachments/deployment/on-premises-design/setting-up-monitoring-with-new-relic/18580677.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/on-premises-design/setting-up-monitoring-with-new-relic/18580677.png" class="no-border" >}} {{% alert color="info" %}} After you restart the application, your data should show up in New Relic. This requires the application to send data to New Relic servers, so your firewalls should be configured to allow for this traffic. diff --git a/content/en/docs/deployment/on-premises-design/unix-like.md b/content/en/docs/developerportal/deploy/on-premises-design/unix-like.md similarity index 100% rename from content/en/docs/deployment/on-premises-design/unix-like.md rename to content/en/docs/developerportal/deploy/on-premises-design/unix-like.md diff --git a/content/en/docs/deployment/private-cloud/_index.md b/content/en/docs/developerportal/deploy/private-cloud/_index.md similarity index 98% rename from content/en/docs/deployment/private-cloud/_index.md rename to content/en/docs/developerportal/deploy/private-cloud/_index.md index 5588f78a81c..c1893754b0a 100644 --- a/content/en/docs/deployment/private-cloud/_index.md +++ b/content/en/docs/developerportal/deploy/private-cloud/_index.md @@ -51,13 +51,13 @@ If you have chosen to register a connected cluster, the Mendix Gateway Agent wil Using this channel, any Mendix user who has been given the correct authority can pass instructions to the Mendix Operator and receive status information about the cluster. This includes instructions needed to deploy an app, or to configure the environment. -{{< figure src="/attachments/deployment/private-cloud/mx4pc-architecture.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/mx4pc-architecture.png" class="no-border" >}} ### 2.2 Standalone Architecture If you have chosen to register a standalone cluster, then all communication with the Mendix Operator will be through instructions which are made directly through the Kubernetes API. These can be made manually, but are generally performed by your CI/CD pipeline. In this case, you will also have to have local source control of the Mendix app deployment packages to ensure that the deployment process can discover them. -{{< figure src="/attachments/deployment/private-cloud/mx4pc-standalone-architecture.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/mx4pc-standalone-architecture.png" class="no-border" >}} ## 3 Product Capability Comparison diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/_index.md similarity index 92% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/_index.md index 1bd4d1ee2ad..f14539ef5ba 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/_index.md @@ -9,7 +9,7 @@ weight: 10 To allow you to manage the deployment of your apps to Red Hat OpenShift and Kubernetes, you first need to create a cluster and add at least one namespace in the Mendix Portal. This will provide you with the information you need to deploy the **Mendix Operator** and **Mendix Gateway Agent** in your OpenShift or Kubernetes context and create a link to the **Environments** pages of your Mendix app through the **Interactor**. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/mx4pc-architecture.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-architecture.png" class="no-border" >}} This document explains how to set up the cluster in Mendix. @@ -47,20 +47,20 @@ Should you consider using a connected environment, the following URLs should be 1. Click [Cloud Settings](/developerportal/collaborate/general-settings/#cloud-settings) on the **Settings** page of your Mendix app. 2. Click **Mendix for Private Cloud**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image3.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image3.png" class="no-border" >}} 3. Click **Set up Mendix for Private Cloud**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image4.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image4.png" class="no-border" >}} 4. Open the [Global Navigation menu](/developerportal/global-navigation/) and select **Deployment**. 5. Select **Mendix for Private Cloud** from the top menu bar in the Mendix Portal. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} 6. Click **Register Cluster**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image6.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image6.png" class="no-border" >}} 7. Enter the following information: @@ -71,7 +71,7 @@ Should you consider using a connected environment, the following URLs should be 8. Click **Create**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/create-cluster.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/create-cluster.png" class="no-border" >}} ### 3.2.1 Adding a Namespace for Connected Cluster {#add-namespace} @@ -81,13 +81,13 @@ To add a namespace, do the following: 1. Click **Details** ({{% icon name="notes-paper-text" %}}) on the top right of the page: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/empty-cluster.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/empty-cluster.png" class="no-border" >}} - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/ClusterDetails.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/ClusterDetails.png" class="no-border" >}} 2. Click **Add Namespace**: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/namespace-details.PNG" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details.PNG" class="no-border" >}} 3. Enter the following details: * **Namespace** – this is the namespace in your platform; this must conform to the namespace naming conventions of the cluster: all lower-case with hyphens allowed within the name @@ -95,7 +95,7 @@ To add a namespace, do the following: 4. Click **Done** to create the namespace. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/add-namespace.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/add-namespace.png" class="no-border" >}} {{% alert color="warning" %}} If you have selected a *Connected Installation Type* please verify that the [Connected Environment Pre-requisites](#prerequisites-connected) are configured. {{% /alert %}} @@ -105,13 +105,13 @@ If you would like to add a namespace to be added in the Standalone cluster, do t 1. Click **Details** ({{% icon name="notes-paper-text" %}}) on the top right of the page: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/empty-cluster.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/empty-cluster.png" class="no-border" >}} - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/ClusterDetails.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/ClusterDetails.png" class="no-border" >}} 2. Click **Add Namespace**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/namespace-details-standalone.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details-standalone.png" class="no-border" >}} 3. Enter the following details: @@ -121,7 +121,7 @@ If you would like to add a namespace to be added in the Standalone cluster, do t 4. Click **Next**. 5. Once you click on **Next**, you will be redirected to the Installation pop up page from where you can download the mxpc-cli and get the command to install the namespace in the cluster. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/standalone_downloadcli.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/standalone_downloadcli.png" class="no-border" >}} For existing namespaces, if you would like to download the executables for mxpc-cli, you can go [here](https://privatecloud.mendixcloud.com/rest/internal/v1/mxpc-cli?operatorVersion=latest) @@ -138,7 +138,7 @@ You can install and run the Mendix Operator in either Global or Standard mode. I You can license the Operator and Runtime of your application by configuring the Operator configuration with License Manager details. In order to start using Private Cloud License Manager, you need to first download the PCLM executable available in the Installation page. For more information, see [Private Cloud License Manager](/developerportal/deploy/private-cloud/private-cloud-license-manager/). The PCLM executable is available for download from this page. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/PCLMDownload.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/PCLMDownload.png" class="no-border" >}} {{% alert color="info" %}} In order to configure PCLM, make sure that the Operator version is 2.11.0 and above. @@ -916,7 +916,7 @@ Once it is configured, you can manage your cluster and namespaces through the Me Go to the Cluster Manager page by clicking **Cluster Manager** in the top menu of the **Clouds** page of the Mendix Portal. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} From this page you can see a summary of your clusters with all their namespaces and an indication of the namespace status and how long it has been running (runtime). @@ -935,11 +935,11 @@ Here you can perform the following actions on the entire cluster: * When name of the cluster is changed * When cluster description is changed -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-activity-logs.PNG" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-activity-logs.PNG" class="no-border" >}} If you prefer the individual to join as a cluster manager automatically, without requiring them to manually accept the invitation, you can enable the **Automatically accept invites** option. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptClusterManager.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/AutoAcceptClusterManager.png" class="no-border" >}} {{% alert color="info" %}} The **Automatically accept invites** option is applicable only when the invited users have the same email domain as yours. @@ -979,13 +979,13 @@ See the sections below for more information. You can also delete your namespace from the cluster manager by clicking **Delete Namespace** ({{% icon name="trash-can" %}}) in the top right. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image25.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image25.png" class="no-border" >}} If there are any environments associated with the namespace, you cannot delete the namespace until the environments associated with it are deleted. When you delete a namespace, this removes the namespace from the cluster in the Mendix Portal. However, it will not remove the namespace from your platform. You will need to explicitly delete the namespace using the tools provided by your platform. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image26.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image26.png" class="no-border" >}} {{% alert color="info" %}} In the case of a Global Operator managed namespace, the managed namespace will not be deleted from the cluster. You must delete it from the cluster manually. Additionally, you also need to remove the managed namespace from the list of managed namespaces in the Operator configuration of the main namespace. @@ -1106,7 +1106,7 @@ You can also see an activity log containing the following information for all na The **Apps** tab of namespace details in the cluster manager page lists all the app environments which are deployed to this namespace. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image27.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image27.png" class="no-border" >}} If you are a team member of the app, click **Details** to go to the *Environment Details* page for that app. @@ -1192,7 +1192,7 @@ You can invite additional members to the namespace, and configure their role dep 1. The **Members** tab displays a list of current members (if any). 2. Click **Invite Member**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image28.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image28.png" class="no-border" >}} 3. Enter the **Email** of the person you want to invite. 4. If you prefer the individual to join as a namespace member automatically, without requiring them to manually accept the invitation, you can enable the **Automatically accept invites** option. @@ -1210,7 +1210,7 @@ You can invite additional members to the namespace, and configure their role dep 6. Click **Send Invite** to send an invite to this person. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptInvite.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/AutoAcceptInvite.png" class="no-border" >}} 7. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link. @@ -1224,7 +1224,7 @@ You can change the access rights for, or completely remove, existing members. 1. Make changes and click **Save**. 2. Click **Remove member** to remove this member completely. You will be asked to confirm this action. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image30.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image30.png" class="no-border" >}} #### 7.2.3 Operate {#operate} @@ -1240,13 +1240,13 @@ The specification of these pages is optional. Open the **Operate** tab, enter the URLs relevant to your namespace, and click **Save** for each one. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image32.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image32.png" class="no-border" >}} #### 7.2.4 Plans The **Plans** tab shows you the database and storage plans which are currently configured for your namespace. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image33.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image33.png" class="no-border" >}} ##### 7.2.4.1 Deactivating a Plan @@ -1286,19 +1286,19 @@ Here, you can create customized plan for your core resources. 1. Click **Add New Plan**. 2. Provide a name to the plan under **Plan Name**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/customPlan.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlan.png" class="no-border" >}} 3. Provide the required **CPU Limits**, **CPU Request**, **Memory Limit**, **Memory Request**, **Ephemeral Storage Request** and **Ephemeral Storage Limit** based on your choice. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/customPlanDetails.png" class="no-border" >}}. + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlanDetails.png" class="no-border" >}}. 4. Click **OK** button to save the customized resource plan. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/savedCustomPlan.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/savedCustomPlan.png" class="no-border" >}} 5. In order to make the customized plan available to the customer, make sure to enable the toggle button next **Use custom core resources plans**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/customPlanEnable.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlanEnable.png" class="no-border" >}} {{% alert color="info" %}} Ephemeral Storage is a temporary storage attached to the lifecycle of a pod. Hence, with the deletion of pod, the data stored in the ephemeral storage is also lost. @@ -1346,7 +1346,7 @@ The product type value to be entered is case-sensitive. Ensure that the value ma The selected product type will be applied to all environments within this namespace, and associated environments will adopt the license of this specific product type. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/Customization.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/Customization.png" class="no-border" >}} #### 7.2.9 PCLM Statistics @@ -1354,21 +1354,21 @@ This tab shows information about claimed licenses, operator licenses and runtime Select **Claim** to view a list of licenses from the license bundle which are claimed in the namespace. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/LicenseClaim.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicenseClaim.png" class="no-border" >}} Select **Operator** to view a list of all the Operator licenses in the bundle. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/OperatorList.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/OperatorList.png" class="no-border" >}} Select **Runtime** to view a list of all the Runtime licenses in the bundle. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/RuntimeList.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/RuntimeList.png" class="no-border" >}} Select **Export in Excel** to export the above lists. If you would like to see the license payload, click **Show License Payload**. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/LicensePayload.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicensePayload.png" class="no-border" >}} {{% alert color="info" %}} If you want to use the Private Cloud License Manager, the Mendix Operator must be in version 2.11.0 or later. @@ -1434,11 +1434,11 @@ When running the installation tool over SSH, make sure that the SSH client suppo ### 8.4 Configuration Tool - Known Issues -When restoring a previously saved session, some UI elements (such as drop-downs and checkboxes) will not use the saved session and will revert to their default values. +When restoring a previously saved session, some UI elements (such as dropdowns and checkboxes) will not use the saved session and will revert to their default values. For example, the **Authentication** dropdown for Postgres will always switch to `static` authentication. -Selecting the correct value from those drop-downs will restore the state of the form and any fields which might not be visible. +Selecting the correct value from those dropdowns will restore the state of the form and any fields which might not be visible. ## 9 Troubleshooting @@ -1456,21 +1456,21 @@ This section covers how to troubleshoot an issue you may find when running the i If you are unable to copy and paste in the installation tool, you may need to enable it from the Windows PowerShell Properties. Open the **Properties** menu by right clicking the header or by pressing Alt + Space. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image34.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image34.png" class="no-border" >}} Select the **Options** tab and enable **Use Ctrl+Shift+C/V as Copy/Paste** -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image35.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image35.png" class="no-border" >}} You can now copy and paste with Ctrl+Shift+C and Ctrl+Shift+V in the terminal. ### 9.2.2 Unable to Click a Button -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image36.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image36.png" class="no-border" >}} If you highlight a button instead of clicking the button, you may need to disable the **Quick Edit Mode** from the Windows PowerShell Properties. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image37.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image37.png" class="no-border" >}} After disabling the option you need to enable the new settings. You can do this by navigating to other page by pressing a shortcut key, or reopening the installer tool by closing it with **Ctrl+C** and reopening the tool with the installation command. @@ -1478,6 +1478,6 @@ After disabling the option you need to enable the new settings. You can do this Within your cluster you can run one, or several, Mendix apps. Each app runs in an environment, and each environment is in a namespace. You can see the relationship between the Mendix environments and the Kubernetes namespaces in the image below. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/mx4pc-containerized-architecture.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-containerized-architecture.png" class="no-border" >}} To ensure that every app deployed to a namespace has a unique name, the environment will have an **Environment UUID** added to the environment name when it is deployed to ensure that it is unique in the project. This also ensures the app cannot have the same name as the Mendix tools used to deploy the app. See [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/) for more information. diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive.md similarity index 97% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive.md index 86b70ebfc55..dc1354bfa20 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive.md @@ -28,7 +28,7 @@ The following parameters may be used in the commands: When using connected mode, you need to put namespace id and namespace secret as arguments. These parameters are used by the Mendix Gateway Agent to connect to the Private Cloud Portal. You can see these values in the installation command, as the -i and -s parameters, respectively. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive/installation-command.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive/installation-command.png" class="no-border" >}} ## 2 Base Installation diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-global-operator.md similarity index 87% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-global-operator.md index 97e789ee994..6672fbb508b 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-global-operator.md @@ -27,25 +27,25 @@ To install and configure the Global Operator, perform the following steps: 1. In the Private Cloud Portal, create a cluster and select **Global Installation** as the **Installation Type**. - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator1.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator1.png" class="no-border" >}} 2. Provide the **Cluster Name**, **Cluster Type** and **Description**. - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator2.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator2.png" class="no-border" >}} 3. Click **Create**. - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator3.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator3.png" class="no-border" >}} 4. After the Global Operator cluster is created, click **Add Global Operator Main Namespace**. {{% alert color="warning" %}}Ensure that you do not use a namespace that is intended to be a managed namespace, that is, a namespace where you plan to deploy a Mendix app. The Global Operator namespace must be separate from managed namespaces, otherwise you may encounter unexpected results.{{% /alert %}} - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator4.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator4.png" class="no-border" >}} 5. Provide the Global Operator **Namespace name**, select the **Installation type**, and then click **Done**. - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator5.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator5.png" class="no-border" >}} 6. Select the **Operating system** and install the Mendix Operator by performing the following steps: @@ -53,7 +53,7 @@ To install and configure the Global Operator, perform the following steps: 2. [Sign into the Platform](/developerportal/deploy/standard-operator/#openshift-signin). 3. Perform the [Base Installation](/developerportal/deploy/standard-operator/#base-installation). - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator6.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator6.png" class="no-border" >}} 7. Verify that the installation was successful by using the following command: @@ -69,15 +69,15 @@ To install and configure the Global Operator, perform the following steps: 9. In the Private Cloud Portal, verify that the status of the Global Operator namespace is *Connected*, as in the following figure: - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator7.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator7.png" class="no-border" >}} 10. Click **Namespaces** to go to the **Namespaces Overview** page. - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator8.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator8.png" class="no-border" >}} 11. Install the managed namespace under the Global Operator namespace by clicking **Add Managed Namespace**. - {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator9.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/global-operator/global-operator9.png" class="no-border" >}} {{% alert color="warning" %}}Ensure that you use the same name for the managed namespace in the Portal and in the cluster. Using different names may result in unwanted issues.{{% /alert %}} diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating.md similarity index 94% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating.md index 2081bec67ca..9c6790c4388 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating.md @@ -37,7 +37,7 @@ Follow these steps to export the Mendix components and store them on your local 3. Select the **Main Components** and **Storage Provisioners** you want to export. 4. Enter the version numbers of any Mendix Runtimes which you want to export. You can use wildcards and create a list of versions separated by commas. For example `8.12.*, 7.23.6.*` will export all patch versions of the Mendix 8.12 runtime and the published build of the Mendix 7.23.6 runtime. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating/export.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating/export.png" class="no-border" >}} 5. Click the **Clear cache** button, which will trigger the deletion of local image cache, otherwise the cache is reused when redownloading the same images. 6. Click the **Check for updates** button, which is used to verify that the hash of your downloaded images matches with the latest remote images. @@ -47,7 +47,7 @@ Follow these steps to export the Mendix components and store them on your local {{% alert color="info" %}} To avoid downloading too many images, there is a default limit on the number of images that will be downloaded. You can check the current limit by running the following command: `./mxpc-cli registry-migration --help` -Since version 2.10.2 of `mxpc-cli`, you can change this limit by using a `--max-images` command-line argument, for example, `mxpc-cli registry-migration --max-images=50`. +Since version 2.10.2 of `mxpc-cli`, you can change this limit by using a `--max-images` commandline argument, for example, `mxpc-cli registry-migration --max-images=50`. {{% /alert %}} ## 5 Import Mendix Components Into Your Own Registry @@ -71,7 +71,7 @@ Perform the following steps. {{% alert color="info" %}}You can only choose components which you exported in the previous section, [Export Mendix Components](#export).

**ALL** runtime versions you exported will be imported – you cannot choose which versions are imported{{% /alert %}} - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating/import.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating/import.png" class="no-border" >}} 6. Click **Import components**. @@ -104,7 +104,7 @@ Click **Apply Configuration** to apply the configuration to your namespace, as n ### 6.3 Upgrade Cluster{#upgrade-cluster} {{% alert color="info" %}} -Make sure that you are in the right Kubernetes context before upgrading the namespace. +Make sure that you are in the right kubernetes context before upgrading the namespace. {{% /alert %}} If you have already installed and configured a namespace, but would like to upgrade it to the current Mendix for Private Cloud version, diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-registry.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-registry.md similarity index 98% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-registry.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-registry.md index c644cd105c2..8525e9726e0 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-registry.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-registry.md @@ -44,7 +44,7 @@ In all other cases, Mendix for Private Cloud will use HTTPS to access the regist ### 1.3 Push and Pull URLs -Mendix for Private Cloud builds images from inside the cluster. After an image is built, the Mendix Operator sets (updates) image URLs of the app's Kubernetes Deployment resource; +Mendix for Private Cloud builds images from inside the cluster. After an image is built, the Mendix Operator sets (updates) image URLs of the app's Kubernetes Deployment resouce; to start a copy of the app, Kubernetes will pull the image directly from the registry. If the registry is hosted externally (outside the cluster), there is no difference between connecting to the registry from a pod in the cluster, or from the cluster node. However, if the registry is hosted in the cluster, there are the following differences: @@ -129,7 +129,7 @@ To use ECR with the Mendix Operator, you must do the following steps: 1. Open the role for editing and add an entry for the ServiceAccount (or ServiceAccounts) to the list of conditions: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} 2. For the second condition, copy and paste the `sts.amazonaws.com` line; replace `:aud` with `:sub` and set it to `system:serviceaccount::`. You can specify any serviceaccount name here (for simplicity, Mendix recommends using `mendix-builder`). For example, if the Mendix Operator is installed into the `mynamespace` namespace, set the value to `system:serviceaccount:mynamespace:mendix-builder`. @@ -143,7 +143,7 @@ Use the following configuration options: * **Pull URL** - specify the registry IP address returned by `oc get svc` earlier * **Registry name** - specify the repository name you created on step 1, for example: `mendixapps/mynamespace` * **Region** - specify the ECR region, for example `eu-west-1` -* **Authentication** - choose the authentication mode, *Kubernetes Service Account* (recommended) or *AWS Static Credentials* (not recommended by AWS) +* **Authentication** - choose the authentication mode, *Kubernetes Service Account* (recommended) or *AWS Static Credentials* (not recommented by AWS) * **IAM Role ARN** - the role ARN you created on step 3 * **K8s Service Account** - the Kubernetes service account that the Mendix Operator should use for authentication; it should match the service account name specified on step 4; the account will be created automatically when you apply the changes * **Access Key ID** - the IAM access key to use for static authentication (only when using the *AWS Static Credentials* mode) @@ -174,7 +174,7 @@ To use ACR with the Mendix Operator, you will need to: Write down the `USER_ASSIGNED_CLIENT_ID`, it will be needed later. -3. Open the ACR Access Control (IAM) tab, and add an `AcrPush` role assignment to the Managed Identity created on step 2. +3. Open the ACR Access Control (IAM) tab, and add an `AcrPush` role assigment to the Managed Identity created on step 2. Use the following configuration options: @@ -230,7 +230,7 @@ Use the following configuration options: * **Registry name** - the repository name, for example: `mendixapps/mynamespace`. * For some registries, the repository might need to be created first. * Registries could also have security or technical limitations on what can be specified as the repository name. -* **With authentication** - allows to specify the username and password used to access the registry. This is required for almost all registries, the only exception is self-hosted registries in test environments such as MicroK8s, k3s or Minikube. +* **With authentication** - allows to specify the username and password used to access the registry. This is required for almost all registries, the only exception is self-hosted registries in test envrionments such as MicroK8s, k3s or Minikube. * **Add credentials to pull secrets in default service account** - if your cluster is not using built-in authentication, checking this option will automatically image pull credentials to the `default` Kubernetes ServiceAccount. This would enable authentication when pulling app images. #### 2.6.1 Example Configurations @@ -277,7 +277,7 @@ To access quay.io, you will need to create a robot account, and give this accoun | Password | Token (password) for a user or account with push and pull permissions | Check your image registry documentation to see if repositories can be created automatically (on push) or need to be pre-created. -Some registries impose limitations on repository names, for example the repository path cannot have more than three parts. +Some registries impose limitations on repository names, for example the repositiry path cannot have more than three parts. ### 2.8 Existing Docker Registry Secret diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md similarity index 99% rename from content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md index a933bd4ff33..645a3e6f9f9 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md @@ -162,7 +162,7 @@ To create a new database, do the following steps: * **Validate** – Checks that you have provided all the required values and that they are in the correct format. * **Connection validation** – Checks whether the specified storage plan has been successfully created. This does not guarantee that the storage instance will be created successfully when the configuration is applied, so to fully test a database plan, you will need to test it by [creating a temporary test environment](#typical-workflow). -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/database-plan-config.png" alt="Database Plan Configuration" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/database-plan-config.png" alt="Database Plan Configuration" class="no-border" >}} {{% alert color="info" %}} You cannot create multiple database plans at the same time. Run the configuration tool multiple times to create several database plans. @@ -374,7 +374,7 @@ AWS IRSA allows a Kubernetes Service Account to assume an IAM role. For this to 1. Open the role for editing and add an entry for the ServiceAccount (or ServiceAccounts) to the list of conditions: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} {{% alert color="info" %}}For Global Operator installations, you must specify the managed namespace in the **Namespace** field.{{% /alert %}} @@ -606,7 +606,7 @@ To connect to an Azure SQL Server, the Kubernetes cluster must be added to the l SQL server databases are automated, on-demand databases. The **SQL Server** plan offers a good balance between automation, ease of use, and security when using Microsoft SQL Server or Azure SQL. If you would like to have more control over database configuration, consider using the [JDBC plan](#database-jdbc) instead. {{% alert color="info" %}} -This section provides technical details on how managed identity authentication works with Azure SQL. If you just need instructions to get started, the [Azure managed Identity-based storage walkthrough](#walkthrough-azure-azwi) provides a quick start guide to set the Mendix Operator to manage a Postgres database, SQL Server and Blob Storage account using managed identity authentication. +This section provides technical details on how managed identity authentication works with Azure SQL. If you just need instructions to get started, the [Azure managed Identity-based storage walkthrough](#walkthrough-azure-azwi) provides a quick start guide to set the Mendix Operator to manage a Postgres database, SQL Server and Blob Storage account using managed identity authenticaiton. {{% /alert %}} ##### 2.5.2.1 Prerequisites @@ -1232,7 +1232,7 @@ AWS IRSA allows a Kubernetes Service Account to assume an IAM role. For this to 1. Open the role for editing and add an entry for the ServiceAccount (or ServiceAccounts) to the list of conditions: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} 2. For the second condition, copy and paste the `sts.amazonaws.com` line; replace `:aud` with `:sub` and set it to `system:serviceaccount::`. @@ -1862,7 +1862,7 @@ Before you begin, you need to create an EKS cluster and install Mendix for Priva Navigate to the EKS cluster details and write down the **OpenID Connect provider URL**: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/IRSA-OIDC.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/IRSA-OIDC.png" class="no-border" >}} IRSA authentication uses the same AWS IAM Role and Kubernetes Service Account to authenticate with AWS services. It is not possible to assign more than one IAM Role or Kubernetes Service Account to a Mendix app environment. To avoid conflicts, IAM roles and service accounts will be managed by the S3 blob file storage provisioner. The Postgres provisioner only creates a database and Postgres user (Postgres role), but does not manage IAM roles. To use IAM authentication, the database and blob file storage plans need to be managed together - the IAM policy is shared, and grants access to the database and S3 bucket. @@ -1901,11 +1901,11 @@ To configure the required settings for an RDS database, do the following steps: * The database **Endpoint** from the **Connectivity & security** tab: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Endpoint.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Endpoint.png" class="no-border" >}} * The **Master username** and **Resource ID** from the **Configuration** tab: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Connection.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Connection.png" class="no-border" >}} 4. Download the [RDS TLS certificates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions) and save them into a Kubernetes secret (replace `{namespace}` with the namespace where the Mendix Operator is installed): @@ -2021,7 +2021,7 @@ Create a new IAM role. 1. Open the role for editing and add an entry for the ServiceAccount to the list of conditions: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} 2. For the second condition, copy and paste the `sts.amazonaws.com` line; replace `:aud` with `:sub` and set it to `system:serviceaccount::`. diff --git a/content/en/docs/deployment/private-cloud/private-cloud-data-transfer.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-data-transfer.md similarity index 99% rename from content/en/docs/deployment/private-cloud/private-cloud-data-transfer.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-data-transfer.md index 85df24cf7b8..9d286277800 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-data-transfer.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-data-transfer.md @@ -214,7 +214,7 @@ If you need to export or import data from an environment that uses AWS IRSA auth 1. Open the role for editing and add an entry for the ServiceAccount (or ServiceAccounts) to the list of conditions: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} 2. For the second condition, copy and paste the `sts.amazonaws.com` line; replace `:aud` with `:sub` and set it to `system:serviceaccount::`. diff --git a/content/en/docs/deployment/private-cloud/private-cloud-deploy.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-deploy.md similarity index 89% rename from content/en/docs/deployment/private-cloud/private-cloud-deploy.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-deploy.md index 6cfc23d3279..f6c2453db40 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-deploy.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-deploy.md @@ -18,7 +18,7 @@ To deploy to a namespace in a **standalone** cluster, you provide the CRs throug Within your namespace you can run one, or several, Mendix apps. You can see the relationship between the Mendix environments and the Kubernetes namespaces in the image below. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/mx4pc-containerized-architecture.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/mx4pc-containerized-architecture.png" class="no-border" >}} Because you can run several Mendix apps in the same namespace, each environment will have an **Internal Name** (UUID) added when the app is deployed to ensure that it is unique in the project. You should not use the same name as the Mendix tools used to deploy the app. See the section [Reserved Names for Mendix Apps](#reserved-names), below. @@ -43,13 +43,13 @@ When you first create your app, it will be set to deploy to the Mendix Cloud. Yo 1. Open your app in [Apps](https://sprintr.home.mendix.com/). - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image2.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image2.png" class="no-border" >}} 2. Open the **Settings** page. 3. Click **Cloud Settings**. 4. In the **Mendix for Private Cloud** section, click **Set up**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/SetupButton.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/SetupButton.png" class="no-border" >}} ### 3.2 Creating a Deployment Package {#create-deployment-package} @@ -62,27 +62,27 @@ Deployment package creation for Mendix versions 7 and below is no longer support 1. Open your app in [Apps](https://sprintr.home.mendix.com/). 2. Go to the **Environments** page and click **Create Deployment Package**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image9.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image9.png" class="no-border" >}} 3. Select the branch which contains the commit for which you want to create a deployment package and click **Next**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image10.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image10.png" class="no-border" >}} 4. Select the revision/commit for which you want to create a deployment package and click **Next**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image11.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image11.png" class="no-border" >}} 5. Enter a **New version** and **Tag description** according to your own deployment procedure. 6. Select an environment in **Autodeploy** if you want to deploy and start your package immediately. You need to make sure that the environment is ready using the techniques described in the [Deploying the Deployment Package](#deploy-package) section below, where you can also see how to deploy a deployment package manually. 7. Click **Build this revision.** - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image12.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image12.png" class="no-border" >}} 8. Confirm the information message and you will be returned to the **Environments** page. 9. Once the deployment package is created, an **Unlock** icon is displayed by the **Details** button. This indicates that the created deployment package is not deployed in any environment yet. If you want to save a deployment package for future use, you can lock the deployment package by clicking the **Lock** button. This ensures that the locked deployment packages cannot be deleted until unlocked again. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/lock.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/lock.png" class="no-border" >}} {{% alert color="info" %}} Alternatively, you can upload an existing MDA by clicking **Upload**. @@ -92,7 +92,7 @@ Alternatively, you can upload an existing MDA by clicking **Upload**. When deploying your app for the first time, there will be no environments available. Before creating an environment, make sure that you have created/uploaded deployment package. The **Environments** page for your app in [Apps](https://sprintr.home.mendix.com/) will show you the current status. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image5.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image5.png" class="no-border" >}} {{% alert color="warning" %}} All environments are defined as production environments, which means that [security in the app must be set to `Production`](/refguide/app-security/). You will not receive an error if security is set off, but the deployment will appear to hang with a spinner being displayed. @@ -100,7 +100,7 @@ All environments are defined as production environments, which means that [secur 1. Click **Create Environment**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/selectDeploymentpackage.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/selectDeploymentpackage.png" class="no-border" >}} 2. Select the deployment package from the list of deployment packages and click **Next**. @@ -108,7 +108,7 @@ All environments are defined as production environments, which means that [secur {{% alert color="info" %}}You can change the internal name if you wish, but do not reuse one which has already been used in this namespace, even if the environment it was used for has been deleted.{{% /alert %}} - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/customizeEnvironmentPage1.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/customizeEnvironmentPage1.png" class="no-border" >}} {{% alert color="warning" %}}In the case of the Global Operator, do not use the same internal names for the managed namespaces under the same Global Operator namespace. Using the same internal name may result in unwanted issues.{{% /alert %}} @@ -116,17 +116,17 @@ All environments are defined as production environments, which means that [secur 5. Use the drop-down **Select Namespace** to select an existing namespace. You will see all namespaces of which you are a member. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/customizeEnvironmentNamespaceSelection.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/customizeEnvironmentNamespaceSelection.png" class="no-border" >}} 6. Enter a **Subscription Secret** if you want your app to run as a licensed app. Without a license, your app will be subjected to restrictions very similar to those listed in the [Free Apps](/developerportal/deploy/mendix-cloud-deploy/#free-app) section of *Mendix Cloud*. If you have configured **PCLM** in your namespace, the license from your license bundle will be automatically applied in the environment (with a condition that licenses should be available in the license bundle and not claimed in other environments). For more information, see [Private Cloud License Manager](/developerportal/deploy/private-cloud/private-cloud-license-manager/). - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/PCLM.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/PCLM.png" class="no-border" >}} 7. Click **Next**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/configureEnvResources.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/configureEnvResources.png" class="no-border" >}} 8. Select **Core Resources**. @@ -153,12 +153,12 @@ All environments are defined as production environments, which means that [secur {{% alert color="info" %}}If the Cluster Manager has configured a secret store for this namespace, this option will be disabled. You can find more information on configuring the secret store in [Integrate Kubernetes with Secret Stores](/developerportal/deploy/secret-store-credentials/).{{% /alert %}} - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image7.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image7.png" class="no-border" >}} 11. Click **Create Environment**. 12. You will see your new environment listed. An *in-progress* icon will be shows next to the resource plans until they have been provisioned. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image8.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image8.png" class="no-border" >}} See [Deploying the Deployment Package](#deploy-package), below, for instructions on how to check that the environment has been created successfully. @@ -185,23 +185,23 @@ You can deploy the deployment package of your app by doing the following: 3. Confirm that the **Status** is *Ready*. 4. Click **Transport**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image15.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image15.png" class="no-border" >}} 5. Change any constants in the **Constants** tab: select the constant you want to edit and then click **Edit**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/constantTab.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/constantTab.png" class="no-border" >}} 6. Toggle any scheduled events in the **Scheduled Events** tab: select the scheduled event you want to enable or disable and click **Toggle**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/scheduledevent.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/scheduledevent.png" class="no-border" >}} 7. Click **Continue** to continue to the Start Application confirmation page. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image16.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image16.png" class="no-border" >}} 8. Click Apply Changes to deploy the application to the selected environment. The app will start automatically once the deployment is successful. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/ApplyChangesPage.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/ApplyChangesPage.png" class="no-border" >}} You can find a description of what this deployment means within the Kubernetes cluster in [How the Operator Deploys Your App](#how-operator-deploys), below. @@ -219,7 +219,7 @@ After opening your app in [Apps](https://sprintr.home.mendix.com/), you can find This lists the deployment packages which have been created for this app. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image17.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image17.png" class="no-border" >}} There are five buttons: @@ -251,7 +251,7 @@ This creates a new package as described in [Creating a Deployment Package](#crea This displays details of the deployment package. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image18.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image18.png" class="no-border" >}} {{% alert color="info" %}} Should a deployment package remain unused, inactive, or unlocked for a period exceeding 2 weeks, it will be automatically deleted according to the expiry date. To retain the deployment package for future use, be sure to lock it. This also applies to deployment packages for which the status is **Failed**. @@ -362,7 +362,7 @@ This button contains a list of actions which you can perform quickly on the envi This section shows all the activities, such as creating environments and deploying apps, which have taken place in this environment. You can sort the activities in either descending or ascending date and time order. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image20.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image20.png" class="no-border" >}} ## 5 Managing Your Environments from the Environment Details Page{#environment-details} @@ -370,7 +370,7 @@ Each environment you create has an **Environment Details** page which allows you If you have any outstanding changes to your environment the page will display a warning message. If you click **Apply Changes**, the environment will be stopped and restarted. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image21.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image21.png" class="no-border" >}} The environment details page consists of seven tabs: @@ -388,7 +388,7 @@ These tabs are described below. The general tab shows information about your running app. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image22.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image22.png" class="no-border" >}} Most of the information is self-explanatory, but the status information gives you a quick summary of the status of the environment and the app deployed there. The **Source** field shows how the environment was created - by using the Portal or the [API](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/) @@ -432,7 +432,7 @@ Allows you to deploy the deployment package in the current environment to anothe This allows you to scale your app by increasing the number of replicas. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image23.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image23.png" class="no-border" >}} To apply the new value, click **Restart the App and Scale**. Because you restart your app, it will be unavailable for a short time. @@ -460,7 +460,7 @@ If the cluster is standalone, or the Mendix Gateway Agent is not connected for s If the environment cannot be deleted, you will receive a warning, but can go ahead and remove it from the Mendix Portal. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/delete-environment.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/delete-environment.png" class="no-border" >}} For a *connected* cluster, the top level MendixApp CRD will be deleted from the namespace – this will cause the following environment resources set up by the Operator to be garbage collected: @@ -502,7 +502,7 @@ When the namespace in which the environment is deployed is configured with PCLM * **Runtime Product Type** - The product type currently provisioned for Runtime license. * **License Provision Error** - If the licenses are not provisioned successfully for Runtime, then the error message would be displayed under this section. Example: When there are not enough Runtime license in the bundle or requested product type is not available in License bundle. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/LicensePCLM.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/LicensePCLM.png" class="no-border" >}} #### 5.1.4 Security @@ -516,7 +516,7 @@ Your app can only be deployed to a production environment if [security in the ap The **Model Options** tab allows you to change the configuration of scheduled events and constants in your app. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/image24.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image24.png" class="no-border" >}} To toggle any scheduled events, select the scheduled event you want to enable or disable and click **Toggle**. You can also export the scheduled events to an Excel file by selecting **Export Constants to Excel**. @@ -534,13 +534,13 @@ If you change the data type and value in the .mpr file, the changes are visible On the Network tab, you add client certificates (in the PKCS12 format) or certificate authorities (in the PEM format) for outgoing connections. These will be used when your application initiates SSL/TLS connections. This works in the same way as the Network tab for deployments to the Mendix Cloud. For more details on these, see the [Network Tab](/developerportal/deploy/environments-details/#network-tab) section of *Environment Details*. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/network-tab.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/network-tab.png" class="no-border" >}} ### 5.4 Runtime Tab {#runtime-tab} On the Runtime tab, you can change various runtime settings for your app environment. This works in the same way as the Runtime tab for deployments to the Mendix Cloud. For more details on these, see the [Runtime Tab](/developerportal/deploy/environments-details/#runtime-tab) section of *Environment Details*. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/runtime-tab.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/runtime-tab.png" class="no-border" >}} {{% alert color="info" %}} When you use some settings on the Runtime tab for Mendix for Private Cloud they may work differently from how they work in the Mendix Cloud. @@ -554,11 +554,11 @@ If the custom runtime settings are configured in both the CSI Secrets Storage an On the **Log Levels** tab, you can change the log levels which are used for the log nodes in your app. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-1.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-1.png" class="no-border" >}} The **NODE** is a **Log node name** that you specified in your Mendix application. In the example below, the constant `MyFirstModule.LogNode` is used as a log node name. In this case you need put the *value* of the constant (in this case, `Test Service`) as a NODE on the Log Levels tab. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-2.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-2.png" class="no-border" >}} You can find your logs in your Mendix application pod inside the Mendix container using the command below: @@ -568,7 +568,7 @@ kubectl logs -c mendix This might produce the log below for the example described above. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-3.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-3.png" class="no-border" >}} For more information, see the [Log Levels Tab](/developerportal/deploy/environments-details/#log-levels) section of *Environment Details*. @@ -582,23 +582,23 @@ In the TLS pane, you can choose whether to **Apply Default Configuration** or a If you are using a version of Mendix Operator before 1.5.0, the settings in this tab will have no effect and the default configuration will be applied. {{% /alert %}} -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/tls-configuration.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/tls-configuration.png" class="no-border" >}} If you choose a custom TLS configuration, you will need to enter the following information: * Enable TLS – is TLS enabled for this environment? -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/enable-tls.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/enable-tls.png" class="no-border" >}} * Use existing TLS secret or add new TLS private key and certificate? -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/choose-secret.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/choose-secret.png" class="no-border" >}} * Existing Secret Name – if you choose an existing TLS secret then you will be asked to enter its name * TLS Private Key File and TLS Certificate File – if you choose to add a new key you will need to upload these two files -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/new-tls-key.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/new-tls-key.png" class="no-border" >}} Click **Save** to confirm your new configuration. @@ -608,7 +608,7 @@ You will receive a warning that you have made some changes. Click **Apply Change On the Debugger tab you can set up and view the credentials you need to debug your app when it is running in your private cloud. For more information see [Debugging Microflows Remotely](/refguide/debug-microflows-remotely/#private-cloud). -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/debuggerTab.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/debuggerTab.png" class="no-border" >}} {{% alert color="info" %}} If the Debugger password is configured in both the CSI Secrets Storage and another location (such as the Mendix Portal or MendixApp CR), the secret storage configuration has a higher priority and overrides the value specified elsewhere. @@ -664,7 +664,7 @@ Both commands should return an empty list. If the Operator fails to deprovision an app's database or file storage, the `*-database` or `*-file` Pod will fail with an Error state: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/deprovision-failed.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/deprovision-failed.png" class="no-border" >}} To force removal of a StorageInstance `{name}`, run: @@ -839,7 +839,7 @@ If your application keeps restarting unexpectedly, check your application log fo The Mendix Operator is another app within your private cloud namespace. It is triggered when you provide a CR file. This can either be through the Mendix Portal, for a connected cluster, or through the command line, for a standalone cluster. The process looks like this: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/mx4pc-operator-deploy.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/mx4pc-operator-deploy.png" class="no-border" >}} The Mendix Operator CR is processed by the Mendix Operator into four steps: diff --git a/content/en/docs/deployment/private-cloud/private-cloud-environments.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-environments.md similarity index 83% rename from content/en/docs/deployment/private-cloud/private-cloud-environments.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-environments.md index cf17f9722a6..cd93f72096f 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-environments.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-environments.md @@ -10,7 +10,7 @@ weight: 70 With Mendix for Private Cloud, you have more control over where the environments you need for your Mendix app are created. You can decide whether a cluster contains one namespace or several, whether a namespace contains one environment or several, and whether those environments are all for the same app, or for several. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png" alt="Example of distributing environments in different clusters" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png" alt="Example of distributing environments in different clusters" class="no-border" >}} This document discusses the recommended ways of configuring environments for Private Cloud clusters and the licensing requirements. @@ -42,7 +42,7 @@ There are two possible ways to set up your non-production (for example test and In the minimal configuration, all non-production environments are put into a single namespace. This has the benefit of simplicity. As these are not production environments it is expected that they will not have a large volume of data or users, and that the test data does not require any special security. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png" alt="Example of minimal configuration of environments where all non-production environments are created in a single namespace" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png" alt="Example of minimal configuration of environments where all non-production environments are created in a single namespace" class="no-border" >}} This approach is not recommended if you are performing stress tests on your app as it will be affected by other apps running in the same namespace. @@ -57,7 +57,7 @@ There are multiple ways you can do this, depending on your requirements. Example * Separate namespaces for each app * Separate namespaces for each business function -{{< figure src="/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-fine-grained.png" alt="Example of fine-grained configuration of environments" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-fine-grained.png" alt="Example of fine-grained configuration of environments" class="no-border" >}} The advantages of this approach are: diff --git a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-license-manager.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-license-manager.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-license-manager.md diff --git a/content/en/docs/deployment/private-cloud/private-cloud-monitor.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-monitor.md similarity index 88% rename from content/en/docs/deployment/private-cloud/private-cloud-monitor.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-monitor.md index e0cf082e9c1..74c518a469a 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-monitor.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-monitor.md @@ -325,27 +325,27 @@ If you would like to enable Prometheus scraping only for a specific environment, 1. Go to the Cluster Manager page by clicking **Cluster Manager** in the top menu of the **Clouds** page of the Mendix Portal. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} 2. Click **Details** next to the namespace where your environment is deployed. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-details.png" class="no-border" >}} 3. Click **Configure** next to the environment name where Prometheus scraping should be enabled. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image27.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image27.png" class="no-border" >}} 4. Click **Quick setup** within **Pod annotations**: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png" class="no-border" >}} 5. Check the **Prometheus Metrics** checkbox and click **Close**: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-quick-setup-prometheus.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-quick-setup-prometheus.png" class="no-border" >}} 6. Click **Apply Changes**: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-apply-annotations.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-apply-annotations.png" class="no-border" >}} @@ -397,25 +397,25 @@ There are two dashboards available at the moment. If necessary you can install b 1. Open Grafana in a web browser using the domain name, admin username and password from [Section 2](#install-grafana-loki). 2. Click **Create**, then **Import**: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import-button.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import-button.png" class="no-border" >}} 3. Then click **Upload JSON file** and select the dashboard JSON you downloaded earlier. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import.png" class="no-border" >}} 4. Select **Prometheus** from the *Prometheus data source* dropdown, and **Loki** from the *Loki data source* dropdown. If necessary, rename the dashboard and change its uid. Press **Import** to import the dashboard into Grafana. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import-settings.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import-settings.png" class="no-border" >}} ### 4.2 Using the Dashboard Click **Dashboards**, then **Manage** and click *Mendix app dashboard (native)* or *Mendix app dashboard (compatibility mode)* to open the dashboard: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/grafana-open-dashboard.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-open-dashboard.png" class="no-border" >}} Select the **Namespace**, **Environment internal name** and **Pod name** from the dropdowns to see the metrics and logs for a specific Pod: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/grafana-select-pod.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-select-pod.png" class="no-border" >}} {{% alert color="info" %}}If the dropdowns are empty, this means that no metrics are available for that date range. Select another date range in the top right corner, or check if Prometheus is set up correctly.{{% /alert %}} @@ -453,15 +453,15 @@ To set the **Metrics** and **Logs** links: 1. Go to the Cluster Manager page by clicking **Cluster Manager** in the top menu of the **Clouds** page of the Mendix Portal. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} 2. Click **Details** next to the namespace where your environment is deployed. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-details.png" class="no-border" >}} 3. Open the **Operate** tab, enter dashboard URL for the **Metrics** and **Logs** links, and click **Save** for each one. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image32.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image32.png" class="no-border" >}} @@ -522,23 +522,23 @@ In this mode, all other `runtimeMetricsConfiguration` attributes are ignored. 2. Go to the **Environments** page. 3. Click **Details** next to the environment where compatibility mode should be used. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-overview.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-overview.png" class="no-border" >}} 4. Click the **Runtime** tab. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-details-general.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-details-general.png" class="no-border" >}} 5. Click **Enable** next to the **Custom Configuration** of **Runtime Metrics Configuration**, then click **Save**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-disabled.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-disabled.png" class="no-border" >}} 6. Click **Edit** next to **Mode**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-default.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-default.png" class="no-border" >}} 7. Set **Mode** to **compatibility** and click **Save and Apply**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png" class="no-border" >}} #### 5.1.2 Enable Compatibility Metrics in Standalone Mode @@ -572,23 +572,23 @@ To completely disable metrics collection, delete the `runtimeMetricsConfiguratio 2. Go to the **Environments** page. 3. Click **Details** next to the environment where compatibility mode should be used. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-overview.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-overview.png" class="no-border" >}} 4. Click the **Runtime** tab. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-details-general.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-details-general.png" class="no-border" >}} 5. Click **Enable** next to the **Custom Configuration** of **Runtime Metrics Configuration**, then click **Save**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-disabled.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-disabled.png" class="no-border" >}} 6. Click **Edit** next to **Mode**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-default.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-default.png" class="no-border" >}} 7. Set **Mode** to **default** and click **Save and Apply**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png" class="no-border" >}} #### 5.2.2 Disable Metrics in Standalone Mode @@ -632,23 +632,23 @@ It is also possible to add extra tags (Prometheus labels) by specifying them in 2. Go to the **Environments** page. 3. Click **Details** next to the environment where compatibility mode should be used. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-overview.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-overview.png" class="no-border" >}} 4. Click the **Runtime** tab. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-details-general.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-details-general.png" class="no-border" >}} 5. Click **Enable** next to the **Custom Configuration** of **Runtime Metrics Configuration**, then click **Save**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-disabled.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-disabled.png" class="no-border" >}} 6. Click **Edit** next to **Mode**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-default.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-default.png" class="no-border" >}} 7. Set **Mode** to **default**, then click **Save**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-native.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-native.png" class="no-border" >}} 8. Set a custom value for **MxAgent Config**. @@ -657,7 +657,7 @@ It is also possible to add extra tags (Prometheus labels) by specifying them in 9. Click **Apply Changes**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-apply.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-apply.png" class="no-border" >}} #### 5.3.2 Configure additional Native Metrics options in Connected Mode @@ -665,30 +665,30 @@ After an environment is [switched into native metrics mode](#enable-native-metri 1. Go to the Cluster Manager page by clicking **Cluster Manager** in the top menu of the **Clouds** page of the Mendix Portal. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}} 2. Click **Details** next to the namespace where your environment is deployed. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-details.png" class="no-border" >}} 3. Click **Configure** next to the environment name where the native metrics mode should be used. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image27.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image27.png" class="no-border" >}} 4. Click the **Runtime** tab. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png" class="no-border" >}} 5. Set custom values for **Interval** and **MxAgent Instrumentation Config** by clicking the **Edit** button. These parameters are optional and can be left empty. For more information about **MxAgent** see [Configuring the Java Instrumentation Agent](#configuring-mxagent), below. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-native.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-metrics-native.png" class="no-border" >}} 6. Click **Apply Changes** - {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png" class="no-border" >}} #### 5.3.3 Enable Native Metrics in Standalone Mode diff --git a/content/en/docs/deployment/private-cloud/private-cloud-operator.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-operator.md similarity index 97% rename from content/en/docs/deployment/private-cloud/private-cloud-operator.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-operator.md index 15837d542a5..5ed2afebe63 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-operator.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-operator.md @@ -37,7 +37,7 @@ You can obtain the deployment package in a number of ways: * within Studio Pro, by choosing the menu option **Project > Create Deployment Package…** – see [Create Deployment Package](/refguide/create-deployment-package-dialog/) for more information * from the **Environments** page of your app in [Apps](https://sprintr.home.mendix.com/) - {{< figure src="/attachments/deployment/private-cloud/private-cloud-operator/environments-create-mda.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-operator/environments-create-mda.png" class="no-border" >}} * through a CI/CD process, such as Jenkins. The deployment package must be available over the internet without requiring authorization credentials, as these cannot be provided in the CR. @@ -229,7 +229,7 @@ You need to make the following changes: The constant name is equal to `{module-name}.{constant-name}` where {module-name} is the name of the Mendix app module containing the constant, and {constant-name} is the name of the constant. The constant name will also be visible in the constant properties (UnitTesting.RemoteApiEnabled in this example): -{{< figure src="/attachments/deployment/private-cloud/private-cloud-operator/constant-name.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-operator/constant-name.png" class="no-border" >}} Set the constant values in the **microflowConstants** value in **runtime**. For example: @@ -318,12 +318,12 @@ To build and deploy your app using the OpenShift Console, do the following: 2. Go to your project. 3. Click the **Add** button, and select **Import YAML**. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-operator/image1.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-operator/image1.png" class="no-border" >}} 4. In the **Import YAML** page, enter/paste the YML you prepared in [Editing the CR}(#edit-cr), above. 5. Click the **Create** button. - {{< figure src="/attachments/deployment/private-cloud/private-cloud-operator/image2.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-operator/image2.png" class="no-border" >}} Mendix Operator will now pick up the YAML and deploy your app. diff --git a/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-supported-environments.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-supported-environments.md diff --git a/content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/_index.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/_index.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/_index.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/_index.md diff --git a/content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-01.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-01.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-01.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-01.md diff --git a/content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02.md similarity index 91% rename from content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02.md index c4be97f3e6f..bbb043a2d68 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02.md @@ -95,7 +95,7 @@ For *Connected* clusters, Mendix for Private Cloud needs to be able to connect t The diagram below shows the steps which you need to take to install Mendix for Private Cloud in a namespace. It assumes that the Cluster Administrator has already set up the cluster so that the Mendix Portal knows about it. See [Creating a Private Cloud Cluster](/developerportal/deploy/private-cloud-cluster/#create-cluster) for more information. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-installation.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-installation.png" class="no-border" >}} First, you create the namespace in the Mendix Portal. @@ -119,13 +119,13 @@ In standalone mode, you need to create the MendixApp CR directly in your Kuberne When it finds the MendixApp CR, the Operator will initiate processing of all the `MendixApp` dependencies, as shown in the diagram below. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-deployment.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-deployment.png" class="no-border" >}} These dependency CRs include `StorageInstance`, `Build`, and `Endpoint` CRs. Each dependency CR is handled by its own controller. Once all dependencies are processed (report their status as Ready), the Operator will process the `Runtime` CR. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/crd-controller-hierarchy.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/crd-controller-hierarchy.png" class="no-border" >}} Any time a CR's status is changed, the Operator will propagate it to the `MendixApp` CR. The Agent will receive events any time the `MendixApp` CR changes its status. @@ -136,7 +136,7 @@ To ensure you see the latest status reported by the Mendix Gateway Agent in the The diagram below provides a more detailed explanation how the Mendix Operator communicates with the `StorageInstance` controller when creating a new environment. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-provision-storage.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-provision-storage.png" class="no-border" >}} The Operator doesn't communicate with the database or file storage directly, instead, the `StorageInstance` controller runs a provisioner pod (a “task” pod) to create a new storage tenant in the database or file server. The `StoragePlan` CR (created earlier when the Operator was [configured with the `mxpc-cli` configuration tool](/developerportal/deploy/standard-operator/#configure-namespace) contains blueprints for the provisioner pod, such as: @@ -164,7 +164,7 @@ For a standalone environment, you need to create the `MendixApp` CR yourself and The processing of the `MendixApp` CR is shown in the diagram below. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-build-image.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-build-image.png" class="no-border" >}} When the `Build` controller detects that the source URL (`spec.sourceURL`) in the `Build` CR has changed, it will run the build pod. The build pod will then do the following: @@ -202,7 +202,7 @@ To use an Ingress controller, you need to install it first: * Install and set up Kubernetes [External DNS](https://github.com/kubernetes-sigs/external-dns) to automatically manage your DNS server 3. Create a test ingress object and deploy a test app to verify that the network setup is working. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-ingress-controller.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-ingress-controller.png" class="no-border" >}} #### 4.3.2 Using OpenShift Routes @@ -213,15 +213,15 @@ If you are using OpenShift Routes, the OpenShift router is already configured an When a new environment is created in the Mendix Operator, the Operator will create a service object (for all endpoint types: service only, ingress, or route) together with the ingress or route object, if required. After the `Endpoint` controller successfully creates all required objects, the `MendixApp` controller will automatically set the Runtime's ApplicationRootUrl so that a Mendix app can always know its URL. Some marketplace modules, for example [SAML](https://marketplace.mendix.com/link/component/1174), need this information to work correctly. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-applicationrooturl.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-applicationrooturl.png" class="no-border" >}} When accessing an app from a web browser through an ingress or route, the path would look like this: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-ingress.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-ingress.png" class="no-border" >}} When accessing an app from a web browser through a load balancer service, the path would look like this: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-service.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-service.png" class="no-border" >}} ### 4.4 Logging and Metering @@ -232,4 +232,4 @@ For logging and metering, Mendix for Private Cloud relies on open industry stand If your cluster doesn't already have a logging and monitoring solution, you can follow [Monitoring Environments in Mendix for Private Cloud](/developerportal/deploy/private-cloud-monitor/) for information on how to install Grafana and start collecting logs and metrics from Mendix apps. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-logging-metering.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-logging-metering.png" class="no-border" >}} diff --git a/content/en/docs/deployment/private-cloud/private-cloud-tekton/_index.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-tekton/_index.md similarity index 98% rename from content/en/docs/deployment/private-cloud/private-cloud-tekton/_index.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-tekton/_index.md index 879216511a3..5860ae43e51 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-tekton/_index.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-tekton/_index.md @@ -73,7 +73,7 @@ Each Mendix pipeline can be run independently. However, the **create-app-pipelin The Mendix pipelines work together as shown in the diagram below to create the app environment, build and push an app to the environment, and, finally, configure the app. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-tekton/build-pipeline.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/build-pipeline.png" class="no-border" >}} #### 3.3.1 Mendix Pipelines @@ -101,7 +101,7 @@ You can read the official installation procedure on the [Tekton Dashboard](https Below is and example of the recommended architecture setup. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-tekton/tekton-architecture-example.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/tekton-architecture-example.png" class="no-border" >}} The example shows the following namespaces: @@ -193,7 +193,7 @@ More details on how to activate a trigger using any HTTP client are [here](#auth #### 7.2.1 GitLab Configuration To set the GitLab Token in GitLab you specify it as the **Secret Token** when creating the webhook: -{{< figure src="/attachments/deployment/private-cloud/private-cloud-tekton/gitlab-webhook.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/gitlab-webhook.png" class="no-border" >}} #### 7.2.2 Other HTTP Clients {#auth-other-clients} @@ -589,7 +589,7 @@ You can set up a [GitLab Webhook Trigger](#gitlab-webhook) to generate the build Within GitLab, set up a webhook. Use the trigger URL of the trigger you installed in the [Installing Triggers](#installing-triggers) section, and choose which push events you want to trigger the build. -{{< figure src="/attachments/deployment/private-cloud/private-cloud-tekton/gitlab-webhook.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/gitlab-webhook.png" class="no-border" >}} {{% alert color="info" %}} To fill in the **Secret token** see the [Authentication](#authentication) section. diff --git a/content/en/docs/deployment/private-cloud/private-cloud-tekton/private-cloud-tekton-airgap.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-tekton/private-cloud-tekton-airgap.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-tekton/private-cloud-tekton-airgap.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-tekton/private-cloud-tekton-airgap.md diff --git a/content/en/docs/deployment/private-cloud/private-cloud-upgrade-guide.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-upgrade-guide.md similarity index 96% rename from content/en/docs/deployment/private-cloud/private-cloud-upgrade-guide.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-upgrade-guide.md index f57a8792f4f..8950f72e85a 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-upgrade-guide.md +++ b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-upgrade-guide.md @@ -50,10 +50,10 @@ You must have the *OpenShift CLI* installed for upgrading Mendix for Private Clo 1. Follow the instructions to [Run the Configuration Tool](/developerportal/deploy/standard-operator/#running-the-tool). You will see the initial screen: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-upgrade-guide/mxpc-cli-welcome.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-upgrade-guide/mxpc-cli-welcome.png" class="no-border" >}} 2. Click **Upgrade Namespace**. You will see the screen below: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-upgrade-guide/upgrade-wizard.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-upgrade-guide/upgrade-wizard.png" class="no-border" >}} ### 3.1 Automatic Upgrade Mode diff --git a/content/en/docs/deployment/private-cloud/private-cloud-velero.md b/content/en/docs/developerportal/deploy/private-cloud/private-cloud-velero.md similarity index 100% rename from content/en/docs/deployment/private-cloud/private-cloud-velero.md rename to content/en/docs/developerportal/deploy/private-cloud/private-cloud-velero.md diff --git a/content/en/docs/deployment/private-cloud/secret-store-credentials.md b/content/en/docs/developerportal/deploy/private-cloud/secret-store-credentials.md similarity index 98% rename from content/en/docs/deployment/private-cloud/secret-store-credentials.md rename to content/en/docs/developerportal/deploy/private-cloud/secret-store-credentials.md index 177e70684b7..cfb15ce72b3 100644 --- a/content/en/docs/deployment/private-cloud/secret-store-credentials.md +++ b/content/en/docs/developerportal/deploy/private-cloud/secret-store-credentials.md @@ -352,7 +352,7 @@ To enable your environment to use [AWS Secrets Manager](https://aws.amazon.com/b 1. Open the role for editing and add an entry for the ServiceAccount (or ServiceAccounts) to the list of conditions: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png" class="no-border" >}} 2. For the second condition, copy and paste the `sts.amazonaws.com` line; replace `:aud` with `:sub` and set it to `system:serviceaccount::`. @@ -552,7 +552,7 @@ To enable your environment to use [Azure Key Vault](https://learn.microsoft.com/ 2. Select the **Enable secret store CSI driver** option. 3. Press **Apply**: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-vault/aks-enable-csi-driver.png" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-vault/aks-enable-csi-driver.png" >}} 3. Create a new Azure Key vault by using the Azure CLI or [Azure Portal](https://learn.microsoft.com/en-us/azure/key-vault/general/quick-create-portal). @@ -568,7 +568,7 @@ To enable your environment to use [Azure Key Vault](https://learn.microsoft.com/ After creating the keys, your Key vault should look like this: - {{< figure src="/attachments/deployment/private-cloud/private-cloud-vault/aks-keyvault-keys.png" >}} + {{< figure src="/attachments/developerportal/deploy/private-cloud/private-cloud-vault/aks-keyvault-keys.png" >}} 7. Create an app with the secret store enabled. If you are using connected mode, secret stores are enabled automatically if the **Enable Secrets Store** option is activated for the namespace where you create the app. For a standalone app, you must set the value of the setting `allowOverrideSecretsWithSecretStoreCSIDriver` to `true` in the Mendix app CRD. @@ -790,7 +790,7 @@ After completing the prerequisites, follow these steps to switch from password-b 2. Add the following keys to the `SecretProviderClass` and Azure Key vault: * `storage-azure-blob-endpoint` - specify the storage account's [Primary endpoint](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview#standard-endpoints); * `storage-azure-use-default-azure-credential` - set to `true` to enable managed identity authentication. -3. Open the environment's Blob Storage Account Container in the Azure portal, and [assign a Storage Blob Data Contributor role](https://learn.microsoft.com/en-us/azure/storage/blobs/assign-azure-role-data-access) to the environment's managed identity. +3. Open the envionment's Blob Storage Account Container in the Azure portal, and [assign a Storage Blob Data Contributor role](https://learn.microsoft.com/en-us/azure/storage/blobs/assign-azure-role-data-access) to the environment's managed identity. 4. Restart the Mendix app environment. ## 4 Additional Considerations {#additional-considerations} diff --git a/content/en/docs/deployment/sap-btp/_index.md b/content/en/docs/developerportal/deploy/sap-btp/_index.md similarity index 86% rename from content/en/docs/deployment/sap-btp/_index.md rename to content/en/docs/developerportal/deploy/sap-btp/_index.md index df162588f38..bd892e45a84 100644 --- a/content/en/docs/deployment/sap-btp/_index.md +++ b/content/en/docs/developerportal/deploy/sap-btp/_index.md @@ -33,11 +33,11 @@ Before you can manage your SAP BTP using the Mendix Portal, you will need to set In this scenario, you have an existing app which is running in another environment: for instance, on Mendix Cloud. To change this, open your app in [Apps](https://sprintr.home.mendix.com/), go to **Settings**, and then switch to the **Cloud Settings** tab. -{{< figure src="/attachments/deployment/sap-cloud-platform/cloud-settings.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/cloud-settings.png" class="no-border" >}} Click **Set up SAP Cloud** to go to the SAP BTP welcome page. -{{< figure src="/attachments/deployment/sap-cloud-platform/cloud-settings-landing-page.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/cloud-settings-landing-page.png" class="no-border" >}} Click **Getting Started**, then continue with [Set Up Region](#SetUpRegion). @@ -80,7 +80,7 @@ Make sure that you have enough quota in this region for your organization to run * Route * Binding to XSUAA -{{< figure src="/attachments/deployment/sap-cloud-platform/01-sap-select-region.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/01-sap-select-region.png" class="no-border" >}} If you have already logged on to SAP and your SAP session has not expired, you will only have to choose the region. If you do not have a current SAP session you will be asked for your SAP credentials as well. Providing your credentials will grant the Deployment Portal access to manage your SAP BTP account. @@ -95,7 +95,7 @@ If you have issues using SAP authentication, please refer to the reference [SAP You will now be asked to provide the final details for the SAP BTP development environment. -{{< figure src="/attachments/deployment/sap-cloud-platform/create-development.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/create-development.png" class="no-border" >}} You will be able to choose a Domain, Organization, and Space which is configured for you in this region. @@ -111,7 +111,7 @@ You can create several environments for your app. For example, you may have crea You can do this in the **Environments** page after opening your app in [Apps](https://sprintr.home.mendix.com/). -{{< figure src="/attachments/deployment/sap-cloud-platform/environments-page.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/environments-page.png" class="no-border" >}} Your Environments page will show you the following: @@ -123,11 +123,11 @@ To create a new environment, perform the following steps: 1. Click **Add Environment** to start the wizard. - {{< figure src="/attachments/deployment/sap-cloud-platform/add-environment.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/add-environment.png" class="no-border" >}} 2. Select the region where you want your app to be deployed. - {{< figure src="/attachments/deployment/sap-cloud-platform/sap-env-0.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/sap-env-0.png" class="no-border" >}} If no session is active for that region, or the current session does not have access to that region, you will be asked for your SAP credentials for that region. @@ -143,13 +143,13 @@ To create a new environment, perform the following steps: https://myapp-development.cfapps.eu10.ondemand.com ``` - {{< figure src="/attachments/deployment/sap-cloud-platform/07-sap-env-1.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/07-sap-env-1.png" class="no-border" >}} 4. Click **Next**. 5. Enter the name of the environment. This can be anything you choose: for example Test, Acceptance, or Production. - {{< figure src="/attachments/deployment/sap-cloud-platform/08-sap-env-2.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/08-sap-env-2.png" class="no-border" >}} 6. Set the size of the memory that the app needs in order to run. This can also be changed later. @@ -159,7 +159,7 @@ To create a new environment, perform the following steps: If you choose **Custom database** you will need to enter a name for the database and the plan. - {{< figure src="/attachments/deployment/sap-cloud-platform/custom-database.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/custom-database.png" class="no-border" >}} 9. Select **File Store Enabled** if your application makes use of FileDocument or Image objects. Other sorts of object do not need File Store to be enabled. @@ -171,11 +171,11 @@ To create a new environment, perform the following steps: 12. Click **Next** to create the environment and finish the setup. - {{< figure src="/attachments/deployment/sap-cloud-platform/09-sap-env-3.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/09-sap-env-3.png" class="no-border" >}} An environment is created; with more than one environment it is possible to transport your application between environments (see [Transport App Between Environments](#TransportApp), below). -{{< figure src="/attachments/deployment/sap-cloud-platform/10-sap-env-tap.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/10-sap-env-tap.png" class="no-border" >}} ## 4 Preparing Packages for Deployment @@ -205,25 +205,25 @@ You will still have to deploy your app in [Apps](https://sprintr.home.mendix.com 1. Open the app in [Apps](https://sprintr.home.mendix.com/). 2. Go to the **Environments** page. - {{< figure src="/attachments/deployment/sap-cloud-platform/environments-page.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/environments-page.png" class="no-border" >}} 3. Click **Create package from Team Server** to start the wizard. 4. Select the branch on the Team server which you want to use. - {{< figure src="/attachments/deployment/sap-cloud-platform/03-sap-select-branch.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/03-sap-select-branch.png" class="no-border" >}} 5. Select the revision of the branch you want to build. - {{< figure src="/attachments/deployment/sap-cloud-platform/04-sap-select-revision.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/04-sap-select-revision.png" class="no-border" >}} 6. Add a version number and Tag description as required. The revision number will be added to the version number automatically. - {{< figure src="/attachments/deployment/sap-cloud-platform/05-sap-define-tag.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/05-sap-define-tag.png" class="no-border" >}} 7. Click **Build this revision** to build the package. - {{< figure src="/attachments/deployment/sap-cloud-platform/06-sap-build-revision.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/06-sap-build-revision.png" class="no-border" >}} When the package is ready to be deployed, a green tick will be shown next to the deployment package. To deploy your package, follow the instructions in the [Deploy Package](#DeployPackage) section, below. @@ -237,7 +237,7 @@ Alternatively, you can upload an MDA which has already been created from the app 3. Click **Upload** to upload the MDA. - {{< figure src="/attachments/deployment/sap-cloud-platform/upload-mda.png" alt="Upload button and dialog for uploading MDAs" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/upload-mda.png" alt="Upload button and dialog for uploading MDAs" class="no-border" >}} The package will be added to the list of packages in the **Deployment Package Repository**. To deploy your package, follow the instructions in the [Deploy Package](#DeployPackage) section, below. @@ -255,15 +255,15 @@ SAP BTP [has a limit of 1.5 GB](https://help.sap.com/viewer/65de2977205c403bbc10 1. A green tick indicates that the build has finished. Click **Deploy** to deploy the package to SAP BTP. - {{< figure src="/attachments/deployment/sap-cloud-platform/sap-revision-built.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/sap-revision-built.png" class="no-border" >}} 2. Change the deployment environment if required. - {{< figure src="/attachments/deployment/sap-cloud-platform/sap-transport.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/sap-transport.png" class="no-border" >}} 3. The **Timeout** value indicates how long (in seconds) Cloud Foundry will wait between starting an app and the first healthy response from the app before deciding that the application has failed to start. For some apps, the default (60 seconds) is too short. If your app is failing to start you can try increasing this value using the **Change timeout** option. - {{< figure src="/attachments/deployment/sap-cloud-platform/sap-change-timeout.png" width="60%" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/sap-change-timeout.png" width="60%" class="no-border" >}} 4. Click **Transport** to deploy the package to the SAP environment. This will replace any current app deployed to this environment. If the app is already running, you will be asked to stop it so that your new app can be deployed. @@ -271,19 +271,19 @@ SAP BTP [has a limit of 1.5 GB](https://help.sap.com/viewer/65de2977205c403bbc10 1. You will see confirmation of the package which has been transported. - {{< figure src="/attachments/deployment/sap-cloud-platform/transport-deploy.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/transport-deploy.png" class="no-border" >}} 2. Change any constants in the Constants tab: select the constant you want to edit and then click **Edit**. - {{< figure src="/attachments/deployment/sap-cloud-platform/transport-constants.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/transport-constants.png" class="no-border" >}} 3. Toggle any scheduled events in the Scheduled Events tab: select the scheduled event you want to enable or disable and click **Toggle**. - {{< figure src="/attachments/deployment/sap-cloud-platform/transport-events.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/transport-events.png" class="no-border" >}} 4. Select any additional services you need for your app. For more information see [Binding Services](#binding-services), below. - {{< figure src="/attachments/deployment/sap-cloud-platform/transport-services.png" width="75%" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/transport-services.png" width="75%" class="no-border" >}} {{% alert color="warning" %}}In your initial deployment, do not remove any of the services with the status **Services To Be Bound**. For a new app, these services are all required for the correct deployment of the app.{{% /alert %}} @@ -291,13 +291,13 @@ SAP BTP [has a limit of 1.5 GB](https://help.sap.com/viewer/65de2977205c403bbc10 6. Click **Start Application** to start the application on SAP BTP. - {{< figure src="/attachments/deployment/sap-cloud-platform/start-application.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/start-application.png" class="no-border" >}} {{% alert color="info" %}}This will bind any services which are in the status **Services To Be Bound**.{{% /alert %}} 7. When the application has been started you will receive a confirmation message. Click **OK** and you will be taken to the Environment Details page for the selected environment. See [Environment Details](#EnvironmentDetails), below. - {{< figure src="/attachments/deployment/sap-cloud-platform/application-started.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/application-started.png" class="no-border" >}} ### 5.3 Unbinding and Deleting Service Instances @@ -305,7 +305,7 @@ If you want to remove a service instance from your environment, you can do it is 1. Click the three-dot menu for the service and select **Unbind Service** or **Delete Service**. - {{< figure src="/attachments/deployment/sap-cloud-platform/unbind-service.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/unbind-service.png" class="no-border" >}} The options will do the following: @@ -316,15 +316,15 @@ If you want to remove a service instance from your environment, you can do it is 1. Click **Transport** on the source environment you want to transport to another environment. Environments without deployed apps will have the transport button grayed out and cannot be transported. - {{< figure src="/attachments/deployment/sap-cloud-platform/transport-environments.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/transport-environments.png" class="no-border" >}} 2. Change the deployment environment if required by clicking **Change environment**. - {{< figure src="/attachments/deployment/sap-cloud-platform/transport-from-to.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/transport-from-to.png" class="no-border" >}} 3. The **Timeout** value indicates how long (in seconds) Cloud Foundry will wait between starting an app and the first healthy response from the app before deciding that the application has failed to start. For some apps, the default (60 seconds) is too short. If your app is failing to start you can try increasing this value using the **Change timeout** option. - {{< figure src="/attachments/deployment/sap-cloud-platform/sap-change-timeout.png" width="60%" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/sap-change-timeout.png" width="60%" class="no-border" >}} 4. Click **Transport** to deploy the package to the SAP environment. This will replace any current app deployed to this environment. If the app is already running, you will be asked to stop it so that your new app can be deployed. @@ -341,7 +341,7 @@ The environment details page contains the following four tabs: Open the environment details by clicking **Details** on an environment on the Environments page of the Development Portal. You will also be taken to this page when you successfully deploy or transport your app. -{{< figure src="/attachments/deployment/sap-cloud-platform/environment-details.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/environment-details.png" class="no-border" >}} {{% alert color="info" %}}If you make changes to your app which you want be applied next time the app is deployed you must make them here. @@ -351,7 +351,7 @@ Changes made to the app in the SAP BTP cockpit are only temporary and can be ove This tab contains information on how the application is deployed on SAP BTP. -{{< figure src="/attachments/deployment/sap-cloud-platform/11-sap-env-details.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/11-sap-env-details.png" class="no-border" >}} Most of this page shows information about the app, but there are several options which allow you to change the app. @@ -385,7 +385,7 @@ Click **View Recent Log** to see recent events written to the log. You will be asked to confirm that this environment should be removed. You will also be asked to confirm that the resources associated with the environment should also be removed. Note that the default is NOT to remove the resources. -{{< figure src="/attachments/deployment/sap-cloud-platform/delete-environment.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/delete-environment.png" class="no-border" >}} {{% alert color="info" %}} If you do not select **Remove resources** in this dialog, the resources will be left in SAP BTP. This could be useful if you want to remove the environment but, for some reason, a resource cannot be removed. In this case, the resources can only be removed individually from within the SAP BTP cockpit. @@ -427,7 +427,7 @@ Click **Change** to change the subscription secret which is the code which regis This tab displays the application constants and allows you to edit them. It also lets you enable or disable scheduled events. -{{< figure src="/attachments/deployment/sap-cloud-platform/12-sap-model-options.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/12-sap-model-options.png" class="no-border" >}} {{% alert color="info" %}} You need to restart your app if you change any of these options. @@ -449,7 +449,7 @@ To change a value, select the constant you want to change and click **Edit**. This tab displays Cloud Foundry services which are bound to the app, waiting to be bound to the app, or available to be bound to the app. These are the services which are available to you in SAP BTP and are the same services that you can see in the SAP BTP marketplace. -{{< figure src="/attachments/deployment/sap-cloud-platform/service-tab.png" width="50%" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/service-tab.png" width="50%" class="no-border" >}} {{% alert color="warning" %}} There are a number of services which your Mendix app requires. If you unbind any of these services, your app will probably stop working: @@ -477,7 +477,7 @@ To connect a service in the **Available Services** section, do the following ste 3. Select a JSON **File** to upload if you need to add extra configuration. 4. Click **Connect Services**. - {{< figure src="/attachments/deployment/sap-cloud-platform/service-connect.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/service-connect.png" class="no-border" >}} The services you have selected will be added as **Services To Be Bound**. Now, you can upload JSON **File** with a configuration that will be applied to the service binding. @@ -516,7 +516,7 @@ If you no longer require a service, you can unbind it or remove it from your app * **Unbind Service** – unbind the service instance and move it to the **Services To Be Bound** section — the service will be bound again next time your app is restarted * **Delete Service** – unbind the service instance from the application and delete the service instance from your environment - {{< figure src="/attachments/deployment/sap-cloud-platform/service-unbind.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/service-unbind.png" class="no-border" >}} 3. Confirm by clicking the appropriate button @@ -525,7 +525,7 @@ If you no longer require a service, you can unbind it or remove it from your app * **Delete** – if you want to unbind more services or do not want the change to happen immediately, then you can choose *Delete*. However, this may leave the app in an unstable state as the service will be deleted from the environment * **Cancel** – do not delete or unbind this service - {{< figure src="/attachments/deployment/sap-cloud-platform/service-unbind-warning.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/service-unbind-warning.png" class="no-border" >}} Once the service is deleted, it is deleted from the app environment and returned to the list of **Available Services**. If the service is unbound but not deleted, it is returned to the list of **Services To Be Bound**, and will be rebound next time the app is restarted. @@ -551,7 +551,7 @@ If you want to change the configuration of a service which is already bound, you 3. You can either use the Configurator to create your configuration by clicking **Open Editor**, or click **Browse…** to upload an existing file as the configuration. - {{< figure src="/attachments/deployment/sap-cloud-platform/add-binding-configuration.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/add-binding-configuration.png" class="no-border" >}} See the documentation for the service you are configuring for more information. @@ -584,7 +584,7 @@ You can choose to add supported variables by selecting them from a drop-down lis * **DT_TENANT** – the unique identifier of your Dynatrace environment * **NON_MENDIX_PUBLIC_CLOUD** - must be set to **true** when using Datadog, Dynatrace, or other similar tools -{{< figure src="/attachments/deployment/sap-cloud-platform/custom-environment-variables.png" alt="List of custom environment variables" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/custom-environment-variables.png" alt="List of custom environment variables" class="no-border" >}} The variables beginning **DT_** set up Dynatrace. Setting these variables means that the Dynatrace OneAgent is loaded into your environment. You will then receive all J2EE-related metrics from your app. See [Dynatrace OneAgent](https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/) for more information. @@ -592,7 +592,7 @@ The variables beginning **DT_** set up Dynatrace. Setting these variables means You can also enter other environment variables which can be used to support Mendix features which are in beta. In this case, click **No** for **Supported** and enter the name of the variable as well as its value. -{{< figure src="/attachments/deployment/sap-cloud-platform/custom-environment-variables-unsupported.png" alt="List of custom environment variables" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/custom-environment-variables-unsupported.png" alt="List of custom environment variables" class="no-border" >}} {{% alert color="info" %}} Only use unsupported environment variables if you know exactly what you are doing. Incorrect values can prevent Mendix Runtime from starting. @@ -610,7 +610,7 @@ SAP have removed some of the PostgreSQL databases available in their marketplace Select the **postgresql-db** (PostgreSQL, Hyperscaler Option) database service. -{{< figure src="/attachments/deployment/sap-cloud-platform/postgresql-service.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/postgresql-service.png" class="no-border" >}} You will need to upload a file which contains the configuration for this database – click **Browse…** to select your configuration file. You can use the [SAP Hyperscaler PostgreSQL Configurator](#postgresql-configurator) to help you create the configuration file and find more information in the *Parameters* section of [PostgreSQL on SAP Business Technology Platform, Hyperscaler Option](https://help.sap.com/viewer/b3fe3621fa4a4ed28d7bbe3d6d88f036/Cloud/en-US/0630e03aa45d479eaf806c564dc2447a.html) in the *SAP Help Portal*. @@ -624,7 +624,7 @@ To get help to create the configuration file, click the **Configurator** button. On the new page which is displayed you can set the required values for your **SAP Hyperscaler PostgreSQL** database. Tooltips describe the values which you need to provide. -{{< figure src="/attachments/deployment/sap-cloud-platform/postgresql-configurator.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/postgresql-configurator.png" class="no-border" >}} {{% alert color="warning" %}} There is no validation on the value of the **Source Instance ID** or **Restore Time** you enter for Standard or Premium plans. If you have issues, check that you entered the correct value here. @@ -664,7 +664,7 @@ If you have issues with your app running on SAP HANA, you will need to use the S For new trial accounts, you can bind your Mendix app to a trial SAP HANA database. Just choose **hanatrial-securestore** from the drop-down of supported databases. -{{< figure src="/attachments/deployment/sap-cloud-platform/hanatrial-schema.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/hanatrial-schema.png" class="no-border" >}} Some older trial accounts do not include `hanatrial-securestore`. In this case you will get an error when you try to deploy your Mendix app saying that *provisioning has failed because service hanatrial with plan securestore is not found*. @@ -679,7 +679,7 @@ If your SAP HANA database has performance issues, you may be able to improve per * Schema * Password * User - {{< figure src="/attachments/deployment/sap-cloud-platform/binding-credentials.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/binding-credentials.png" class="no-border" >}} 2. Go to the [Runtime tab](#runtime-tab) of your app environment 3. Enter the following unsupported environment variables with the associated values, using the values taken from the service binding credentials: | Variable | Value | @@ -711,7 +711,7 @@ If you are the last person to leave a Mendix app you can delete the app. However If you are the last member of the app development team, you will be asked if you want to delete the app. -{{< figure src="/attachments/deployment/sap-cloud-platform/delete-app.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/delete-app.png" class="no-border" >}} {{% alert color="info" %}} This will not stop the app and delete the deployment of the app in SAP BTP. @@ -729,7 +729,7 @@ If you encounter any issues with your apps on SAP BTP, use the following trouble If you add an environment and it fails to be created it will be shown with a red symbol next to it on the Environments page: -{{< figure src="/attachments/deployment/sap-cloud-platform/failed-environment.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/failed-environment.png" class="no-border" >}} #### 10.1.1 Cause @@ -737,15 +737,15 @@ This could be caused by exceeding your organization quota limit for a service wh 1. Click **Details** next to the failed environment. - {{< figure src="/attachments/deployment/sap-cloud-platform/failed-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/failed-details.png" class="no-border" >}} 2. Click **Details** on the error message at the top of the page. - {{< figure src="/attachments/deployment/sap-cloud-platform/failed-more-details.png" class="no-border" >}} + {{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/failed-more-details.png" class="no-border" >}} A more detailed description of the reason why the environment creation failed will be displayed. -{{< figure src="/attachments/deployment/sap-cloud-platform/failed-description.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/failed-description.png" class="no-border" >}} #### 10.1.2 Solution @@ -755,7 +755,7 @@ Resolve the issue described in the error message. Under some circumstances an app with a service in the **Services To Be Bound** status will not restart. You will get an error with *Could not bind service...* in the details. -{{< figure src="/attachments/deployment/sap-cloud-platform/service-bind-error.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/service-bind-error.png" class="no-border" >}} #### 10.2.1 Cause @@ -775,13 +775,13 @@ If an app is deployed to SAP using the Studio Pro **Run** or **Publish** button The deployment fails because the marketplace services have not been bound. -{{< figure src="/attachments/deployment/sap-cloud-platform/error-desktop-modeler.png" width="50%" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/error-desktop-modeler.png" width="50%" class="no-border" >}} #### 10.3.1 Solution If you use the Mendix Portal to look at the details of the environment to which you are deploying, you will see that the services are still waiting to be bound. -{{< figure src="/attachments/deployment/sap-cloud-platform/error-not-bound.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-cloud-platform/error-not-bound.png" class="no-border" >}} Start the app from the Mendix Portal to bind the services. Once they are bound, you can deploy your app from Studio Pro, as usual. diff --git a/content/en/docs/deployment/sap-btp/sap-autoscaler.md b/content/en/docs/developerportal/deploy/sap-btp/sap-autoscaler.md similarity index 89% rename from content/en/docs/deployment/sap-btp/sap-autoscaler.md rename to content/en/docs/developerportal/deploy/sap-btp/sap-autoscaler.md index 7f5ca5b9018..f3a9541eaec 100644 --- a/content/en/docs/deployment/sap-btp/sap-autoscaler.md +++ b/content/en/docs/developerportal/deploy/sap-btp/sap-autoscaler.md @@ -20,7 +20,7 @@ The **autoscaler** service can be found on the [Services Tab](/developerportal/d Selecting the **autoscaler** service expands the entry to allow you to enter more details about the service you wish to bind, namely the **Plan** and the **File** which contains the configuration. -{{< figure src="/attachments/deployment/sap-autoscaler/autoscaler-service.png" alt="Autoscaler service on the environment details page" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/autoscaler-service.png" alt="Autoscaler service on the environment details page" class="no-border" >}} You need to specify the following: @@ -101,13 +101,13 @@ Click **Add rule** or **Add another rule** (if rules already exist) to add a new You need to enter the information requested on the following screen. A tooltip explains what needs to be entered for each value: -{{< figure src="/attachments/deployment/sap-autoscaler/add-specific-date.png" alt="Add specific date rule dialog" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/add-specific-date.png" alt="Add specific date rule dialog" class="no-border" >}} Click **Add Rule** to add this rule. The new rule, and any existing rules will be shown in the **Configurator** as shown below. -{{< figure src="/attachments/deployment/sap-autoscaler/specific-date.png" alt="Existing specific date rule" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/specific-date.png" alt="Existing specific date rule" class="no-border" >}} You can collapse the view of existing rule by clicking **-** and expand it again with the **+**. You can also edit an existing rule by clicking **Edit** and delete an existing rule by clicking **Delete**. @@ -120,7 +120,7 @@ Select whether you want to add a rule for days of the week (for example, every M You need to enter the information requested on the following screen. A tooltip explains what needs to be entered for each value: -{{< figure src="/attachments/deployment/sap-autoscaler/add-recurring-date.png" alt="Add recurring date rule dialog" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/add-recurring-date.png" alt="Add recurring date rule dialog" class="no-border" >}} Click **Add Day** to add the days to which this recurring schedule applies. If it is a rule for days of the week, day one is always Monday irrespective of any local conventions. You can add several days by using **Add Day** multiple times. @@ -128,7 +128,7 @@ Click **Add Rule** to add this rule. The new rule and any existing rules are shown in the configurator as shown below. -{{< figure src="/attachments/deployment/sap-autoscaler/recurring-date.png" alt="Existing recurring date rule" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/recurring-date.png" alt="Existing recurring date rule" class="no-border" >}} You can collapse the view of existing rule by clicking **-** and expand it again with the **+**. You can also edit an existing rule by clicking **Edit** and delete an existing rule by clicking **Delete**. @@ -148,13 +148,13 @@ Click **Add rule** or **Add another rule** (if rules already exist) to add a new You need to enter the information requested on the following screen. A tooltip explains what needs to be entered for each value: -{{< figure src="/attachments/deployment/sap-autoscaler/add-dynamic.png" alt="Add recurring date rule dialog" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/add-dynamic.png" alt="Add recurring date rule dialog" class="no-border" >}} Click **Add Rule** to add this rule. The new rule, and any existing rules are shown in the configurator as shown below. -{{< figure src="/attachments/deployment/sap-autoscaler/dynamic.png" alt="Existing recurring date rule" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-autoscaler/dynamic.png" alt="Existing recurring date rule" class="no-border" >}} You can collapse the view of existing rule by clicking **-** and expand it again with the **+**. You can also edit an existing rule by clicking **Edit** and delete an existing rule by clicking **Delete**. diff --git a/content/en/docs/deployment/sap-btp/sap-cloud-connector.md b/content/en/docs/developerportal/deploy/sap-btp/sap-cloud-connector.md similarity index 100% rename from content/en/docs/deployment/sap-btp/sap-cloud-connector.md rename to content/en/docs/developerportal/deploy/sap-btp/sap-cloud-connector.md diff --git a/content/en/docs/deployment/sap-btp/sap-destination-service.md b/content/en/docs/developerportal/deploy/sap-btp/sap-destination-service.md similarity index 91% rename from content/en/docs/deployment/sap-btp/sap-destination-service.md rename to content/en/docs/developerportal/deploy/sap-btp/sap-destination-service.md index 01f83ee5c98..48214e85178 100644 --- a/content/en/docs/deployment/sap-btp/sap-destination-service.md +++ b/content/en/docs/developerportal/deploy/sap-btp/sap-destination-service.md @@ -19,7 +19,7 @@ The SAP Destination Service will only provide the correct information when run o Your Mendix app will use destinations which are configured as part of your SAP subaccount. From your SAP BTP cockpit, you can see which destinations have been configured. -{{< figure src="/attachments/deployment/sap-destination-service/sap-cockpit-destinations.png" alt="SAP BTP cockpit - Destinations screen" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-service/sap-cockpit-destinations.png" alt="SAP BTP cockpit - Destinations screen" class="no-border" >}} It is not the aim of this document to explain how to configure destinations. For this you need to see the SAP documentation here: [SAP Business Technology Platform Connectivity: Destinations](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e4f1d97cbb571014a247d10f9f9a685d.html). @@ -31,11 +31,11 @@ Although you can use the SAP Destination Service on its own, the main use within There is one action within the OData Connector for SAP solutions module which allows you to get information about a destination. This is **Get Destination**, which is in the *SAP Destination Service* category of the microflow toolbox. -{{< figure src="/attachments/deployment/sap-destination-service/drag-get-destination.png" alt="Drag a Get Destination action from the toolbox" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-service/drag-get-destination.png" alt="Drag a Get Destination action from the toolbox" class="no-border" >}} The **Get Destination** action properties look like this: -{{< figure src="/attachments/deployment/sap-destination-service/get-destination-properties.png" alt="Get Destination properties dialog" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-service/get-destination-properties.png" alt="Get Destination properties dialog" class="no-border" >}} **Destination** is a string containing the name of the destination. This matches the name of the destination as set up in the SAP BTP cockpit. @@ -45,7 +45,7 @@ The **Get Destination** action properties look like this: By default, your destination will be found and authenticated using XSUAA. This is controlled using a constant `XSUAAEnabled` which defaults to `true`. -{{< figure src="/attachments/deployment/sap-destination-service/xsuaaenabled.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-service/xsuaaenabled.png" class="no-border" >}} Set `XSUAAEnabled` to `true` if your application is using XSUAA for user authentication, and you want to use the generated access token to authenticate with destination service. @@ -60,7 +60,7 @@ With `XSUAAEnabled` set to `false`, the destination will use the `VCAP` settings The details of your SAP destination are held in the **Destination** entity which is part of the *SAPODataConnector* domain model. The entity looks like this: -{{< figure src="/attachments/deployment/sap-destination-service/destination-entity.png" alt="Destination entity" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-service/destination-entity.png" alt="Destination entity" class="no-border" >}} This contains attributes for all the possible information about a destination, but only those attributes which are relevant to the chosen *Authentication* method will be populated with values. @@ -150,7 +150,7 @@ This is the type of authentication which you need to implement if you previously By providing the OData Connector for SAP solutions actions (*Get list* for example) with a destination of this type, you can gain access to your on-premises systems which are configured through the SAP Connectivity Service. -The attributes in the **Destination** entity which are used for *Principal Propagation* are: +The attributes in the **Destination** entity which are used for *Principal Propogation* are: * Url – the *Location* of the service * ProxyHost – the *Host* of the service @@ -170,7 +170,7 @@ You need to get the destination at least once before you perform any actions whi You should catch any exceptions when using the **Get Destination** to access the service in your microflows. -{{< figure src="/attachments/deployment/sap-destination-service/get-destination-error-flow.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-service/get-destination-error-flow.png" class="no-border" >}} If your access token has expired, you will get a return code of **401**. The access token cannot be refreshed automatically and the end-user will be signed out and will need to sign in again to get a new token. diff --git a/content/en/docs/deployment/sap-btp/sap-destination-with-rest.md b/content/en/docs/developerportal/deploy/sap-btp/sap-destination-with-rest.md similarity index 89% rename from content/en/docs/deployment/sap-btp/sap-destination-with-rest.md rename to content/en/docs/developerportal/deploy/sap-btp/sap-destination-with-rest.md index 31da809bff2..11b0e5ce75c 100644 --- a/content/en/docs/deployment/sap-btp/sap-destination-with-rest.md +++ b/content/en/docs/developerportal/deploy/sap-btp/sap-destination-with-rest.md @@ -26,13 +26,13 @@ Before starting this how-to, make sure you have completed the following prerequi In your microflow which is making a REST or SOAP call, perform a **Get Destination** action before the REST or SOAP call. This needs to use the Destination Name which is configured in a Destination on SAP BTP. -{{< figure src="/attachments/deployment/sap-destination-with-rest/rest-microflow.png" alt="REST Microflow" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-with-rest/rest-microflow.png" alt="REST Microflow" class="no-border" >}} The **Get Destination** action returns a **Destination** object. This is named as *DestinationObject* in the above example, and is used to configure the subsequent REST or SOAP call. The Destination object has the properties shown in the image below: -{{< figure src="/attachments/deployment/sap-destination-with-rest/destination-entity.png" alt="Destination entity" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-with-rest/destination-entity.png" alt="Destination entity" class="no-border" >}} ### 3.1 Configuring a REST Call @@ -52,7 +52,7 @@ The following entries are required in the **General** tab: |Username|$DestinationObject/SapConnectivityProxyCredentials| |Password|empty| -{{< figure src="/attachments/deployment/sap-destination-with-rest/rest-general.png" alt="REST general tab" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-with-rest/rest-general.png" alt="REST general tab" class="no-border" >}} #### 3.1.2 HTTP Headers Tab @@ -91,7 +91,7 @@ The following entries are required in the **Operation** tab: |Username|$DestinationObject/SapConnectivityProxyCredentials| |Password|empty| -{{< figure src="/attachments/deployment/sap-destination-with-rest/web-service-general.png" alt="SOAP web service general tab" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-destination-with-rest/web-service-general.png" alt="SOAP web service general tab" class="no-border" >}} #### 3.2.2 HTTP Headers Tab diff --git a/content/en/docs/deployment/sap-btp/sap-monitoring.md b/content/en/docs/developerportal/deploy/sap-btp/sap-monitoring.md similarity index 94% rename from content/en/docs/deployment/sap-btp/sap-monitoring.md rename to content/en/docs/developerportal/deploy/sap-btp/sap-monitoring.md index c30eb69eaac..2b665f71df8 100644 --- a/content/en/docs/deployment/sap-btp/sap-monitoring.md +++ b/content/en/docs/developerportal/deploy/sap-btp/sap-monitoring.md @@ -21,7 +21,7 @@ For information about configuring and using Kibana, see the [Kibana User Guide]( The **Logs** page in your Mendix app shows all the environments for this app. Click the **Logs** button to open the log in Kibana. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/logs/log-sap.png" alt="Logs Page SAP" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/mendix-cloud-deploy/logs/log-sap.png" alt="Logs Page SAP" class="no-border" >}} You may be asked to provide your SAP credentials before you can see the log in Kibana. diff --git a/content/en/docs/deployment/sap-btp/sap-single-sign-on.md b/content/en/docs/developerportal/deploy/sap-btp/sap-single-sign-on.md similarity index 82% rename from content/en/docs/deployment/sap-btp/sap-single-sign-on.md rename to content/en/docs/developerportal/deploy/sap-btp/sap-single-sign-on.md index 75530884749..21d3a3ff79e 100644 --- a/content/en/docs/deployment/sap-btp/sap-single-sign-on.md +++ b/content/en/docs/developerportal/deploy/sap-btp/sap-single-sign-on.md @@ -17,7 +17,7 @@ One implication of this is that you must use the same login email address for bo When you sign in to Mendix Studio Pro, you have the option to use SAP authentication or Mendix authentication. -{{< figure src="/attachments/deployment/sap-single-sign-on/mendix-login-page.png" max-width=50% >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/mendix-login-page.png" max-width=50% >}} {{% alert color="warning" %}} @@ -35,11 +35,11 @@ Enter your **Email Address** and Mendix **Password**. Click **Log in**. This wil Click **SAP** to use your SAP credentials. These credentials are region-specific, so you need to choose a region first. -{{< figure src="/attachments/deployment/sap-single-sign-on/select-sap-region.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/select-sap-region.png" class="no-border" >}} Click **Select region** and you will be asked for your SAP credentials. -{{< figure src="/attachments/deployment/sap-single-sign-on/sap-login-screen.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/sap-login-screen.png" class="no-border" >}} Enter the correct credentials and you will be signed in to Studio Pro. @@ -51,23 +51,23 @@ SAP SSO is triggered if you do not already have an active session in the SAP reg First, select a region and click **Next** -{{< figure src="/attachments/deployment/sap-single-sign-on/app-select-sap-region.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/app-select-sap-region.png" class="no-border" >}} If needed, you will be asked for credentials: -{{< figure src="/attachments/deployment/sap-single-sign-on/sap-login-screen.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/sap-login-screen.png" class="no-border" >}} Enter the correct credentials and click **SIGN IN** to continue the creation of your SAP BTP environment. ## 4 Resolving "Go back to where you originally came from" Error -{{< figure src="/attachments/deployment/sap-single-sign-on/go-back.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/go-back.png" class="no-border" >}} This error occurs when you work with SAP environments from within the Mendix Portal. As described on the error page, it occurs when you use different email addresses for signing in to Mendix platform and SAP region which you are working on. Click **Go back to where you originally came from**, and you will see another error message. Click **OK** to clear it. -{{< figure src="/attachments/deployment/sap-single-sign-on/server-error.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/server-error.png" class="no-border" >}} There are three possible solutions, depending on why the email addresses are different. Some of these can be changed within Mendix itself, but you may also need to make changes directly on the SAP site. @@ -86,7 +86,7 @@ Choose the URL for the correct region. Select the down arrow next to your email address, and this will give the option to **Sign Out**. -{{< figure src="/attachments/deployment/sap-single-sign-on/where-to.png" class="no-border" >}} +{{< figure src="/attachments/developerportal/deploy/sap-single-sign-on/where-to.png" class="no-border" >}} Click **Sign Out** and you can then return to Mendix and sign in again with an account which has the same email address as the email address you use for Mendix. diff --git a/content/en/docs/developerportal/deployment.md b/content/en/docs/developerportal/deployment.md deleted file mode 100644 index 4e2ca28a9d5..00000000000 --- a/content/en/docs/developerportal/deployment.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: "Deployment" -url: /developerportal/deploy/ -description: "Describes the Deployment section of the Apps navigation pane." -weight: 10 -no_list: false -description_list: true ---- - -## 1 Introduction - -The **Deployment** category in the **Apps** [navigation pane](/developerportal/#navigation-pane) provides access to built-in deployment and monitoring tools for your app. The pages in this category are listed below. - -{{% alert color="info" %}} -The interface and functionality of these pages vary depending on where your app is deployed. For details about the various deployment options, see the [Deployment](/deployment/) section. -{{% /alert %}} - -## 2 Environments - -For supported platforms, the **Environments** page allows you to review and configure different aspects of your app. It also allows you to deploy to your chosen platform, configure individual environments, and transport your app between staging environments. - -For details on the **Environments** pages for Mendix Cloud, Mendix for Private Cloud, and SAP deployments, see the following pages: - -* Mendix Cloud deployments – [Environments](/developerportal/deploy/environments/) -* Mendix for Private Cloud deployments – [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/#environment-details) -* SAP deployments – [SAP Business Technology Platform](/developerportal/deploy/sap-cloud-platform/#EnvironmentDetails) - -Other platforms are not currently supported on the **Environments** page; instead, you must go to the relevant platform portal to monitor and configure your environments. - -## 3 Pipelines - -The **Pipelines** page is for licensed apps deployed to Mendix Cloud. For more information, see [Pipelines](/developerportal/deploy/pipelines/). - -## 4 Software Composition - -The **Software Composition** page is for Free Apps and licensed apps running in Mendix Cloud or Mendix for Private Cloud. For more information, see [Software Composition](/developerportal/deploy/software-composition/). - -## 5 Metrics - -The **Metrics** page is for licensed apps deployed to Mendix Cloud. Metrics are not available for Free Apps deployed to Mendix Cloud. For more information, see [Metrics](/developerportal/operate/metrics/). - -If your app is deployed to SAP Business Technology Platform (SAP BTP), the **Metrics** page displays links to the SAP BTP cockpit. - -## 6 Logs - -The **Logs** page is for licensed apps deployed to Mendix Cloud. Logs are not available for Free Apps deployed to Mendix Cloud. For more information, see [Logs](/developerportal/operate/logs/). - -To configure logs if your app is running on a different cloud, go to the cloud management portal for the cloud to which your app is deployed. For more information, see [Monitoring Environments in Mendix for Private Cloud](/developerportal/deploy/private-cloud-monitor/) or [Monitoring Environments in Mendix Apps on SAP BTP](/developerportal/deploy/sap-cloud-platform/sap-monitoring/). - -## 7 Backups - -The **Backups** page is for apps deployed to Mendix Cloud. For more information, see [Backups](/developerportal/operate/backups/). - -If your app is deployed to SAP Business Technology Platform (SAP BTP) instead, the **Backups** page links to the SAP BTP cockpit. - -## 8 Alerts - -The **Alerts** page is for licensed apps deployed to Mendix Cloud. Alerts are not available for Free Apps deployed to Mendix Cloud. For more information, see [Alerts](/developerportal/operate/monitoring-application-health/). - -If your app is deployed to SAP Business Technology Platform (SAP BTP) instead, the **Alerts** page links to the SAP BTP cockpit. - -## 9 Mobile App - -On the **Mobile App** page, you can manage and publish your app in mobile app stores. For more details, see [Mobile App](/developerportal/deploy/mobileapp/). - -## 10 Webhooks - -The **Webhooks** page is for licensed apps that are deployed to Mendix Cloud or Mendix for Private Cloud. For more information, see [Webhooks](/developerportal/deploy/webhooks/). diff --git a/content/en/docs/developerportal/general/team/app-roles.md b/content/en/docs/developerportal/general/team/app-roles.md index dfdd0bf80d0..c991f873428 100644 --- a/content/en/docs/developerportal/general/team/app-roles.md +++ b/content/en/docs/developerportal/general/team/app-roles.md @@ -48,7 +48,7 @@ Every deployed app has a Technical Contact. When you view the [Settings](/develo Provide the Technical Contact with the Scrum Master role. Because the Technical Contact is the contact for regular users, they need to be able to perform app operations on behalf of all Scrum Masters. {{% /alert %}} -The Technical Contact manages the technical deployment settings of the app. The Technical Contact can be responsible for [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/) or various [deployment](/deployment/) platforms. A Mendix application is always set up and delivered with a Technical Contact assigned to it. The Technical Contact for a Free App is assigned when the app is deployed for the first time. The Technical Contact needs an MxID before Mendix can activate a license for an application. +The Technical Contact manages the technical deployment settings of the app. The Technical Contact can be responsible for [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/) or various [deployment](/developerportal/deploy/) platforms. A Mendix application is always set up and delivered with a Technical Contact assigned to it. The Technical Contact for a Free App is assigned when the app is deployed for the first time. The Technical Contact needs an MxID before Mendix can activate a license for an application. The responsibilities of a Technical Contact depend on whether you are hosting your app in Mendix Cloud or on premises. diff --git a/content/en/docs/howto/integration/exposing-data-to-bi-tools-using-odata.md b/content/en/docs/howto/integration/exposing-data-to-bi-tools-using-odata.md index 9d08329d259..927334d9cbe 100644 --- a/content/en/docs/howto/integration/exposing-data-to-bi-tools-using-odata.md +++ b/content/en/docs/howto/integration/exposing-data-to-bi-tools-using-odata.md @@ -2,7 +2,7 @@ title: "Expose Data to BI Tools Using OData" url: /howto/integration/exposing-data-to-bi-tools-using-odata/ weight: 13 -description: "Describes how to create a published OData service with resources, add the OData server to Tableau and Excel, combine resources in Tableau, and create custom queries." +description: "Describes how to create a published OData service with resources, add the OData server to Tableau and Excel, combine resources in Tableau, and create qustom queries." --- ## 1 Introduction diff --git a/content/en/docs/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors.md b/content/en/docs/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors.md index 53be4660324..8ffdcb6a96e 100644 --- a/content/en/docs/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors.md +++ b/content/en/docs/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors.md @@ -7,7 +7,7 @@ description: "Describes how to find the root cause of runtime errors via Studio ## 1 Introduction -This how to will show you how to find the information necessary to locate the root cause of a runtime error. The message displayed in the application is often vague and nondescript. Depending on the environment in which the error occurred, there are two methods for finding this information. +This how to will show you how to find the information necessary to locate the root cause of a runtime error. The message displayed in the application is often vague and non-descript. Depending on the environment in which the error occurred, there are two methods for finding this information. This how-to teaches you how to do the following: @@ -19,7 +19,7 @@ If the application is deployed from Studio Pro, the information is located in th {{< figure src="/attachments/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors/18580024.png" class="no-border" >}} -When an error occurs, a line with a red font appears in the console. Double-clicking on this line brings up the **View Log Line Details** dialog box: +When an error occurs, a line with a red font will appear in the console. Double-clicking on this line brings up the **VIew Log Line Details** pop-up window: {{< figure src="/attachments/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors/18580023.png" class="no-border" >}} diff --git a/content/en/docs/howto/monitoring-troubleshooting/manage-app-performance/_index.md b/content/en/docs/howto/monitoring-troubleshooting/manage-app-performance/_index.md index eb8135b78a2..830796f2e65 100644 --- a/content/en/docs/howto/monitoring-troubleshooting/manage-app-performance/_index.md +++ b/content/en/docs/howto/monitoring-troubleshooting/manage-app-performance/_index.md @@ -26,4 +26,4 @@ Outside Mendix Cloud, you can use the following monitoring tools: * Datadog * New Relic – see [Manage App Performance with New Relic](/howto/monitoring-troubleshooting/manage-app-performance-with-new-relic/) * Dynatrace – for example on [SAP Business Technology Platform](/developerportal/deploy/sap-cloud-platform/#runtime-tab) -* Other tools – you can see these under [Telemetry Configuration](https://github.com/mendix/cf-mendix-buildpack#telemetry-configuration) in the Mendix *Cloud Foundry Buildpack*. +* Other tools – you can see these under [Telemetry Configuration](https://github.com/mendix/cf-mendix-buildpack#telemetry-configuration) in the Mendix *Cloud Foundry Buildback*. diff --git a/content/en/docs/howto8/mobile/hybrid-mobile/build-hybrid-apps/build-hybrid-locally.md b/content/en/docs/howto8/mobile/hybrid-mobile/build-hybrid-apps/build-hybrid-locally.md index 57172e22fee..93f9c3523c1 100644 --- a/content/en/docs/howto8/mobile/hybrid-mobile/build-hybrid-apps/build-hybrid-locally.md +++ b/content/en/docs/howto8/mobile/hybrid-mobile/build-hybrid-apps/build-hybrid-locally.md @@ -205,7 +205,7 @@ You *APK* should now be generated and signed using Android Studio. The resulting ## 4 Read More -* [Deployment](/deployment/) +* [Deploy and Manage Guide](/developerportal/deploy/) * [Offline Reference Guide](/refguide8/offline-first/) * [How to Publish a Mendix Hybrid Mobile App in App Stores](/howto8/mobile/publishing-a-mendix-hybrid-mobile-app-in-mobile-app-stores/) * [Apache Cordova Reference Config.xml](https://cordova.apache.org/docs/en/latest/config_ref/) diff --git a/content/en/docs/partners/_index.md b/content/en/docs/partners/_index.md index c592a6d8298..49a77525334 100644 --- a/content/en/docs/partners/_index.md +++ b/content/en/docs/partners/_index.md @@ -6,7 +6,7 @@ weight: 50 no_list: false description_list: true cascade: - - content_type: "Strategic Partners" + - content_type: "Strategic Partners Guide" - mendix_version: 10 #This document is mapped to the landing page, update the link there if renaming or moving the doc file. --- diff --git a/content/en/docs/partners/sap/_index.md b/content/en/docs/partners/sap/_index.md index 5ac431994f2..38d0fadac55 100644 --- a/content/en/docs/partners/sap/_index.md +++ b/content/en/docs/partners/sap/_index.md @@ -38,7 +38,7 @@ The following articles contain the documentation for all platform-supported SAP The following articles contain information about deploying your Mendix app on the SAP Business Technology Platform: -* [SAP Business Technology Platform](/developerportal/deploy/sap-cloud-platform/) - provides information about deploying your app to the SAP Business Technology Platform +* [SAP Business Technology Platform](/developerportal/deploy/sap-cloud-platform/) - provides information about deployinh your app to the SAP Business Technology Platform * [Monitoring Environments in Mendix Apps on SAP BTP](/developerportal/deploy/sap-cloud-platform/sap-monitoring/) * [SAP Destination Service](/developerportal/deploy/sap-cloud-platform/sap-destination-service/) – presents details on enabling your Mendix app running on SAP BTP to use external services and systems * [Use SAP Connectivity Services with REST and SOAP](/developerportal/deploy/sap-cloud-platform/sap-destination-with-rest/) diff --git a/content/en/docs/partners/siemens/3d-viewer/_index.md b/content/en/docs/partners/siemens/3d-viewer/_index.md index 67b874f04f9..255bc29a2ab 100644 --- a/content/en/docs/partners/siemens/3d-viewer/_index.md +++ b/content/en/docs/partners/siemens/3d-viewer/_index.md @@ -326,7 +326,7 @@ If you have already deployed your app, change the existing **LicenseToken** cons #### 4.7.2 For an App Deployed in Your Own Environment -If you deploy your app in your own environment, you need to configure the license token in your own environment. For more information, see [Deployment](/deployment/). +If you deploy your app in your own environment, you need to configure the license token in your own environment. For more information, see [Deployment](/developerportal/deploy/). ## 5 Usage diff --git a/content/en/docs/private-platform/_index.md b/content/en/docs/private-platform/_index.md index 52a6611f8d1..cf37f2b353f 100644 --- a/content/en/docs/private-platform/_index.md +++ b/content/en/docs/private-platform/_index.md @@ -6,7 +6,7 @@ weight: 42 no_list: false description_list: true cascade: - - content_type: "Private Mendix Platform" + - content_type: "Private Mendix Platform Guide" - mendix_version: 10 --- diff --git a/content/en/docs/quickstarts/leading-mendix-implementation.md b/content/en/docs/quickstarts/leading-mendix-implementation.md index 8ab33d2a56d..d99055ef57a 100644 --- a/content/en/docs/quickstarts/leading-mendix-implementation.md +++ b/content/en/docs/quickstarts/leading-mendix-implementation.md @@ -625,7 +625,7 @@ When setting up your deployment strategy, it is important to look at the feature If your organization is deploying on **Private Cloud or on-prem**, please **make sure that you are ready to take on the effort and responsibility of managing all hosting and support of the application deployments**. -For a list of all the deployment options that are available, see [Deployment](/deployment/).  +For a list of all the deployment options that are available, see [Deployment](/developerportal/deploy/).  Some highlights to consider: diff --git a/content/en/docs/refguide/_index.md b/content/en/docs/refguide/_index.md index 1d5a89647f1..45e0afa6cd8 100644 --- a/content/en/docs/refguide/_index.md +++ b/content/en/docs/refguide/_index.md @@ -40,7 +40,7 @@ When it comes to testing your application, you first need to decide what you are Studio Pro allows you to run and view your app locally or in the default environment. -For more information on options for deploying your app see [Deployment](/deployment/). +For more information on options for deploying your app see [Deployment](/developerportal/deploy/). ## 3 Version Control diff --git a/content/en/docs/refguide/general/studio-pro-overview.md b/content/en/docs/refguide/general/studio-pro-overview.md index dd65b93050a..81fe1901e8e 100644 --- a/content/en/docs/refguide/general/studio-pro-overview.md +++ b/content/en/docs/refguide/general/studio-pro-overview.md @@ -44,7 +44,7 @@ Deploy your app by clicking the **Publish** or **Run Locally** ({{% icon name="c {{< figure src="/attachments/refguide/studio-pro-overview/view-and-publish.png" alt="View and Publish buttons" class="no-border" >}} -For more information on deployment in Mendix, see [Deployment](/deployment/). +For more information on deployment in Mendix, see [Deployment](/developerportal/deploy/). For more information on deploying and versioning your app, see the [Versioning an App Deployed to the Cloud](/refguide/using-version-control-in-studio-pro/#versioning-app) section in *Using Version Control in Studio Pro*. diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/use-min-older-sp.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/use-min-older-sp.md index e8f6d595836..cc29d4daf86 100644 --- a/content/en/docs/refguide/mobile/distributing-mobile-apps/use-min-older-sp.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/use-min-older-sp.md @@ -7,58 +7,81 @@ description: "This guide will help you build a MIN app compatible with a non-LTS ## 1 Introduction -The Make It Native (MIN) app allows you to test native apps in development with ease. We have also made it open source, allowing you to change it depending on your needs. You can continue to use the [Make It Native App](/releasenotes/mobile/make-it-native-parent/) we provide via the iOS App Store and Google Play Store, or you can build your own Make It Native app. +The Make It Native (MIN) app allows you to test native apps in development with ease. We have also made it open source, allowing you to change it depending on your needs. Depending on your Mendix version, you can use the MIN app in one of two ways: -A common reason to build your own Make It Native app is to support one or more development teams that work on a specific version of Mendix and require additional native dependencies. Building your own Make It Native app is an alternative to [Creating a Custom Developer App](/howto/mobile/how-to-devapps/) which adds more convenience for your developers and gives you more control over the native app. +* **Long Term Support (LTS) Studio Pro Version** — If you want to use the Make It Native app to test your native apps, you must choose a [MIN version](/releasenotes/mobile/make-it-native-parent/) compatible with your LTS version of Studio Pro. +* **Non-LTS Studio Pro Version** — If you choose use a non-LTS version of Studio Pro and still wish to use the MIN app, then you will have to manually build a version of the MIN that is compatible with your version of Studio Pro. -This guide explains how to build your own Make It Native app. +This guide explains how to complete the second bullet's task: build a MIN app compatible with a non-LTS Studio Pro version. ### 1.1 Getting Started -First things first, make sure you clone your repo: +First things first, make sure you clone your repo and install necessary software: -```bash -git clone https://github.com/mendix/make-it-native.git -cd make-it-native -``` - -#### 1.1.1 Select Mendix Version - -Next, select the Mendix version you want to build your Make It Native App for: - -```bash -git checkout > -``` - -For example, if you want to build Make It Native for Mendix 10.0.0, do the following: +1. Clone the repository: -```bash -git checkout mx/10.0 -``` - -You can find a complete list of supported Mendix versions and their branch names in the [GitHub Repository](https://github.com/mendix/make-it-native/branches/active). + ```bash + git clone https://github.com/mendix/make-it-native.git + ``` -#### 1.1.2 Install Dependencies +1. Navigate to the project directory: -Make It Native, just like any other native apps, relies on third party dependencies that must be installed. Run the following commands to do so: + ```bash + cd make-it-native + ``` 1. Install dependencies: ```bash npm install ``` -1. Install pods (only for iOS): + +1. Install pods: + ```bash - cd ios && pod install && cd .. + cd ios && pod install ``` -If either command fails, make sure you have [NodeJS](https://nodejs.org/en) and [CocoaPods](https://cocoapods.org) installed. To build Make It Native for Apple devices, you need an Apple computer. +### 1.2 Switching to the Compatible Mendix Studio Pro Branch + +To ensure that you can build and run the Make it Native (MiN) application successfully, you need to use a version of the application that is compatible with your Mendix Studio Pro version. Our repository includes multiple branches, each compatible with different versions of Mendix Studio Pro. Follow these steps to switch to the appropriate branch and build the application. + +#### 1.2.1 Identify Your Mendix Studio Pro Version -### 1.2 Additional Setup Requirements +First, confirm the version of Mendix Studio Pro you are currently using. You can find this information in the Mendix Studio Pro application under **Help** > **About Mendix Studio Pro**. + +#### 1.2.2 Switch to the Compatible Branch + +Based on your Mendix Studio Pro version, switch to the corresponding branch in our repository. + +Here are the branches available for different versions: + +| Studio Pro Version | Branch | +| -------------------------- | ------------- | +| Mendix Studio Pro 10.10.0 | `mx/10.10.0` | +| Mendix Studio Pro 10.9.0 | `mx/10.9.0` | +| Mendix Studio Pro 10.8.0 | `mx/10.8.0` | +| Mendix Studio Pro 10.7.0 | `mx/10.7.0` | +| Mendix Studio Pro 10.6.0 | `mx/10.6.0` | +| Mendix Studio Pro 10.5.0 | `mx/10.5.0` | +| Mendix Studio Pro 10.4.1 | `mx/10.4.1` | +| Mendix Studio Pro 10.3.1 | `mx/10.3.1` | +| Mendix Studio Pro LTS/9.24 | `mx/lts/9.24` | +| Mendix Studio Pro MTS/9.24 | `mx/mts/10.6` | + +Use the following Git command to switch branches: + +```bash +git checkout +``` + +Replace `` with the branch corresponding to your version of Mendix Studio Pro. + +### 1.3 Additional Setup Requirements To build and run the native mobile app successfully, you must complete several setup steps related to external services like Firebase and Google Maps. Follow the instructions below carefully. -#### 1.2.1 Setting up Firebase +#### 1.3.1 Setting up Firebase 1. Create a Firebase Project: 1. Go to the [Firebase Console](https://console.firebase.google.com/) and create a new project. @@ -72,13 +95,13 @@ To build and run the native mobile app successfully, you must complete several s 1. For Android, move the *google-services.json* file to the **android/app** directory. 1. For iOS, move the *GoogleService-Info.plist* file to the **ios/DeveloperApp** directory. -#### 1.2.2 Setting up Google Maps API +#### 1.3.2 Setting up Google Maps API -##### 1.2.2.1 Getting a Google Maps API key +##### 1.3.2.1 Getting a Google Maps API key Follow the instructions provided by Google [here](https://developers.google.com/maps/documentation/android-sdk/get-api-key) to obtain an API key. -##### 1.2.2.2 Integrate the API Key into an Android Project +##### 1.3.2.2 Integrate the API Key into an Android Project Open your *android/app/src/main/AndroidManifest.xml* file and find the section with the placeholder `{{GEO_API_KEY}}`. Replace `{{GEO_API_KEY}}` with your actual Google Maps API key: @@ -87,7 +110,7 @@ Open your *android/app/src/main/AndroidManifest.xml* file and find the section w android:value="YOUR_API_KEY_HERE"/> ``` -##### 1.2.2.3 Integrate the API Key into an iOS Project +##### 1.3.2.3 Integrate the API Key into an iOS Project To run iOS Fastlane script containing an API key, define the variable `GOOGLE_MAPS_API_KEY` before beta lane. If you run it manually in XCode, change the API key in the *ApiKeys.xcconfig* file. @@ -108,13 +131,13 @@ Fastlane is an all in one CI tool that automates the process of building and dep export PATH="$FASTLANE_PATH:$PATH" ``` -## 3 Building +## 2 Building For building iOS apps, Mendix uses Fastlane. Fastlane is an all in one continuous integration tool that automates building and deploying. For building Android apps, the process is still manual. -### 3.1 iOS +### 2.1 iOS iOS builds are produced via Fastlane. @@ -130,7 +153,7 @@ Currently submitting the app for review is a manual step, but this might change. For the **Beta** and **Release** lanes, before building, be sure to change the **VERSION_NUMBER** in the `Fastlane` config file manually. {{% /alert %}} -#### 3.1.1 Build an App for Internal Testing +#### 2.1.1 Build an App for Internal Testing To build your app for internal testing, do the following: @@ -138,7 +161,7 @@ To build your app for internal testing, do the following: 1. Run the `fastlane internal` command to build your app. 1. The output will reside in `/build/internal/output`, so grab your files from that directory. -#### 3.1.2 Releasing to TestFlight +#### 2.1.2 Releasing to TestFlight Change the VERSION_NUMBER in the `Fastlane` config file to your new version, then build: @@ -147,7 +170,7 @@ Change the VERSION_NUMBER in the `Fastlane` config file to your new version, the The script will take considerable amount of time as it also waits for processing to finish, to release a TestFlight beta test. -#### 3.1.3 Releasing to App Store +#### 2.1.3 Releasing to App Store Change the VERSION_NUMBER in the `Fastlane` config file to the new version, then build: @@ -156,7 +179,7 @@ Change the VERSION_NUMBER in the `Fastlane` config file to the new version, then The script will take considerable amount of time as it also waits for processing to finish, to release a TestFlight beta test. -### 3.2 Android +### 2.2 Android Android builds are made via Android Studio: @@ -168,9 +191,9 @@ Android builds are made via Android Studio: 1. Select `developerappRelease` from the build variants, and tick `V1` and `V2` Signatures. 1. Build your Android app. -## 4 Set Up your Developer Environment +## 3. Set Up your Developer Environment -### 4.1 iOS +### 3.1 iOS iOS applications require XCode, so we assume you have the latest version installed and ready to use. @@ -182,14 +205,14 @@ Mendix uses CocoaPods to manage the iOS dependencies, which you can set up as fo 1. Install provision profile and certificates by running `npm run ios:dev`, then enter your machine password. 1. Open the project via the `*.xcworkspace` file (not the `xcodeproj`). -#### 4.1.1 When to Re-Install CocoaPods +#### 3.1.1 When to Re-Install CocoaPods From to time you must update the native dependencies. Therefore, it is important to re-install the node modules and CocoaPods in the following cases: * After a branch switch * If the app exhibits erratic or odd behavior -### 4.2 Android +### 3.2 Android Set up your developer environment for Android as follows: @@ -201,7 +224,7 @@ Set up your developer environment for Android as follows: 1. Start a Gradle sync. 1. If successful, the green play button should be usable. -#### 4.2.1 Remote Debugging +#### 3.2.1 Remote Debugging To enable remote debugging, do the following: @@ -214,7 +237,7 @@ To enable remote debugging, do the following: 1. Select **Enable remote debugging** from the menu. 1. After the Chrome screen pops up, change its URL to *localhost:8083/debugger-ui/*. -#### 4.2.2 Build from Source +#### 3.2.2 Build from Source Building from source is required to be able to debug React Native specific code. @@ -225,7 +248,7 @@ Building from source can be done as follows: 1. Toggle `BUILD_RN_FROM_SOURCE=true` in `gradle.properties`. 1. Clean and build app. -#### 4.2.3 Remote Debugging on an Android Emulator +#### 3.2.3 Remote Debugging on an Android Emulator You cannot use `localhost`, as it points to the Android simulator instead of the host machine. To work around this, do one of the following: @@ -233,31 +256,31 @@ To work around this, do one of the following: * Use `10.0.2.2:8080` as the URL. * Run `adb reverse tcp:8080 tcp:8080` and `adb reverse tcp:8083 tcp:8083` from your console. -## 5 Google Maps Configuration +## 4 Google Maps Configuration -### 5.1 iOS +### 4.1 iOS To configure Google Maps functionality, do the following: * To run a iOS FastLane script containing an API key, please define the variable `GOOGLE_MAPS_API_KEY` before beta lane. If you run it manually in XCode, change the API key in `ApiKeys.xcconfig` file. -### 5.2 Android +### 4.2 Android To configure Google Maps functionality, do the following: * To run Android a FastLane script containing an API key, please define the variables `FIREBASE_API_KEY_1` and `FIREBASE_API_KEY_2` before internal lane. This values can be find in the Firebase file when downloading it from the Firebase website. If you run it manually in Android Studio, change the API keys in the `google-services.json` file. -## 6 FAQ +## 5 FAQ -### 6.1 Android Syncing Breaks +### 5.1. Android Syncing Breaks There are a number of reasons why syncing would fail. Please consult the sections below depending on your use case. -#### 6.1.1 Dependency Missing or was Falsely Imported +#### 5.1.1 Dependency Missing or was Falsely Imported We are trying to keep master working, but something might go wrong from time to time. If a dependency is missing or was falsely important due to developer error, we recommend consulting the build logs. The build logs should point exactly to the offending files, allowing you to fix the issue and resync. -#### 6.1.2 Android Studio Fails to Load NPM modules +#### 5.1.2 Android Studio Fails to Load NPM modules If the project explorer does not list any of the NPM modules imported, check for both of the following situations: @@ -278,7 +301,7 @@ As a last resort, delete the following folders relatively to the project's direc 3. Delete both `build` folders in `/app` and `/mendixNative`. 4. Restart android studio and open the project. -#### 6.1.3 Windows Long Path Limitation +#### 5.1.3 Windows Long Path Limitation When building on windows, the NDK build step generates extremely long paths that might break the build. A possible indication of this problem is errors in the form of "can't find directory or file in `c:\`". @@ -290,7 +313,7 @@ To fix this issue, do the following: From now on the output of the builds is being generated in the build directory provided. So if you are looking for the generated APKs, then look there. -#### 6.1.4 Android NDK Cannot be Found +#### 5.1.4 Android NDK Cannot be Found For errors that point to the React Native Gradle files or native compilation, React Native probably cannot find your NDK installation. The easiest way to fix it is to add the path to the NDK to your `PATH`: @@ -302,7 +325,7 @@ export ANDROID_NDK="~/Library/Android/sdk/ndk/*add-your-ndk-version-number*" export PATH=$PATH:$ANDROID_NDK ``` -## 7 Contribution Guide +## 6 Contribution Guide For deeper information on the best contributions, see the following: @@ -316,13 +339,13 @@ For example - We upgraded the embedded database HSQLDB to version 2.6.1. ``` -## 8 Sample Apps +## 7 Sample Apps -### 8.1 Updating Sample App Bundles and Assets +### 7.1 Updating Sample App Bundles and Assets To update sample app bundles and assets, see the sections below for instructions based on platform. -#### 8.1.1 Android +#### 7.1.1 Android In `android > app > src > main > assets` (from here on referred to as (A)) there is a `sampleapps.zip` file. @@ -342,7 +365,7 @@ to update the Android developer app bundle and assets: See [Generating iOS & Android Native Bundles and Assets](#generate-native-bundles) for details on generating a project's bundles and assets. -#### 8.1.2 iOS +#### 7.1.2 iOS In `ios > DeveloperApp > SampleApps > Bundles` there are folders that represent each sample app. @@ -356,9 +379,9 @@ The folder name can be arbitrary. The `config.json` file describes each sample a See [Generating iOS & Android Native Bundles and Assets](#generate-native-bundles) for details on generating a project's bundles and assets. -## 9 Generating iOS & Android Native Bundles and Assets {#generate-native-bundles} +## 8 Generating iOS & Android Native Bundles and Assets {#generate-native-bundles} -### 9.1 Using Native Builder UI (also creates native apps to use for testing) +### 8.1 Using Native Builder UI (also creates native apps to use for testing) If using Native Builder UI (which also creates native apps to use for testing), do the following to generate iOS & Android native bundles and assets: @@ -378,7 +401,7 @@ If using Native Builder UI (which also creates native apps to use for testing), The native app's source code will be in the disk location selected in step 3. In your Mendix Project directory, in **deployment** > **native** > **bundle** there will be both the Android and iOS bundles and assets. -### 9.2 Using Studio Pro in Dev Mode +### 8.2 Using Studio Pro in Dev Mode To generate native bundles and assets while using Studio Pro in developer mode, do the following: @@ -388,22 +411,22 @@ To generate native bundles and assets while using Studio Pro in developer mode, In your Mendix Project directory, in **deployment** > **native** > **bundle** you will find both the Android and iOS bundles and assets. -### 9.3 Bundle and Asset Location +### 8.3 Bundle and Asset Location In your Mendix project folder you will find the files listed below depending on your platform. -#### 9.3.1 Android Bundle {#android-bundle} +#### 8.3.1 Android Bundle {#android-bundle} In **deployment** > **native** > **bundle** > **android** > **assets** > **index.android.bundle** -#### 9.3.2 Android Assets {#android-assets} +#### 8.3.2 Android Assets {#android-assets} In **deployment** > **native** > **bundle** > **android** > **res** > **(all folders and files)** -#### 9.3.3 iOS Bundle {#ios-bundle} +#### 8.3.3 iOS Bundle {#ios-bundle} In **deployment** > **native** > **bundle** > **iOS** > **index.ios.bundle** -#### 9.3.4 iOS Assets {#ios-assets} +#### 8.3.4 iOS Assets {#ios-assets} In **deployment** > **native** > **bundle** > **iOS** > **assets** > **(all folders and files)** diff --git a/content/en/docs/refguide/modeling/application-logic/expressions/enumerations-in-expressions.md b/content/en/docs/refguide/modeling/application-logic/expressions/enumerations-in-expressions.md index 70140dc1281..343a0c65de3 100644 --- a/content/en/docs/refguide/modeling/application-logic/expressions/enumerations-in-expressions.md +++ b/content/en/docs/refguide/modeling/application-logic/expressions/enumerations-in-expressions.md @@ -25,7 +25,7 @@ else OrderProcessing.Status.started ``` -You can also use conditional statements to check whether two enumeration values are the same: +You can also use conditional statements to check whether two emuneration values are the same: ```java if $Order/Status = OrderProcessing.Status.completed then diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/_index.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/_index.md index 8209e86ef28..8f043eadf02 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/_index.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/_index.md @@ -29,7 +29,7 @@ Recommenders: Generators: -* **Translation Generator** (currently an [experimental feature](/releasenotes/beta-features/) introduced in Studio Pro 10.12.0) - an AI-powered translation tool for **Batch translate** in Mendix Studio Pro. It helps you to translate your model to different languages for which you may not have a translation. It gives contextualized translations for the languages that you have selected, using parameters in the way that works specifically for the selected languages. For more information, see [Translation Generator](/refguide/translation-generator/). +* **Translation Generator** (currently an [experimental feature](/releasenotes/beta-features/) introduced in Studio Pro 10.12.0) - an AI-powered translation tool for **Batch translate** in Mendix Studio Pro. It helps you to translate your model to different languages for which you may not have a translation. It gives contextualized translations for the languages that you have seleted, using parameters in the way that works specifically for the selcted languages. For more information, see [Translation Generator](/refguide/translation-generator/). ## 3 Maia in Mendix Portal diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/translation-generator.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/translation-generator.md index e20e349fe36..ba9426fee7e 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/translation-generator.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/translation-generator.md @@ -11,7 +11,7 @@ description: "Describes the features in Translation Generator." Translation Generator is currently an experimental feature introduced in Studio Pro 10.12.0. For more information on experimental features, see [Beta and Experimental Releases](/releasenotes/beta-features/). {{% /alert %}} -Translation Generator is an AI-powered translation tool that you can use for [Batch translate](/refguide/batch-translate/). It helps you to translate your model to different languages for which you may not have a translation. It gives translations for the languages that you have selected, using parameters in the way that works specifically for the selected languages. + Maia Translation Generator is an AI-powered translation tool that you can use for [Batch translate](/refguide/batch-translate/). It helps you to translate your model to different languages for which you may not have a translation. It gives translations for the languages that you have selected, using parameters in the way that works specifically for the selected languages. ## 2 Modeling Using Translation Generator diff --git a/content/en/docs/refguide/modeling/menus/app-menu/_index.md b/content/en/docs/refguide/modeling/menus/app-menu/_index.md index d118eee6a3e..fbdc2615368 100644 --- a/content/en/docs/refguide/modeling/menus/app-menu/_index.md +++ b/content/en/docs/refguide/modeling/menus/app-menu/_index.md @@ -86,4 +86,4 @@ For more information on using this option, see [Deploy to the Cloud](/refguide/d ## 9 Read More * [Studio Pro Overview](/refguide/studio-pro-overview/) -* [Deployment](/deployment/) +* [Deployment](/developerportal/deploy/) diff --git a/content/en/docs/refguide/modeling/menus/file-menu/new-app.md b/content/en/docs/refguide/modeling/menus/file-menu/new-app.md index f0718df36df..a61c217b05c 100644 --- a/content/en/docs/refguide/modeling/menus/file-menu/new-app.md +++ b/content/en/docs/refguide/modeling/menus/file-menu/new-app.md @@ -38,7 +38,7 @@ The name of your new app. This name is used as the name of the app directory and ### 2.2 Enable Online Services -The Mendix Platform offers online services such as [version control](/refguide/version-control/) and [cloud deployment](/deployment/). When enabled, this will create an app in [Apps](https://sprintr.home.mendix.com/) in the Mendix Portal and a corresponding version control repository. +The Mendix Platform offers online services such as [version control](/refguide/version-control/) and [cloud deployment](/developerportal/deploy/). When enabled, this will create an app in [Apps](https://sprintr.home.mendix.com/) in the Mendix Portal and a corresponding version control repository. If you choose *No*, you will create an app that is only stored on your local disk. At a later point you can still decide to upload this local app to a version control server and enjoy the benefits of version control. diff --git a/content/en/docs/refguide/modeling/menus/view-menu/stories-pane.md b/content/en/docs/refguide/modeling/menus/view-menu/stories-pane.md index ffa1c47e5a6..06b90c8d54b 100644 --- a/content/en/docs/refguide/modeling/menus/view-menu/stories-pane.md +++ b/content/en/docs/refguide/modeling/menus/view-menu/stories-pane.md @@ -59,7 +59,7 @@ When you view the details of a story, the **Story Details** pop-up window opens ### 2.5 Changing the Status of a Story or a Task {#changing-status} -If you use Studio Pro version 10.10 or higher, you can change the status of a story on the **Stories** pane. To do so, just select a new status in the **Status** column. The list of statuses to choose from can be managed via [Epics](/developerportal/project-management/epics/) in the Mendix Portal or the connected [Jira board](/developerportal/project-management/jira-connector/). +To change the status of a story, select the new status in the **Status** column. The list of statuses to choose from can be managed via [Epics](/developerportal/project-management/epics/) in the Mendix Portal or the connected [Jira board](/developerportal/project-management/jira-connector/). To change the status of a task, select or clear the checkbox in the **Status** column: diff --git a/content/en/docs/refguide/runtime/data-storage/oracle.md b/content/en/docs/refguide/runtime/data-storage/oracle.md index 81fec14a111..295eaeb97cd 100644 --- a/content/en/docs/refguide/runtime/data-storage/oracle.md +++ b/content/en/docs/refguide/runtime/data-storage/oracle.md @@ -6,7 +6,7 @@ weight: 60 ## 1 Introduction -There are some minor differences in how Mendix behaves when using an Oracle database in comparison to using a PostgreSQL database. This document describes these differences. +There are some minor differences in how Mendix behaves when using an Oracle database in comparision to using a PostgreSQL database. This document describes these differences. ## 2 Setting Up a User for Mendix diff --git a/content/en/docs/refguide/runtime/date-and-time-handling/datetime-handling-faq.md b/content/en/docs/refguide/runtime/date-and-time-handling/datetime-handling-faq.md index e2886dc7d5a..acecbe1d829 100644 --- a/content/en/docs/refguide/runtime/date-and-time-handling/datetime-handling-faq.md +++ b/content/en/docs/refguide/runtime/date-and-time-handling/datetime-handling-faq.md @@ -65,7 +65,7 @@ It depends on when you run this statement. Usually it will return true because t ## 14 If I Am Comparing Something with a `[%CurrentDateTime%]` Token in a DataGrid, Which Time Should It Use as a Constraint for a Localized and for a Non-Localized Date? -So if I do an XPath with the following constraint `[LocalDateAttr > [%CurrentDateTime%]` or the following constraint `[NotLocalDateAttr > [%CurrentDateTime%]`, what should I expect in the result when it is 12:10pm in Boston ET? Should it show all records with a date after 12:10 or all records after 17:10? +So if I do an XPath with the following constraint `[LocalDateAttr > [%CurrentDateTime%]` or the following constraint `[NotLocalDateAttr > [%CurrentDateTime%]` what should I expect in the result when it is 12:10pm in boston ET? Should it show all records with a date after 12:10 or all records after 17:10? Whether something is a local date or not is irrelevant in this case. Note that there is no UTC variant of the `[%CurrentDateTime%]` token because this wouldn't make any sense, a moment in time is the same everywhere in the world, even if it may be displayed differently depending on the place. To answer the question, this is yes to both. It will show all records after 12:10 EST (for the localized dates) which is the same as 17:10 UTC (which is how your non-localized dates would show), but these times are the same. diff --git a/content/en/docs/refguide/runtime/logging.md b/content/en/docs/refguide/runtime/logging.md index c1eb9eeace5..8792cf173dd 100644 --- a/content/en/docs/refguide/runtime/logging.md +++ b/content/en/docs/refguide/runtime/logging.md @@ -72,7 +72,7 @@ This list is currently incomplete and is being updated. | Integration API | Logs messages related to the documentation of integration APIs. | | JSON | JSON messages from the Mendix Client to the Runtime Server. See [JSON](#json), below, for more information | | JSON Export | Logs messages related to export mappings to JSON. | -| JSON Import | Logs messages related to import mappings from JSON. | +| JSON Import | Logs messages related to improt mappings from JSON. | | Jetty | Logs messages from the internal Jetty webserver that handles HTTP requests between the runtime and the outside world. | | LocalFileSystemStore | Logs messages related to file handling if you are using local file system as your file store. | | Logging | Logs messages related to the logging framework used by Mendix. | diff --git a/content/en/docs/refguide/runtime/runtime-deployment.md b/content/en/docs/refguide/runtime/runtime-deployment.md index f00f9528c6e..0833d7b687a 100644 --- a/content/en/docs/refguide/runtime/runtime-deployment.md +++ b/content/en/docs/refguide/runtime/runtime-deployment.md @@ -7,7 +7,7 @@ weight: 30 ## 1 Introduction -To convert your Mendix model into an app running in the cloud, it needs to be deployed. This document describes the concepts behind the deployment of your app, and the processes it goes through to begin running in the cloud. For technical details on how to deploy your app, see [Deployment](/deployment/). +To convert your Mendix model into an app running in the cloud, it needs to be deployed. This document describes the concepts behind the deployment of your app, and the processes it goes through to begin running in the cloud. For technical details on how to deploy your app, see [Deployment](/developerportal/deploy/). This description of deployment is based on an app running in the cloud. You can also run Mendix locally for testing, but this is conceptually the same. diff --git a/content/en/docs/refguide8/_index.md b/content/en/docs/refguide8/_index.md index 1dd51d9c2a3..1315c20b12b 100644 --- a/content/en/docs/refguide8/_index.md +++ b/content/en/docs/refguide8/_index.md @@ -42,7 +42,7 @@ When it comes to testing your application, you first need to decide what you are Studio Pro allows you to run and view your app locally or in the default environment. -For more information on options for deploying your app, see [Deployment](/deployment/). +For more information on options for deploying your app see [Deployment](/developerportal/deploy/). ## 3 Version Control diff --git a/content/en/docs/refguide8/modeling/menus/file-menu/new-project.md b/content/en/docs/refguide8/modeling/menus/file-menu/new-project.md index 123a0c39af1..353ec87100a 100644 --- a/content/en/docs/refguide8/modeling/menus/file-menu/new-project.md +++ b/content/en/docs/refguide8/modeling/menus/file-menu/new-project.md @@ -37,7 +37,7 @@ The name of your new app. This name is used as the name of the project directory ### 2.2 Enable Online Services -The Mendix Platform offers online services such as [version control](/refguide8/version-control/) and [cloud deployment](/deployment/). When enabled, this will create a project in the Mendix Portal and a corresponding version control repository. +The Mendix Platform offers online services such as [version control](/refguide8/version-control/) and [cloud deployment](/developerportal/deploy/). When enabled, this will create a project in the Mendix Portal and a corresponding version control repository. If you choose *No*, you will create an app that is only stored on your local disk. At a later point you can still decide to upload this local app to a version control server and enjoy the benefits of version control. diff --git a/content/en/docs/refguide8/modeling/menus/project-menu/_index.md b/content/en/docs/refguide8/modeling/menus/project-menu/_index.md index 0f0bed1049e..a9074841f41 100644 --- a/content/en/docs/refguide8/modeling/menus/project-menu/_index.md +++ b/content/en/docs/refguide8/modeling/menus/project-menu/_index.md @@ -86,4 +86,4 @@ For more information on using this option, see [Deploy to the Cloud](/refguide8/ ## 9 Read More * [Studio Pro Overview](/refguide8/studio-pro-overview/) -* [Deployment](/deployment/) +* [Deployment](/developerportal/deploy/) diff --git a/content/en/docs/refguide8/modeling/studio-pro-overview.md b/content/en/docs/refguide8/modeling/studio-pro-overview.md index da5e992b2ec..296cb25c0f2 100644 --- a/content/en/docs/refguide8/modeling/studio-pro-overview.md +++ b/content/en/docs/refguide8/modeling/studio-pro-overview.md @@ -42,7 +42,7 @@ For more information on menus, see [Menus](/refguide8/menus/). You can deploy your app by clicking the **Run** or **Run locally** buttons. To view your deployed app, click the **View** button. -For more information on deployment in Mendix, see [Deployment](/deployment/). +For more information on deployment in Mendix, see [Deployment](/developerportal/deploy/). For more information on deploying your app and versioning it, see the [Versioning a Project Deployed to the Cloud](/refguide8/using-version-control-in-studio-pro/#versioning-project) section in *Using Version Control in Studio Pro*. diff --git a/content/en/docs/refguide8/runtime/runtime-deployment.md b/content/en/docs/refguide8/runtime/runtime-deployment.md index 0c7639ee3c4..0f4bbdd5086 100644 --- a/content/en/docs/refguide8/runtime/runtime-deployment.md +++ b/content/en/docs/refguide8/runtime/runtime-deployment.md @@ -7,7 +7,7 @@ weight: 30 ## 1 Introduction -To convert your Mendix model into an app running in the cloud, it needs to be deployed. This document describes the concepts behind the deployment of your project, and the processes it goes through to begin running in the cloud. For technical details on how to deploy your app, see [Deployment](/deployment/). +To convert your Mendix model into an app running in the cloud, it needs to be deployed. This document describes the concepts behind the deployment of your project, and the processes it goes through to begin running in the cloud. For technical details on how to deploy your app, see [Deployment](/developerportal/deploy/). This description of deployment is based on an app running in the cloud. You can also run Mendix locally for testing, but this is conceptually the same. diff --git a/content/en/docs/refguide9/_index.md b/content/en/docs/refguide9/_index.md index da5b0fe06f9..aae15c57cf3 100644 --- a/content/en/docs/refguide9/_index.md +++ b/content/en/docs/refguide9/_index.md @@ -40,7 +40,7 @@ When it comes to testing your application, you first need to decide what you are Studio Pro allows you to run and view your app locally or in the default environment. -For more information on options for deploying your app, see [Deployment](/deployment/). +For more information on options for deploying your app see [Deployment](/developerportal/deploy/). ## 3 Version Control diff --git a/content/en/docs/refguide9/modeling/menus/app-menu/_index.md b/content/en/docs/refguide9/modeling/menus/app-menu/_index.md index 91c3b750b89..0589e431375 100644 --- a/content/en/docs/refguide9/modeling/menus/app-menu/_index.md +++ b/content/en/docs/refguide9/modeling/menus/app-menu/_index.md @@ -84,4 +84,4 @@ For more information on using this option, see [Deploy to the Cloud](/refguide9/ ## 9 Read More * [Studio Pro Overview](/refguide9/studio-pro-overview/) -* [Deployment](/deployment/) +* [Deployment](/developerportal/deploy/) diff --git a/content/en/docs/refguide9/modeling/menus/file-menu/new-app.md b/content/en/docs/refguide9/modeling/menus/file-menu/new-app.md index 1560d1843d6..93c8b2782a7 100644 --- a/content/en/docs/refguide9/modeling/menus/file-menu/new-app.md +++ b/content/en/docs/refguide9/modeling/menus/file-menu/new-app.md @@ -38,7 +38,7 @@ The name of your new app. This name is used as the name of the app directory and ### 2.2 Enable Online Services -The Mendix Platform offers online services such as [version control](/refguide9/version-control/) and [cloud deployment](/deployment/). When enabled, this will create an app in [Apps](https://sprintr.home.mendix.com/) and a corresponding version control repository. +The Mendix Platform offers online services such as [version control](/refguide9/version-control/) and [cloud deployment](/developerportal/deploy/). When enabled, this will create an app in [Apps](https://sprintr.home.mendix.com/) and a corresponding version control repository. If you choose *No*, you will create an app that is only stored on your local disk. At a later point you can still decide to upload this local app to a version control server and enjoy the benefits of version control. diff --git a/content/en/docs/refguide9/modeling/resources/scheduled-events/scheduled-events-task-queue.md b/content/en/docs/refguide9/modeling/resources/scheduled-events/scheduled-events-task-queue.md index 4b3f390cd90..b1e1f0f6d6e 100644 --- a/content/en/docs/refguide9/modeling/resources/scheduled-events/scheduled-events-task-queue.md +++ b/content/en/docs/refguide9/modeling/resources/scheduled-events/scheduled-events-task-queue.md @@ -176,7 +176,3 @@ This limit cannot be overridden. ### 5.3 Unsupported Intervals Hour- and minute-based intervals can only be integer divisors of 24 or 60, respectively. For example you cannot schedule an event to run every seven minutes as this does not divide precisely into sixty minutes. If it is absolutely critical that an unsupported interval is used, you should schedule the event with interval value of one (every hour or every minute) and decide within the microflow whether it should continue executing at that particular time. - -### 5.4 One Session for All Scheduled Events - -Each runtime node has one specific session in memory which is used for all scheduled events. Changes to this session are visible for all scheduled events on that node. Things like changing the time zone via a Java action in one scheduled event can lead to unexpected behavior in other scheduled events. You are therefore strongly discouraged from changing the session object for scheduled events. diff --git a/content/en/docs/refguide9/modeling/studio-pro-overview/_index.md b/content/en/docs/refguide9/modeling/studio-pro-overview/_index.md index 0d665a779dc..4e3c7f3041e 100644 --- a/content/en/docs/refguide9/modeling/studio-pro-overview/_index.md +++ b/content/en/docs/refguide9/modeling/studio-pro-overview/_index.md @@ -44,7 +44,7 @@ You can deploy your app by clicking **Publish** or **Run Locally** ({{% icon nam {{< figure src="/attachments/refguide9/modeling/studio-pro-overview/view-and-publish.png" alt="View App, Publish, and Run Locally buttons" class="no-border" >}} -For more information on deployment in Mendix, see [Deployment](/deployment/). +For more information on deployment in Mendix, see [Deployment](/developerportal/deploy/). For more information on deploying your app and versioning it, see the [Versioning an App Deployed to the Cloud](/refguide9/using-version-control-in-studio-pro/#versioning-app) section in *Using Version Control in Studio Pro*. diff --git a/content/en/docs/refguide9/runtime/runtime-deployment.md b/content/en/docs/refguide9/runtime/runtime-deployment.md index 7f0a3ad5755..0287ac676ef 100644 --- a/content/en/docs/refguide9/runtime/runtime-deployment.md +++ b/content/en/docs/refguide9/runtime/runtime-deployment.md @@ -7,7 +7,7 @@ weight: 30 ## 1 Introduction -To convert your Mendix model into an app running in the cloud, it needs to be deployed. This document describes the concepts behind the deployment of your app, and the processes it goes through to begin running in the cloud. For technical details on how to deploy your app, see [Deployment](/deployment/). +To convert your Mendix model into an app running in the cloud, it needs to be deployed. This document describes the concepts behind the deployment of your app, and the processes it goes through to begin running in the cloud. For technical details on how to deploy your app, see [Deployment](/developerportal/deploy/). This description of deployment is based on an app running in the cloud. You can also run Mendix locally for testing, but this is conceptually the same. diff --git a/content/en/docs/releasenotes/marketplace/_index.md b/content/en/docs/releasenotes/marketplace/_index.md index af8fdf27f05..58f23e3a199 100644 --- a/content/en/docs/releasenotes/marketplace/_index.md +++ b/content/en/docs/releasenotes/marketplace/_index.md @@ -14,8 +14,13 @@ These release notes cover changes made to the [Mendix Marketplace](/appstore/). ### June 27, 2024 +### New Features + +* We released of a new label specifically for React Ready widgets in the Marketplace. This enhancement is designed to help developers and users easily identify and access a wide range of widgets that are optimized for React Client applications. You can find a **React-Client** label next to a version of the product when navigating to the **Release** tab of a product details page. For more information, see the [Labels](/appstore/component-details/#labels) section in *Component Details Page*. + #### Improvements +* We made significant improvements to the [Studio Pro download](https://marketplace.mendix.com/link/studiopro) page. The updated interface now provides a more intuitive and user-friendly experience, making it easier to find and download the latest or previous versions of Studio Pro. Each version of Studio Pro now has its own dedicated page, containing important links such as release notes, release blogs, and all relevant installers. * We improved the navigation menus of the [Marketplace home page](/appstore/overview/) to enhance user experience. ### March 7, 2024 diff --git a/content/en/docs/releasenotes/mobile/hybrid-app.md b/content/en/docs/releasenotes/mobile/hybrid-app.md index 94a3aa3bc2e..56fa7068e25 100644 --- a/content/en/docs/releasenotes/mobile/hybrid-app.md +++ b/content/en/docs/releasenotes/mobile/hybrid-app.md @@ -80,7 +80,7 @@ With this release we updated all PhoneGap dependencies to the latest supported v **Release date: January 3, 2020** * We fixed an issue with race conditions in asynchronous hooks. -* We introduced a new **onBeforeSynchronization** hook. +* We introduced a new **onBeforeSynchonization** hook. ## 2019 diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-8-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-8-rn.md index 0f9d8451cb5..3ccda5b9722 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-8-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-8-rn.md @@ -5,15 +5,7 @@ weight: 8 description: "Native Template 8 release notes." --- -## 8.2.5 {#814} - -**Release date: July 5, 2024** - -### Fixes - -* We updated the `@mendix/native` dependency to fix an encryption issue. - -## 8.2.3 {#812} +## 8.2.3 {#811} **Release date: June 7, 2024** @@ -77,15 +69,7 @@ description: "Native Template 8 release notes." * We upgraded security-crypto dependency on Android to version 1.1.0-alpha06. * We upgraded `@mendix/react-native-sqlite-storage` to version 7.1.0 and `@mendix/native` to the latest compatible version. -## 8.0.13 {#813} - -**Release date: July 4, 2024** - -### Fixes - -* We updated the `@mendix/native` dependency to fix an encryption issue. - -## 8.0.10 {#809} +* ## 8.0.10 {#809} **Release date: June 24, 2024** diff --git a/content/en/docs/releasenotes/studio-pro/10/10.12.md b/content/en/docs/releasenotes/studio-pro/10/10.12.md index 350f4936fcd..5e41bcafa03 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.12.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.12.md @@ -156,7 +156,7 @@ Moreover, your model is analyzed by Studio Pro to ensure that only entities with * We fixed an issue where retrieving more than 1000 objects together with a specialization of an associated entity returned incomplete results. (Ticket 211813) * We added a check so that reimported modules only keep database IDs for attributes when a generalization of the entity remains in place. (Ticket 212565) * We fixed an issue where long text in the design properties definition file caused the styling pane to stretch. (Ticket 214953) -* We fixed an issue which occurred when starting an app containing a consumed OData service that retrieves headers from a microflow. This logged an error that the headers microflow could not be found. (Ticket 214979) +* We fixed an issue which occured when starting an app containing a consumed OData service that retrieves headers from a microflow. This logged an error that the headers microflow could not be found. (Ticket 214979) * We fixed an issue in the Workflow Engine that caused the Mendix Runtime Server to run out of memory after deploying a new version of a workflow that had many decisions in it. (Ticket 215232) * We fixed an issue with searching in protected modules. (Ticket 216100) * We fixed an issue that caused design properties to sometimes apply a change to the wrong widget. (Ticket 216125) diff --git a/content/en/docs/releasenotes/studio-pro/windows-service.md b/content/en/docs/releasenotes/studio-pro/windows-service.md index ed639319ad4..5aa52bc1c58 100644 --- a/content/en/docs/releasenotes/studio-pro/windows-service.md +++ b/content/en/docs/releasenotes/studio-pro/windows-service.md @@ -322,7 +322,7 @@ Now each app has its own license, even if it runs under the same user account as * Added settings 'Uploaded files path' and 'Temporary files path' to the Common Configuration panel. * Now the system log file m2ee_log.txt is closed immediately when the process cannot start. * Connecting to an already running server will be done asynchronously while starting the Service Console, so the form will be shown more quickly. -* Now all configured paths will be validated when the server or the service starts. +* Now all configurated paths will be validated when the server or the service starts. * Windows service exceptions will now be shown in the Service Console (so you don't have to go to Administrative Tools -> Event Viewer anymore). * Default folder of project path changed to 'Project' (was 'Application'). * Default folders will be created if they do not exist when they are needed. diff --git a/content/en/docs/support/_index.md b/content/en/docs/support/_index.md index 6a1523e1c94..a1e3e98b9a4 100644 --- a/content/en/docs/support/_index.md +++ b/content/en/docs/support/_index.md @@ -6,7 +6,7 @@ weight: 47 no_list: false description_list: true cascade: - - content_type: "Mendix Support" + - content_type: "Mendix Support Guide" - mendix_version: 10 aliases: - /howtogeneral/support/index.html @@ -257,7 +257,8 @@ Mendix Support can analyze these components if your app is running on Mendix Clo ### 10.7 Deployment Pipeline -The deployment pipeline takes care of creating and deploying deployment packages. Read more about deployment options in [Deployment](/deployment/). +The deployment pipeline takes care of creating and deploying deployment packages +Please read all about the Deployment options in [Deployment](/developerportal/deploy/). Mendix Support can analyze this component if your app is running on Mendix Cloud, Mendix Cloud Dedicated, Private Cloud Connected, or SAP BTP through the Mendix Portal. 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 3d78bc6e160..a922c872214 100644 --- a/content/en/docs/support/new-app-node-request-template.md +++ b/content/en/docs/support/new-app-node-request-template.md @@ -63,5 +63,5 @@ When your app is offboarded, only the deployed app is removed. You still retain ## 5 Read More -* [Deployment](/deployment/) +* [Deployment Options](/developerportal/deploy/) * [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/) diff --git a/content/en/docs/support/submit-support-request.md b/content/en/docs/support/submit-support-request.md index bcea0fcfc75..8915a8c03b7 100644 --- a/content/en/docs/support/submit-support-request.md +++ b/content/en/docs/support/submit-support-request.md @@ -70,7 +70,7 @@ To submit a request with Mendix Support, follow these steps: 4. When you select **Request for Information** or **Incident**, you then have to select the **Related Component** for the issue. The correct component will allow Mendix Support to help you more effectively. In some cases, you can also select the **Related Sub-Component** for your issue. Selecting the related sub-component is not required, but it will allow Mendix Support to help you more quickly and accurately. There are two main options for the related component: * **App** – select one of these components when you have issues with designing, developing, building, deploying, or operating one of your own apps built on the Mendix Platform: * **App - Development** – issues/questions regarding developing your app (for example, with your [domain model](/refguide/domain-model/), [widgets](/refguide/data-widgets/), or [logic](/refguide/application-logic/)) - * **App - Deployment** – issues/questions regarding deploying your app (for example, when the app cannot be [deployed](/deployment/) or will not start) + * **App - Deployment** – issues/questions regarding deploying your app (for example, when the app cannot be [deployed](/developerportal/deploy/) or will not start) * **App - Operations** – issues/questions regarding running a deployed app (for example, when the app crashes or shows errors in the [log](/developerportal/operate/logs/)) * **App - Add-on** – issues/questions regarding one of the Mendix add-ons (such as [ATS](/appstore/partner-solutions/ats/), [APD](/appstore/partner-solutions/apd/), or [AQM](/addons/aqm-addon/)) * **App - Security** - issues/questions regarding the security of your Mendix app diff --git a/static/attachments/appstore/overview/my-marketplace/company-content.png b/static/attachments/appstore/overview/company-content.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/company-content.png rename to static/attachments/appstore/overview/company-content.png diff --git a/static/attachments/appstore/overview/my-marketplace/company-subscriptions.png b/static/attachments/appstore/overview/company-subscriptions.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/company-subscriptions.png rename to static/attachments/appstore/overview/company-subscriptions.png diff --git a/static/attachments/appstore/overview/component-details/component-details.png b/static/attachments/appstore/overview/component-details/component-details.png new file mode 100644 index 00000000000..b1474d9a5ae Binary files /dev/null and b/static/attachments/appstore/overview/component-details/component-details.png differ diff --git a/static/attachments/appstore/overview/my-marketplace/group-content-context.png b/static/attachments/appstore/overview/group-content-context.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/group-content-context.png rename to static/attachments/appstore/overview/group-content-context.png diff --git a/static/attachments/appstore/overview/my-marketplace/group-content.png b/static/attachments/appstore/overview/group-content.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/group-content.png rename to static/attachments/appstore/overview/group-content.png diff --git a/static/attachments/appstore/overview/my-marketplace/my-content.png b/static/attachments/appstore/overview/my-content.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/my-content.png rename to static/attachments/appstore/overview/my-content.png diff --git a/static/attachments/appstore/overview/my-marketplace/my-drafts.png b/static/attachments/appstore/overview/my-drafts.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/my-drafts.png rename to static/attachments/appstore/overview/my-drafts.png diff --git a/static/attachments/appstore/overview/my-marketplace/my-subscriptions.jpg b/static/attachments/appstore/overview/my-subscriptions.jpg similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/my-subscriptions.jpg rename to static/attachments/appstore/overview/my-subscriptions.jpg diff --git a/static/attachments/appstore/overview/overview/component-details.png b/static/attachments/appstore/overview/overview/component-details.png deleted file mode 100644 index 5cb26b02239..00000000000 Binary files a/static/attachments/appstore/overview/overview/component-details.png and /dev/null differ diff --git a/static/attachments/appstore/overview/overview/partner.png b/static/attachments/appstore/overview/overview/partner.png deleted file mode 100644 index 7266df0681c..00000000000 Binary files a/static/attachments/appstore/overview/overview/partner.png and /dev/null differ diff --git a/static/attachments/appstore/overview/my-marketplace/saved.png b/static/attachments/appstore/overview/saved.png similarity index 100% rename from static/attachments/appstore/overview/my-marketplace/saved.png rename to static/attachments/appstore/overview/saved.png diff --git a/static/attachments/appstore/overview/use-content/add-widget.png b/static/attachments/appstore/use-content/add-widget.png similarity index 100% rename from static/attachments/appstore/overview/use-content/add-widget.png rename to static/attachments/appstore/use-content/add-widget.png diff --git a/static/attachments/appstore/overview/use-content/component-details.png b/static/attachments/appstore/use-content/component-details.png similarity index 100% rename from static/attachments/appstore/overview/use-content/component-details.png rename to static/attachments/appstore/use-content/component-details.png diff --git a/static/attachments/appstore/overview/use-content/edit-rating.png b/static/attachments/appstore/use-content/edit-rating.png similarity index 100% rename from static/attachments/appstore/overview/use-content/edit-rating.png rename to static/attachments/appstore/use-content/edit-rating.png diff --git a/static/attachments/appstore/overview/use-content/import-module-in-app-explorer.png b/static/attachments/appstore/use-content/import-module-in-app-explorer.png similarity index 100% rename from static/attachments/appstore/overview/use-content/import-module-in-app-explorer.png rename to static/attachments/appstore/use-content/import-module-in-app-explorer.png diff --git a/static/attachments/appstore/overview/use-content/import-module.png b/static/attachments/appstore/use-content/import-module.png similarity index 100% rename from static/attachments/appstore/overview/use-content/import-module.png rename to static/attachments/appstore/use-content/import-module.png diff --git a/static/attachments/appstore/overview/use-content/marketplace.png b/static/attachments/appstore/use-content/marketplace.png similarity index 100% rename from static/attachments/appstore/overview/use-content/marketplace.png rename to static/attachments/appstore/use-content/marketplace.png diff --git a/static/attachments/appstore/overview/use-content/select-attribute.png b/static/attachments/appstore/use-content/select-attribute.png similarity index 100% rename from static/attachments/appstore/overview/use-content/select-attribute.png rename to static/attachments/appstore/use-content/select-attribute.png diff --git a/static/attachments/appstore/overview/use-content/select-widget.png b/static/attachments/appstore/use-content/select-widget.png similarity index 100% rename from static/attachments/appstore/overview/use-content/select-widget.png rename to static/attachments/appstore/use-content/select-widget.png diff --git a/static/attachments/appstore/overview/use-content/toolbar.png b/static/attachments/appstore/use-content/toolbar.png similarity index 100% rename from static/attachments/appstore/overview/use-content/toolbar.png rename to static/attachments/appstore/use-content/toolbar.png diff --git a/static/attachments/appstore/overview/use-content/toolbox-rating.png b/static/attachments/appstore/use-content/toolbox-rating.png similarity index 100% rename from static/attachments/appstore/overview/use-content/toolbox-rating.png rename to static/attachments/appstore/use-content/toolbox-rating.png diff --git a/static/attachments/appstore/overview/use-content/trust-extension.png b/static/attachments/appstore/use-content/trust-extension.png similarity index 100% rename from static/attachments/appstore/overview/use-content/trust-extension.png rename to static/attachments/appstore/use-content/trust-extension.png diff --git a/static/attachments/appstore/overview/use-content/widget-dropped-in-page.png b/static/attachments/appstore/use-content/widget-dropped-in-page.png similarity index 100% rename from static/attachments/appstore/overview/use-content/widget-dropped-in-page.png rename to static/attachments/appstore/use-content/widget-dropped-in-page.png diff --git a/static/attachments/appstore/overview/use-content/widget-errors.png b/static/attachments/appstore/use-content/widget-errors.png similarity index 100% rename from static/attachments/appstore/overview/use-content/widget-errors.png rename to static/attachments/appstore/use-content/widget-errors.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/app-variables.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/app-variables.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/app-variables.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/app-variables.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/cf-log.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/cf-log.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/cf-log.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/cf-log.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/db-configure.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/db-configure.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/db-configure.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/db-configure.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/db-service-plans.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/db-service-plans.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/db-service-plans.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/db-service-plans.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/edit-cf-configure-app.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-configure-app.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/edit-cf-configure-app.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-configure-app.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/edit-cf-settings-details.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings-details.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/edit-cf-settings-details.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings-details.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/edit-cf-settings-window.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings-window.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/edit-cf-settings-window.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings-window.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/edit-cf-settings.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/edit-cf-settings.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/edit-cf-settings.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/marketplaces.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/marketplaces.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/marketplaces.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/marketplaces.png diff --git a/static/attachments/deployment/cloud-foundry-deploy/run-on-cf.png b/static/attachments/developerportal/deploy/cloud-foundry-deploy/run-on-cf.png similarity index 100% rename from static/attachments/deployment/cloud-foundry-deploy/run-on-cf.png rename to static/attachments/developerportal/deploy/cloud-foundry-deploy/run-on-cf.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/AutoRegistrationExplanation.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationExplanation.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/AutoRegistrationExplanation.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationExplanation.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/AutoRegistrationNameAndDescription.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationNameAndDescription.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/AutoRegistrationNameAndDescription.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationNameAndDescription.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/AutoRegistrationSummary.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationSummary.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/AutoRegistrationSummary.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/AutoRegistrationSummary.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/WebKeyLogin.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/WebKeyLogin.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/WebKeyLogin.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/WebKeyLogin.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/app-store-download-project.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-download-project.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/app-store-download-project.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-download-project.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/app-store-download.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-download.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/app-store-download.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-download.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/app-store-icon.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-icon.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/app-store-icon.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-icon.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/app-store-search.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-search.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/app-store-search.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/app-store-search.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/copy-from-documentation.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/copy-from-documentation.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/copy-from-documentation.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/copy-from-documentation.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image10.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image10.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image10.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image10.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image11.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image11.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image11.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image11.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image13.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image13.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image13.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image13.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image14.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image14.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image14.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image14.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image15.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image15.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image15.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image15.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image16.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image16.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image16.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image16.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image17.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image17.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image17.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image17.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image2.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image2.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image2.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image2.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image4.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image4.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image4.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image4.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/image8.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/image8.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/image8.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/image8.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/import-app-package.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/import-app-package.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/import-app-package.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/import-app-package.png diff --git a/static/attachments/deployment/deploying-to-mindsphere/runMendixApp.png b/static/attachments/developerportal/deploy/deploying-to-mindsphere/runMendixApp.png similarity index 100% rename from static/attachments/deployment/deploying-to-mindsphere/runMendixApp.png rename to static/attachments/developerportal/deploy/deploying-to-mindsphere/runMendixApp.png diff --git a/static/attachments/deployment/docker-deploy/build-image.png b/static/attachments/developerportal/deploy/docker-deploy/build-image.png similarity index 100% rename from static/attachments/deployment/docker-deploy/build-image.png rename to static/attachments/developerportal/deploy/docker-deploy/build-image.png diff --git a/static/attachments/deployment/docker-deploy/create-deployment-package.png b/static/attachments/developerportal/deploy/docker-deploy/create-deployment-package.png similarity index 100% rename from static/attachments/deployment/docker-deploy/create-deployment-package.png rename to static/attachments/developerportal/deploy/docker-deploy/create-deployment-package.png diff --git a/static/attachments/deployment/docker-deploy/dockerbuildpack-vs-mxoperator.png b/static/attachments/developerportal/deploy/docker-deploy/dockerbuildpack-vs-mxoperator.png similarity index 100% rename from static/attachments/deployment/docker-deploy/dockerbuildpack-vs-mxoperator.png rename to static/attachments/developerportal/deploy/docker-deploy/dockerbuildpack-vs-mxoperator.png diff --git a/static/attachments/deployment/docker-deploy/run-mendix-on-kubernetes/kubernetes.png b/static/attachments/developerportal/deploy/docker-deploy/run-mendix-on-kubernetes/kubernetes.png similarity index 100% rename from static/attachments/deployment/docker-deploy/run-mendix-on-kubernetes/kubernetes.png rename to static/attachments/developerportal/deploy/docker-deploy/run-mendix-on-kubernetes/kubernetes.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399044.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399044.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399044.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399044.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399045.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399045.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399045.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399045.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399047.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399047.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399047.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399047.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399048.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399048.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399048.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399048.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399049.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399049.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399049.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399049.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399050.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399050.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399050.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399050.png diff --git a/static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399052.png b/static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399052.png similarity index 100% rename from static/attachments/deployment/general/securing-outgoing-connections-from-your-application/19399052.png rename to static/attachments/developerportal/deploy/general/securing-outgoing-connections-from-your-application/19399052.png diff --git a/static/attachments/deployment/general/two-factor-authentication/authentication-sms.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/authentication-sms.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/authentication-sms.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/authentication-sms.png diff --git a/static/attachments/deployment/general/two-factor-authentication/authenticator-app-setup.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/authenticator-app-setup.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/authenticator-app-setup.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/authenticator-app-setup.png diff --git a/static/attachments/deployment/general/two-factor-authentication/authenticator-choice.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/authenticator-choice.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/authenticator-choice.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/authenticator-choice.png diff --git a/static/attachments/deployment/general/two-factor-authentication/deactivate.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/deactivate.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/deactivate.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/deactivate.png diff --git a/static/attachments/deployment/general/two-factor-authentication/enter-authenticator-code.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/enter-authenticator-code.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/enter-authenticator-code.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/enter-authenticator-code.png diff --git a/static/attachments/deployment/general/two-factor-authentication/enter-sms-code.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/enter-sms-code.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/enter-sms-code.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/enter-sms-code.png diff --git a/static/attachments/deployment/general/two-factor-authentication/not-configured.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/not-configured.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/not-configured.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/not-configured.png diff --git a/static/attachments/deployment/general/two-factor-authentication/please-authenticate.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/please-authenticate.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/please-authenticate.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/please-authenticate.png diff --git a/static/attachments/deployment/general/two-factor-authentication/production.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/production.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/production.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/production.png diff --git a/static/attachments/deployment/general/two-factor-authentication/setup-sms.png b/static/attachments/developerportal/deploy/general/two-factor-authentication/setup-sms.png similarity index 100% rename from static/attachments/deployment/general/two-factor-authentication/setup-sms.png rename to static/attachments/developerportal/deploy/general/two-factor-authentication/setup-sms.png diff --git a/static/attachments/deployment/ibm-cloud/add-environment.png b/static/attachments/developerportal/deploy/ibm-cloud/add-environment.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/add-environment.png rename to static/attachments/developerportal/deploy/ibm-cloud/add-environment.png diff --git a/static/attachments/deployment/ibm-cloud/application-started.png b/static/attachments/developerportal/deploy/ibm-cloud/application-started.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/application-started.png rename to static/attachments/developerportal/deploy/ibm-cloud/application-started.png diff --git a/static/attachments/deployment/ibm-cloud/cloud-settings-landing-page.png b/static/attachments/developerportal/deploy/ibm-cloud/cloud-settings-landing-page.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/cloud-settings-landing-page.png rename to static/attachments/developerportal/deploy/ibm-cloud/cloud-settings-landing-page.png diff --git a/static/attachments/deployment/ibm-cloud/create-development.png b/static/attachments/developerportal/deploy/ibm-cloud/create-development.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/create-development.png rename to static/attachments/developerportal/deploy/ibm-cloud/create-development.png diff --git a/static/attachments/deployment/ibm-cloud/custom-database.png b/static/attachments/developerportal/deploy/ibm-cloud/custom-database.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/custom-database.png rename to static/attachments/developerportal/deploy/ibm-cloud/custom-database.png diff --git a/static/attachments/deployment/ibm-cloud/delete-app.png b/static/attachments/developerportal/deploy/ibm-cloud/delete-app.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/delete-app.png rename to static/attachments/developerportal/deploy/ibm-cloud/delete-app.png diff --git a/static/attachments/deployment/ibm-cloud/delete-environment.png b/static/attachments/developerportal/deploy/ibm-cloud/delete-environment.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/delete-environment.png rename to static/attachments/developerportal/deploy/ibm-cloud/delete-environment.png diff --git a/static/attachments/deployment/ibm-cloud/environment-details.png b/static/attachments/developerportal/deploy/ibm-cloud/environment-details.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/environment-details.png rename to static/attachments/developerportal/deploy/ibm-cloud/environment-details.png diff --git a/static/attachments/deployment/ibm-cloud/environments-page.png b/static/attachments/developerportal/deploy/ibm-cloud/environments-page.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/environments-page.png rename to static/attachments/developerportal/deploy/ibm-cloud/environments-page.png diff --git a/static/attachments/deployment/ibm-cloud/error-desktop-modeler.png b/static/attachments/developerportal/deploy/ibm-cloud/error-desktop-modeler.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/error-desktop-modeler.png rename to static/attachments/developerportal/deploy/ibm-cloud/error-desktop-modeler.png diff --git a/static/attachments/deployment/ibm-cloud/error-not-bound.png b/static/attachments/developerportal/deploy/ibm-cloud/error-not-bound.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/error-not-bound.png rename to static/attachments/developerportal/deploy/ibm-cloud/error-not-bound.png diff --git a/static/attachments/deployment/ibm-cloud/failed-description.png b/static/attachments/developerportal/deploy/ibm-cloud/failed-description.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/failed-description.png rename to static/attachments/developerportal/deploy/ibm-cloud/failed-description.png diff --git a/static/attachments/deployment/ibm-cloud/failed-details.png b/static/attachments/developerportal/deploy/ibm-cloud/failed-details.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/failed-details.png rename to static/attachments/developerportal/deploy/ibm-cloud/failed-details.png diff --git a/static/attachments/deployment/ibm-cloud/failed-environment.png b/static/attachments/developerportal/deploy/ibm-cloud/failed-environment.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/failed-environment.png rename to static/attachments/developerportal/deploy/ibm-cloud/failed-environment.png diff --git a/static/attachments/deployment/ibm-cloud/failed-more-details.png b/static/attachments/developerportal/deploy/ibm-cloud/failed-more-details.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/failed-more-details.png rename to static/attachments/developerportal/deploy/ibm-cloud/failed-more-details.png diff --git a/static/attachments/deployment/ibm-cloud/service-bind-error.png b/static/attachments/developerportal/deploy/ibm-cloud/service-bind-error.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/service-bind-error.png rename to static/attachments/developerportal/deploy/ibm-cloud/service-bind-error.png diff --git a/static/attachments/deployment/ibm-cloud/service-connect.png b/static/attachments/developerportal/deploy/ibm-cloud/service-connect.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/service-connect.png rename to static/attachments/developerportal/deploy/ibm-cloud/service-connect.png diff --git a/static/attachments/deployment/ibm-cloud/service-tab.png b/static/attachments/developerportal/deploy/ibm-cloud/service-tab.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/service-tab.png rename to static/attachments/developerportal/deploy/ibm-cloud/service-tab.png diff --git a/static/attachments/deployment/ibm-cloud/service-unbind-warning.png b/static/attachments/developerportal/deploy/ibm-cloud/service-unbind-warning.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/service-unbind-warning.png rename to static/attachments/developerportal/deploy/ibm-cloud/service-unbind-warning.png diff --git a/static/attachments/deployment/ibm-cloud/service-unbind.png b/static/attachments/developerportal/deploy/ibm-cloud/service-unbind.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/service-unbind.png rename to static/attachments/developerportal/deploy/ibm-cloud/service-unbind.png diff --git a/static/attachments/deployment/ibm-cloud/start-application.png b/static/attachments/developerportal/deploy/ibm-cloud/start-application.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/start-application.png rename to static/attachments/developerportal/deploy/ibm-cloud/start-application.png diff --git a/static/attachments/deployment/ibm-cloud/transport-constants.png b/static/attachments/developerportal/deploy/ibm-cloud/transport-constants.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/transport-constants.png rename to static/attachments/developerportal/deploy/ibm-cloud/transport-constants.png diff --git a/static/attachments/deployment/ibm-cloud/transport-deploy.png b/static/attachments/developerportal/deploy/ibm-cloud/transport-deploy.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/transport-deploy.png rename to static/attachments/developerportal/deploy/ibm-cloud/transport-deploy.png diff --git a/static/attachments/deployment/ibm-cloud/transport-environments.png b/static/attachments/developerportal/deploy/ibm-cloud/transport-environments.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/transport-environments.png rename to static/attachments/developerportal/deploy/ibm-cloud/transport-environments.png diff --git a/static/attachments/deployment/ibm-cloud/transport-events.png b/static/attachments/developerportal/deploy/ibm-cloud/transport-events.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/transport-events.png rename to static/attachments/developerportal/deploy/ibm-cloud/transport-events.png diff --git a/static/attachments/deployment/ibm-cloud/transport-from-to.png b/static/attachments/developerportal/deploy/ibm-cloud/transport-from-to.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/transport-from-to.png rename to static/attachments/developerportal/deploy/ibm-cloud/transport-from-to.png diff --git a/static/attachments/deployment/ibm-cloud/transport-services.png b/static/attachments/developerportal/deploy/ibm-cloud/transport-services.png similarity index 100% rename from static/attachments/deployment/ibm-cloud/transport-services.png rename to static/attachments/developerportal/deploy/ibm-cloud/transport-services.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/access-restriction-profiles.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/access-restriction-profiles.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/access-restriction-profiles.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/access-restriction-profiles.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/app-restriction.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/app-restriction.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/app-restriction.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/app-restriction.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/ca-profile.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/ca-profile.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/ca-profile.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/ca-profile.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/environment-restriction-2.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/environment-restriction-2.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/environment-restriction-2.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/environment-restriction-2.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/environment-restriction.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/environment-restriction.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/environment-restriction.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/environment-restriction.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/ip-range.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/ip-range.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/ip-range.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/ip-range.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/scenario1.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/scenario1.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/scenario1.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/scenario1.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/access-restrictions/v4-access-restriction-profile.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/v4-access-restriction-profile.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/access-restrictions/v4-access-restriction-profile.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/access-restrictions/v4-access-restriction-profile.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/appresumed.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/appresumed.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/appresumed.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/appresumed.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/backup-controls.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/backup-controls.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/backup-controls.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/backup-controls.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/backup-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/backup-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/backup-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/backup-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backupoptions.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/create-backup/backupoptions.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backupoptions.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/create-backup/backupoptions.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/create-backup/environment.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/create-backup/environment.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/create-backup/environment.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/create-backup/environment.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/database-size-reduction/Untitled.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/database-size-reduction/Untitled.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/database-size-reduction/Untitled.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/database-size-reduction/Untitled.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/download-backup/backup-choice.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/backup-choice.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/download-backup/backup-choice.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/backup-choice.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/download-backup/backupoptions.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/backupoptions.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/download-backup/backupoptions.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/backupoptions.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/download-backup/environment.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/environment.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/download-backup/environment.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/download-backup/environment.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/add-configuration.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/add-configuration.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/add-configuration.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/add-configuration.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/add-database.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/add-database.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/add-database.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/add-database.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/app-settings.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/app-settings.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/app-settings.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/app-settings.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/backup-choice.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/backup-choice.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/backup-choice.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/backup-choice.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/backup-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/backup-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/backup-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/backup-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/project-directory.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/project-directory.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/project-directory.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/project-directory.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/restore-database.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/restore-database.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/restore-database.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/restore-database.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/restore-options.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/restore-options.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup-locally/restore-options.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup-locally/restore-options.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/backupoptions.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/backupoptions.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/backupoptions.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/backupoptions.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/environment.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/environment.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/environment.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/environment.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/restore-backup.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/restore-backup.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/restore-backup.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/restore-backup.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/tar-gz-structure.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/tar-gz-structure.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/tar-gz-structure.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/backups/restore-backup/tar-gz-structure.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/certificates/certificate-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/certificates/certificate-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/certificates/certificate-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/certificates/certificate-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/certificates/certificate.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/certificates/certificate.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/certificates/certificate.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/certificates/certificate.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/app-env-certificates.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/app-env-certificates.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/app-env-certificates.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/app-env-certificates.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-edit.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate-edit.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-edit.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate-edit.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-list.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate-list.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-list.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate-list.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/certificate.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domain.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/custom-domain.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domain.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/custom-domain.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domains-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/custom-domains-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domains-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/custom-domains-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/environment-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/environment-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/environment-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/environment-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/generate-cert-req.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/generate-cert-req.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/generate-cert-req.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/generate-cert-req.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/network.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/network.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/network.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/network.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/new-certificate.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-certificate.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/new-certificate.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-certificate.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/new-custom-domain.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-custom-domain.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/new-custom-domain.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/new-custom-domain.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/pem-format.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/pem-format.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/pem-format.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/pem-format.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/custom-domains/signed-certificate.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/signed-certificate.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/custom-domains/signed-certificate.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/custom-domains/signed-certificate.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/deploy-package.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/deploy-package.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/deploy-package.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/deploy-package.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/deploy-to-cloud-node.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/deploy-to-cloud-node.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/deploy-to-cloud-node.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/deploy-to-cloud-node.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/actions-stopped.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/actions-stopped.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/actions-stopped.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/actions-stopped.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/actions-v5.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/actions-v5.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/actions-v5.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/actions-v5.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/change-scaling.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/change-scaling.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/change-scaling.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/change-scaling.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/clear-environment.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/clear-environment.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/clear-environment.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/clear-environment.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/edit-constant.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/edit-constant.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/edit-constant.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/edit-constant.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/environment-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/environment-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/environment-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/environment-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/environment-variable.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/environment-variable.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/environment-variable.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/environment-variable.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-dropdown.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-dropdown.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-dropdown.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-dropdown.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-string.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-string.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-string.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-string.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-url.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-url.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/http-header-url.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/http-header-url.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/loglevels-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/loglevels-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/loglevels-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/loglevels-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/loglevels.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/loglevels.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/loglevels.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/loglevels.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/maintenance.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/maintenance.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/maintenance.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/maintenance.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/model-options.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/model-options.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/model-options.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/model-options.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/network1.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/network1.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/network1.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/network1.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/runtime.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/runtime.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/runtime.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/runtime.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/scale.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/scale.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/scale.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/scale.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details/tags.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/tags.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments-details/tags.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments-details/tags.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/activity.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/activity.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/activity.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/activity.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/deploy-icon.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deploy-icon.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/deploy-icon.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deploy-icon.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/deploy-package.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deploy-package.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/deploy-package.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deploy-package.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/deployment-package-options.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deployment-package-options.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/deployment-package-options.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deployment-package-options.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/deployment-package.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deployment-package.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/deployment-package.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/deployment-package.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/reorder-environments.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/reorder-environments.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/reorder-environments.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/reorder-environments.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments/transport-to.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/transport-to.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/environments/transport-to.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/environments/transport-to.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/billing-accounts-page.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/billing-accounts-page.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/billing-accounts-page.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/billing-accounts-page.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/configure-basic-package.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/configure-basic-package.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/configure-basic-package.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/configure-basic-package.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/free-app-message.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/free-app-message.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/basic-package/free-app-message.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/basic-package/free-app-message.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/choose-node.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/choose-node.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/choose-node.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/choose-node.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/confirm-replace.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/confirm-replace.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/confirm-replace.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/confirm-replace.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/confirm-unlink.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/confirm-unlink.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/confirm-unlink.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/confirm-unlink.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/exchange-apps.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/exchange-apps.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/exchange-apps.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/exchange-apps.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/link-node.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/link-node.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/link-node.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/link-node.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/confirm-unlink.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/confirm-unlink.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/confirm-unlink.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/confirm-unlink.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/download-backup.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/download-backup.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/download-backup.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/download-backup.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/link-node.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/restore-backup.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/restore-backup.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/backups/restore-backup/restore-backup.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/restore-backup.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/unlink-free-app.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/unlink-free-app.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/unlink-free-app.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/migrate-free-app-to-basic/unlink-free-app.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/licensing-apps/unlink-free-app.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/unlink-free-app.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/licensing-apps/unlink-free-app.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/licensing-apps/unlink-free-app.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/logs/activity-log.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/activity-log.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/logs/activity-log.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/activity-log.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/logs/free-app.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/free-app.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/logs/free-app.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/free-app.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/logs/live-log.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/live-log.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/logs/live-log.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/live-log.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/logs/log-sap.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/log-sap.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/logs/log-sap.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/log-sap.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/logs/logs-archives.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/logs-archives.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/logs/logs-archives.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/logs-archives.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/logs/logs-filter.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/logs-filter.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/logs/logs-filter.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/logs/logs-filter.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/maintenance-windows/environment-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/maintenance-windows/environment-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/maintenance-windows/environment-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/maintenance-windows/environment-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/maintenance-windows/maintenance.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/maintenance-windows/maintenance.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/maintenance-windows/maintenance.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/maintenance-windows/maintenance.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/mendix-sso/access-management-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/access-management-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/mendix-sso/access-management-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/access-management-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/mendix-sso/authorize-access.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/authorize-access.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/mendix-sso/authorize-access.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/authorize-access.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/mendix-sso/sso-sign-on.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/sso-sign-on.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/mendix-sso/sso-sign-on.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/sso-sign-on.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/mendix-sso/transport-to-flex.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/transport-to-flex.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/mendix-sso/transport-to-flex.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/mendix-sso/transport-to-flex.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-accounts-logins.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-accounts-logins.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-accounts-logins.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-accounts-logins.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-cpu-usage.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-cpu-usage.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-cpu-usage.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-cpu-usage.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-disk-usage.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-disk-usage.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-disk-usage.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-disk-usage.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-ext-requests.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-ext-requests.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-ext-requests.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-ext-requests.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-heap.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-heap.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-heap.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-heap.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-memory.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-memory.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-memory.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-memory.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-thread-count.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-thread-count.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-jvm-thread-count.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-jvm-thread-count.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-memory-usage.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-memory-usage.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-memory-usage.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-memory-usage.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-number-of-files.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-number-of-files.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-number-of-files.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-number-of-files.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-size-of-files.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-size-of-files.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-size-of-files.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-size-of-files.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/app-threadpool.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-threadpool.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/app-threadpool.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/app-threadpool.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-api-keys.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-api-keys.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-api-keys.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-api-keys.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-integrations-api.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-integrations-api.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-integrations-api.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-integrations-api.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-mendix-integration.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-mendix-integration.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-mendix-integration.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-mendix-integration.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-summary-tags.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-summary-tags.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-summary-tags.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/datadog-summary-tags.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/dd-api-key.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/dd-api-key.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/dd-api-key.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/dd-api-key.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/environment-variable-dd-api-key.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/environment-variable-dd-api-key.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/environment-variable-dd-api-key.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/environment-variable-dd-api-key.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/mendix-application-overview.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/mendix-application-overview.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/mendix-application-overview.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/mendix-application-overview.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/set-tags.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/set-tags.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/set-tags.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/datadog-metrics/set-tags.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-connections-no.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-connections-no.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-connections-no.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-connections-no.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-cpu-usage.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-cpu-usage.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-cpu-usage.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-cpu-usage.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-disk-usage.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-disk-usage.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-disk-usage.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-disk-usage.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-io-latency.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-io-latency.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-io-latency.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-io-latency.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-iops-burst-balance.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-iops-burst-balance.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-iops-burst-balance.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-iops-burst-balance.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-iops.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-iops.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-iops.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-iops.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-memory.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-memory.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-memory.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-memory.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-mutations.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-mutations.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-mutations.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-mutations.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-queries-no.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-queries-no.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-queries-no.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-queries-no.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-table-vs-index.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-table-vs-index.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-table-vs-index.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-table-vs-index.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/db-throughput.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-throughput.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/db-throughput.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/db-throughput.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/metrics-agent-config.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/metrics-agent-config.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/metrics-agent-config.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/metrics-agent-config.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/metrics/metrics-selection.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/metrics-selection.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/metrics/metrics-selection.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/metrics/metrics-selection.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/migrating/deployment-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/deployment-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/migrating/deployment-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/deployment-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/migrating/migratev4.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/migratev4.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/migrating/migratev4.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/migratev4.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/migrating/select-a-node.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/select-a-node.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/migrating/select-a-node.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/select-a-node.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/migrating/tls-certificates.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/tls-certificates.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/migrating/tls-certificates.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/tls-certificates.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/migrating/upload-package.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/upload-package.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/migrating/upload-package.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/migrating/upload-package.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/alert-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/alert-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/alert-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/alert-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/alerts-history.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/alerts-history.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/alerts-history.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/alerts-history.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/application-status.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/application-status.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/application-status.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/application-status.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts/email-alerts.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts/email-alerts.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts/email-alerts.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts/email-alerts.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts/receive-alerts.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts/receive-alerts.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/monitoring-application-health/receive-alerts/receive-alerts.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/monitoring-application-health/receive-alerts/receive-alerts.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/node-permissions/change-environments.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/change-environments.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/node-permissions/change-environments.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/change-environments.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/node-permissions/node-permission.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/node-permission.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/node-permissions/node-permission.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/node-permission.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/node-permissions/nodes-list.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/nodes-list.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/node-permissions/nodes-list.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/nodes-list.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/node-permissions/permissions-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/permissions-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/node-permissions/permissions-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/node-permissions/permissions-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/pipelines/designs-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/designs-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/pipelines/designs-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/designs-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/pipelines/pipeline-design.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/pipeline-design.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/pipelines/pipeline-design.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/pipeline-design.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/pipelines/run-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/run-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/pipelines/run-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/run-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/pipelines/runs-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/runs-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/pipelines/runs-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/runs-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/pipelines/settings-tab.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/settings-tab.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/pipelines/settings-tab.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/pipelines/settings-tab.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/runapp.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/runapp.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/runapp.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/runapp.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/runapp2.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/runapp2.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/runapp2.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/runapp2.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/scale-environment/change-scaling.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/change-scaling.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/scale-environment/change-scaling.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/change-scaling.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/scale-environment/scale.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/scale.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/scale-environment/scale.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/scale.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/scale-environment/scaling-example.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/scaling-example.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/scale-environment/scaling-example.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/scale-environment/scaling-example.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/select-revision.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/select-revision.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/select-revision.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/select-revision.png diff --git a/static/attachments/deployment/general/software-composition/all-components.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/all-components.png similarity index 100% rename from static/attachments/deployment/general/software-composition/all-components.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/all-components.png diff --git a/static/attachments/deployment/general/software-composition/component-summary.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/component-summary.png similarity index 100% rename from static/attachments/deployment/general/software-composition/component-summary.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/component-summary.png diff --git a/static/attachments/deployment/general/software-composition/component-usage.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/component-usage.png similarity index 100% rename from static/attachments/deployment/general/software-composition/component-usage.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/component-usage.png diff --git a/static/attachments/deployment/general/software-composition/overview.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/overview.png similarity index 100% rename from static/attachments/deployment/general/software-composition/overview.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/software-composition/overview.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/studio-deployment-settings/setup-studio-pro-deployment.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/studio-deployment-settings/setup-studio-pro-deployment.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/studio-deployment-settings/setup-studio-pro-deployment.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/studio-deployment-settings/setup-studio-pro-deployment.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/transport-to-flex.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/transport-to-flex.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/transport-to-flex.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/transport-to-flex.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/dialog-box.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/dialog-box.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/dialog-box.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/dialog-box.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/running-request-details.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/running-request-details.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/running-request-details.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/running-request-details.png diff --git a/static/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/stack.png b/static/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/stack.png similarity index 100% rename from static/attachments/deployment/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/stack.png rename to static/attachments/developerportal/deploy/mendix-cloud-deploy/troubleshooting-mxcloud-runningnow/stack.png diff --git a/static/attachments/deployment/on-premises-design/18580717.jpg b/static/attachments/developerportal/deploy/on-premises-design/18580717.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/18580717.jpg rename to static/attachments/developerportal/deploy/on-premises-design/18580717.jpg diff --git a/static/attachments/deployment/on-premises-design/18580718.jpg b/static/attachments/developerportal/deploy/on-premises-design/18580718.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/18580718.jpg rename to static/attachments/developerportal/deploy/on-premises-design/18580718.jpg diff --git a/static/attachments/deployment/on-premises-design/18580719.jpg b/static/attachments/developerportal/deploy/on-premises-design/18580719.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/18580719.jpg rename to static/attachments/developerportal/deploy/on-premises-design/18580719.jpg diff --git a/static/attachments/deployment/on-premises-design/18580720.jpg b/static/attachments/developerportal/deploy/on-premises-design/18580720.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/18580720.jpg rename to static/attachments/developerportal/deploy/on-premises-design/18580720.jpg diff --git a/static/attachments/deployment/on-premises-design/ms-windows/18580726.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580726.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/18580726.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580726.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/18580728.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580728.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/18580728.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580728.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/18580730.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580730.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/18580730.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580730.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/18580733.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580733.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/18580733.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/18580733.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398813.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398813.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398813.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398813.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398814.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398815.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398815.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398815.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398815.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398816.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398816.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398816.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398816.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398817.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398817.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398817.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/activate-a-mendix-license-on-microsoft-windows/19398817.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/application_storage_settings.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/application_storage_settings.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/application_storage_settings.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/application_storage_settings.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/azure_storage_keys.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/azure_storage_keys.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/azure_storage_keys.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/azure_storage_keys.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_add_setting.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_add_setting.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_add_setting.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_add_setting.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_advanced.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_advanced.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_advanced.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_advanced.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_configuration.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_configuration.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_configuration.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/deploy-mendix-ha-on-windows-in-microsoft-azure/slave_click_configuration.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/iis_add_https_binding.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/iis_add_https_binding.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/iis_add_https_binding.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/iis_add_https_binding.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/iis_response_headers.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/iis_response_headers.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/iis_response_headers.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/iis_response_headers.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/service_console_download.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_download.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/service_console_download.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_download.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/service_console_first_run.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_first_run.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/service_console_first_run.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_first_run.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/service_console_selectapp.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_selectapp.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/service_console_selectapp.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/service_console_selectapp.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580648.jpg b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580648.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580648.jpg rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580648.jpg diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580649.jpg b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580649.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580649.jpg rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580649.jpg diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580650.jpg b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580650.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580650.jpg rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580650.jpg diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580651.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580651.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580651.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580651.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580652.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580652.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580652.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580652.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580653.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580653.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580653.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580653.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580654.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580654.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580654.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580654.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580655.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580655.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580655.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580655.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580658.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580658.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580658.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580658.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580659.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580659.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580659.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580659.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580660.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580660.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580660.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580660.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580661.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580661.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580661.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580661.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580662.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580662.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580662.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580662.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580663.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580663.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580663.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580663.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580665.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580665.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580665.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580665.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580666.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580666.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580666.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580666.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580667.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580667.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580667.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580667.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580668.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580668.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580668.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/mendix-sql-maintenance-plans/18580668.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database/18580646.jpg b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database/18580646.jpg similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database/18580646.jpg rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/restoring-a-sql-server-database/18580646.jpg diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580675.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580675.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580675.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580675.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580676.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580676.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580676.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-a-new-sql-server-database/18580676.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580671.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580671.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580671.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580671.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580672.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580672.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580672.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580672.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580673.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580673.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580673.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580673.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580674.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580674.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580674.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/sql-server/setting-up-the-database-user/18580674.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/troubleshooting-iis/18580723.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/troubleshooting-iis/18580723.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/troubleshooting-iis/18580723.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/troubleshooting-iis/18580723.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/18580698.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/18580698.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/18580698.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/18580698.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/1_stop_service.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/1_stop_service.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/1_stop_service.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/1_stop_service.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/2_click_update.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/2_click_update.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/2_click_update.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/2_click_update.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/3_update_app.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/3_update_app.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/3_update_app.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/3_update_app.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/4_browse_mda.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/4_browse_mda.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/4_browse_mda.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/4_browse_mda.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_download.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_download.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_download.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_download.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_missing.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_missing.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_missing.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_missing.png diff --git a/static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_select.png b/static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_select.png similarity index 100% rename from static/attachments/deployment/on-premises-design/ms-windows/updating-a-mendix-application/update_server_select.png rename to static/attachments/developerportal/deploy/on-premises-design/ms-windows/updating-a-mendix-application/update_server_select.png diff --git a/static/attachments/deployment/on-premises-design/setting-up-monitoring-with-new-relic/18580677.png b/static/attachments/developerportal/deploy/on-premises-design/setting-up-monitoring-with-new-relic/18580677.png similarity index 100% rename from static/attachments/deployment/on-premises-design/setting-up-monitoring-with-new-relic/18580677.png rename to static/attachments/developerportal/deploy/on-premises-design/setting-up-monitoring-with-new-relic/18580677.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator1.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator1.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator1.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator1.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator2.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator2.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator2.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator2.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator3.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator3.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator3.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator3.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator4.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator4.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator4.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator4.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator5.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator5.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator5.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator5.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator6.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator6.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator6.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator6.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator7.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator7.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator7.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator7.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator8.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator8.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator8.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator8.png diff --git a/static/attachments/deployment/private-cloud/global-operator/global-operator9.png b/static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator9.png similarity index 100% rename from static/attachments/deployment/private-cloud/global-operator/global-operator9.png rename to static/attachments/developerportal/deploy/private-cloud/global-operator/global-operator9.png diff --git a/static/attachments/deployment/private-cloud/mx4pc-architecture.png b/static/attachments/developerportal/deploy/private-cloud/mx4pc-architecture.png similarity index 100% rename from static/attachments/deployment/private-cloud/mx4pc-architecture.png rename to static/attachments/developerportal/deploy/private-cloud/mx4pc-architecture.png diff --git a/static/attachments/deployment/private-cloud/mx4pc-standalone-architecture.png b/static/attachments/developerportal/deploy/private-cloud/mx4pc-standalone-architecture.png similarity index 100% rename from static/attachments/deployment/private-cloud/mx4pc-standalone-architecture.png rename to static/attachments/developerportal/deploy/private-cloud/mx4pc-standalone-architecture.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptClusterManager.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/AutoAcceptClusterManager.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptClusterManager.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/AutoAcceptClusterManager.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptInvite.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/AutoAcceptInvite.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptInvite.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/AutoAcceptInvite.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/ClusterDetails.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/ClusterDetails.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/ClusterDetails.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/ClusterDetails.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/Customization.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/Customization.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/Customization.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/Customization.png diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicenseClaim.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicenseClaim.png new file mode 100644 index 00000000000..b191e86867e Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicenseClaim.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicensePayload.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicensePayload.png new file mode 100644 index 00000000000..e9409208288 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/LicensePayload.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/OperatorList.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/OperatorList.png new file mode 100644 index 00000000000..7a281884773 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/OperatorList.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/PCLMDownload.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/PCLMDownload.png new file mode 100644 index 00000000000..b99cc206bd8 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/PCLMDownload.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/RuntimeList.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/RuntimeList.png new file mode 100644 index 00000000000..08d8e9f9b9d Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/RuntimeList.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/SetupButton.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/SetupButton.png new file mode 100644 index 00000000000..90c7d36c675 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/SetupButton.png differ diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/add-namespace.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/add-namespace.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/add-namespace.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/add-namespace.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/apply-configuration.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/apply-configuration.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/apply-configuration.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/apply-configuration.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/choose-operating-system.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/choose-operating-system.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/choose-operating-system.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/choose-operating-system.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/cluster-activity-logs.PNG b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-activity-logs.PNG similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/cluster-activity-logs.PNG rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-activity-logs.PNG diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/cluster-details.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-details.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/cluster-details.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-details.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/cluster-manager.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/configure-namespace.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/configure-namespace.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/configure-namespace.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/configure-namespace.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/create-cluster.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/create-cluster.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/create-cluster.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/create-cluster.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/custom-tls-config.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/custom-tls-config.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/custom-tls-config.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/custom-tls-config.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/customPlan.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlan.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/customPlan.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlan.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/customPlanDetails.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlanDetails.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/customPlanDetails.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlanDetails.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/customPlanEnable.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlanEnable.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/customPlanEnable.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/customPlanEnable.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/database-plan-config.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/database-plan-config.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/database-plan-config.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/database-plan-config.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/download-executable.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/download-executable.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/download-executable.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/download-executable.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/download-operator-version.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/download-operator-version.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/download-operator-version.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/download-operator-version.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/empty-cluster.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/empty-cluster.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/empty-cluster.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/empty-cluster.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/evaluate-configuration.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/evaluate-configuration.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/evaluate-configuration.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/evaluate-configuration.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image10.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image10.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image10.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image10.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image11.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image11.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image11.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image11.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image22.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image22.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image22.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image22.png diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image25.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image25.png new file mode 100644 index 00000000000..1dd7b2da8d2 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image25.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image26.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image26.png new file mode 100644 index 00000000000..431ecf9bccd Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image26.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image27.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image27.png new file mode 100644 index 00000000000..a76ce9eab39 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image27.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image28.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image28.png new file mode 100644 index 00000000000..c69d7b2d6d3 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image28.png differ diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image3.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image3.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image3.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image3.png diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image30.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image30.png new file mode 100644 index 00000000000..6c18f99fe61 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image30.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image32.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image32.png new file mode 100644 index 00000000000..89d9e786d21 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image32.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image33.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image33.png new file mode 100644 index 00000000000..93e7db045ab Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image33.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image34.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image34.png new file mode 100644 index 00000000000..2308849b73f Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image34.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image35.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image35.png new file mode 100644 index 00000000000..73415118005 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image35.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image36.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image36.png new file mode 100644 index 00000000000..2220662c764 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image36.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image37.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image37.png new file mode 100644 index 00000000000..dbc1206cb17 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image37.png differ diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image4.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image4.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image4.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image4.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image6.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image6.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image6.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image6.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/image9.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image9.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/image9.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/image9.png diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installation-command.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installation-command.png new file mode 100644 index 00000000000..8daac92375f Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installation-command.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installation-wizard.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installation-wizard.png new file mode 100644 index 00000000000..dfe89ba44e6 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installation-wizard.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installer-options.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installer-options.png new file mode 100644 index 00000000000..b9606a4e1c5 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/installer-options.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-architecture.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-architecture.png new file mode 100644 index 00000000000..e55df35538f Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-architecture.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-containerized-architecture.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-containerized-architecture.png new file mode 100644 index 00000000000..ff100ecc04d Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/mx4pc-containerized-architecture.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details-standalone.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details-standalone.png new file mode 100644 index 00000000000..7874aebfac3 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details-standalone.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details.PNG b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details.PNG new file mode 100644 index 00000000000..fbad13cedf0 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/namespace-details.PNG differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/post-install-landing-page.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/post-install-landing-page.png new file mode 100644 index 00000000000..0beba90c6be Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/post-install-landing-page.png differ diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive/installation-command.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive/installation-command.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive/installation-command.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-cli-non-interactive/installation-command.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating/export.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating/export.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating/export.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating/export.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating/import.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating/import.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-migrating/import.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating/import.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/IRSA-OIDC.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/IRSA-OIDC.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/IRSA-OIDC.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/IRSA-OIDC.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Connection.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Connection.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Connection.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Connection.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Endpoint.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Endpoint.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Endpoint.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-storage-plans/RDS-Endpoint.png diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/review-and-apply.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/review-and-apply.png new file mode 100644 index 00000000000..488d55385ee Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/review-and-apply.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/savedCustomPlan.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/savedCustomPlan.png new file mode 100644 index 00000000000..5be5182bfd8 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/savedCustomPlan.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/standalone_downloadcli.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/standalone_downloadcli.png new file mode 100644 index 00000000000..59655c33d0e Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/standalone_downloadcli.png differ diff --git a/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/write-yaml.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/write-yaml.png new file mode 100644 index 00000000000..e05aabba329 Binary files /dev/null and b/static/attachments/developerportal/deploy/private-cloud/private-cloud-cluster/write-yaml.png differ diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/ApplyChangesPage.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/ApplyChangesPage.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/ApplyChangesPage.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/ApplyChangesPage.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/LicensePCLM.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/LicensePCLM.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/LicensePCLM.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/LicensePCLM.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/PCLM.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/PCLM.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/PCLM.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/PCLM.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/awsserviceaccountlinktorole.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/choose-secret.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/choose-secret.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/choose-secret.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/choose-secret.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/configureEnvResources.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/configureEnvResources.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/configureEnvResources.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/configureEnvResources.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/constantTab.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/constantTab.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/constantTab.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/constantTab.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/customizeEnvironmentNamespaceSelection.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/customizeEnvironmentNamespaceSelection.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/customizeEnvironmentNamespaceSelection.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/customizeEnvironmentNamespaceSelection.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/customizeEnvironmentPage1.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/customizeEnvironmentPage1.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/customizeEnvironmentPage1.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/customizeEnvironmentPage1.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/debuggerTab.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/debuggerTab.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/debuggerTab.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/debuggerTab.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/delete-environment.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/delete-environment.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/delete-environment.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/delete-environment.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/deprovision-failed.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/deprovision-failed.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/deprovision-failed.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/deprovision-failed.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/enable-tls.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/enable-tls.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/enable-tls.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/enable-tls.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image10.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image10.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image10.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image10.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image11.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image11.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image11.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image11.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image12.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image12.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image12.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image12.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image15.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image15.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image15.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image15.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image16.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image16.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image16.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image16.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image17.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image17.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image17.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image17.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image18.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image18.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image18.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image18.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image2.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image2.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image2.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image2.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image20.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image20.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image20.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image20.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image21.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image21.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image21.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image21.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image22.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image22.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image22.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image22.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image23.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image23.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image23.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image23.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image24.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image24.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image24.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image24.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image5.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image5.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image5.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image5.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image7.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image7.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image7.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image7.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image8.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image8.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image8.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image8.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/image9.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image9.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/image9.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/image9.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/lock.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/lock.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/lock.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/lock.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-1.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-1.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-1.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-1.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-2.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-2.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-2.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-2.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-3.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-3.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/log-levels-tab-3.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/log-levels-tab-3.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/mx4pc-containerized-architecture.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/mx4pc-containerized-architecture.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/mx4pc-containerized-architecture.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/mx4pc-containerized-architecture.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/mx4pc-operator-deploy.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/mx4pc-operator-deploy.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/mx4pc-operator-deploy.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/mx4pc-operator-deploy.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/network-tab.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/network-tab.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/network-tab.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/network-tab.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/new-tls-key.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/new-tls-key.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/new-tls-key.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/new-tls-key.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/runtime-tab.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/runtime-tab.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/runtime-tab.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/runtime-tab.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/scheduledevent.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/scheduledevent.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/scheduledevent.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/scheduledevent.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/selectDeploymentpackage.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/selectDeploymentpackage.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/selectDeploymentpackage.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/selectDeploymentpackage.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-deploy/tls-configuration.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/tls-configuration.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-deploy/tls-configuration.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-deploy/tls-configuration.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-fine-grained.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-fine-grained.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-fine-grained.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-fine-grained.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-environments/mx4pc-environments-minimal.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-details-general.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-details-general.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-details-general.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-details-general.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-apply.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-apply.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-apply.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-apply.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-default.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-default.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-default.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-default.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-disabled.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-disabled.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-disabled.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-disabled.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-native.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-native.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-native.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-metrics-mode-native.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/environment-overview.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-overview.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/environment-overview.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/environment-overview.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import-button.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import-button.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import-button.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import-button.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import-settings.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import-settings.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import-settings.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import-settings.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-import.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-import.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-open-dashboard.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-open-dashboard.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-open-dashboard.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-open-dashboard.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-select-pod.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-select-pod.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/grafana-select-pod.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/grafana-select-pod.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-apply-annotations.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-apply-annotations.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-apply-annotations.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-apply-annotations.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-native.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-metrics-native.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-native.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-metrics-native.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-prometheus-annotations.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-quick-setup-prometheus.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-quick-setup-prometheus.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-quick-setup-prometheus.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-monitor/private-cloud-quick-setup-prometheus.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-operator/constant-name.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/constant-name.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-operator/constant-name.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/constant-name.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-operator/environments-create-mda.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/environments-create-mda.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-operator/environments-create-mda.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/environments-create-mda.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-operator/image1.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/image1.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-operator/image1.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/image1.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-operator/image2.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/image2.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-operator/image2.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-operator/image2.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/crd-controller-hierarchy.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/crd-controller-hierarchy.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/crd-controller-hierarchy.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/crd-controller-hierarchy.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-applicationrooturl.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-applicationrooturl.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-applicationrooturl.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-applicationrooturl.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-build-image.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-build-image.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-build-image.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-build-image.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-deployment.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-deployment.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-deployment.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-deployment.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-ingress-controller.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-ingress-controller.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-ingress-controller.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-ingress-controller.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-installation.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-installation.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-installation.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-installation.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-logging-metering.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-logging-metering.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-logging-metering.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-logging-metering.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-provision-storage.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-provision-storage.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-provision-storage.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-provision-storage.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-ingress.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-ingress.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-ingress.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-ingress.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-service.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-service.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-service.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-technical-appendix/private-cloud-technical-appendix-02/mx4pc-traffic-service.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-tekton/build-pipeline.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/build-pipeline.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-tekton/build-pipeline.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/build-pipeline.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-tekton/gitlab-webhook.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/gitlab-webhook.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-tekton/gitlab-webhook.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/gitlab-webhook.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-tekton/tekton-architecture-example.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/tekton-architecture-example.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-tekton/tekton-architecture-example.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-tekton/tekton-architecture-example.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-upgrade-guide/mxpc-cli-welcome.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-upgrade-guide/mxpc-cli-welcome.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-upgrade-guide/mxpc-cli-welcome.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-upgrade-guide/mxpc-cli-welcome.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-upgrade-guide/upgrade-wizard.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-upgrade-guide/upgrade-wizard.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-upgrade-guide/upgrade-wizard.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-upgrade-guide/upgrade-wizard.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-vault/aks-enable-csi-driver.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-vault/aks-enable-csi-driver.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-vault/aks-enable-csi-driver.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-vault/aks-enable-csi-driver.png diff --git a/static/attachments/deployment/private-cloud/private-cloud-vault/aks-keyvault-keys.png b/static/attachments/developerportal/deploy/private-cloud/private-cloud-vault/aks-keyvault-keys.png similarity index 100% rename from static/attachments/deployment/private-cloud/private-cloud-vault/aks-keyvault-keys.png rename to static/attachments/developerportal/deploy/private-cloud/private-cloud-vault/aks-keyvault-keys.png diff --git a/static/attachments/deployment/sap-autoscaler/add-dynamic.png b/static/attachments/developerportal/deploy/sap-autoscaler/add-dynamic.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/add-dynamic.png rename to static/attachments/developerportal/deploy/sap-autoscaler/add-dynamic.png diff --git a/static/attachments/deployment/sap-autoscaler/add-recurring-date.png b/static/attachments/developerportal/deploy/sap-autoscaler/add-recurring-date.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/add-recurring-date.png rename to static/attachments/developerportal/deploy/sap-autoscaler/add-recurring-date.png diff --git a/static/attachments/deployment/sap-autoscaler/add-specific-date.png b/static/attachments/developerportal/deploy/sap-autoscaler/add-specific-date.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/add-specific-date.png rename to static/attachments/developerportal/deploy/sap-autoscaler/add-specific-date.png diff --git a/static/attachments/deployment/sap-autoscaler/autoscaler-service.png b/static/attachments/developerportal/deploy/sap-autoscaler/autoscaler-service.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/autoscaler-service.png rename to static/attachments/developerportal/deploy/sap-autoscaler/autoscaler-service.png diff --git a/static/attachments/deployment/sap-autoscaler/dynamic.png b/static/attachments/developerportal/deploy/sap-autoscaler/dynamic.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/dynamic.png rename to static/attachments/developerportal/deploy/sap-autoscaler/dynamic.png diff --git a/static/attachments/deployment/sap-autoscaler/recurring-date.png b/static/attachments/developerportal/deploy/sap-autoscaler/recurring-date.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/recurring-date.png rename to static/attachments/developerportal/deploy/sap-autoscaler/recurring-date.png diff --git a/static/attachments/deployment/sap-autoscaler/specific-date.png b/static/attachments/developerportal/deploy/sap-autoscaler/specific-date.png similarity index 100% rename from static/attachments/deployment/sap-autoscaler/specific-date.png rename to static/attachments/developerportal/deploy/sap-autoscaler/specific-date.png diff --git a/static/attachments/deployment/sap-cloud-platform/01-sap-select-region.png b/static/attachments/developerportal/deploy/sap-cloud-platform/01-sap-select-region.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/01-sap-select-region.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/01-sap-select-region.png diff --git a/static/attachments/deployment/sap-cloud-platform/03-sap-select-branch.png b/static/attachments/developerportal/deploy/sap-cloud-platform/03-sap-select-branch.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/03-sap-select-branch.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/03-sap-select-branch.png diff --git a/static/attachments/deployment/sap-cloud-platform/04-sap-select-revision.png b/static/attachments/developerportal/deploy/sap-cloud-platform/04-sap-select-revision.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/04-sap-select-revision.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/04-sap-select-revision.png diff --git a/static/attachments/deployment/sap-cloud-platform/05-sap-define-tag.png b/static/attachments/developerportal/deploy/sap-cloud-platform/05-sap-define-tag.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/05-sap-define-tag.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/05-sap-define-tag.png diff --git a/static/attachments/deployment/sap-cloud-platform/06-sap-build-revision.png b/static/attachments/developerportal/deploy/sap-cloud-platform/06-sap-build-revision.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/06-sap-build-revision.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/06-sap-build-revision.png diff --git a/static/attachments/deployment/sap-cloud-platform/07-sap-env-1.png b/static/attachments/developerportal/deploy/sap-cloud-platform/07-sap-env-1.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/07-sap-env-1.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/07-sap-env-1.png diff --git a/static/attachments/deployment/sap-cloud-platform/08-sap-env-2.png b/static/attachments/developerportal/deploy/sap-cloud-platform/08-sap-env-2.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/08-sap-env-2.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/08-sap-env-2.png diff --git a/static/attachments/deployment/sap-cloud-platform/09-sap-env-3.png b/static/attachments/developerportal/deploy/sap-cloud-platform/09-sap-env-3.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/09-sap-env-3.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/09-sap-env-3.png diff --git a/static/attachments/deployment/sap-cloud-platform/10-sap-env-tap.png b/static/attachments/developerportal/deploy/sap-cloud-platform/10-sap-env-tap.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/10-sap-env-tap.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/10-sap-env-tap.png diff --git a/static/attachments/deployment/sap-cloud-platform/11-sap-env-details.png b/static/attachments/developerportal/deploy/sap-cloud-platform/11-sap-env-details.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/11-sap-env-details.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/11-sap-env-details.png diff --git a/static/attachments/deployment/sap-cloud-platform/12-sap-model-options.png b/static/attachments/developerportal/deploy/sap-cloud-platform/12-sap-model-options.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/12-sap-model-options.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/12-sap-model-options.png diff --git a/static/attachments/deployment/sap-cloud-platform/add-binding-configuration.png b/static/attachments/developerportal/deploy/sap-cloud-platform/add-binding-configuration.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/add-binding-configuration.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/add-binding-configuration.png diff --git a/static/attachments/deployment/sap-cloud-platform/add-environment.png b/static/attachments/developerportal/deploy/sap-cloud-platform/add-environment.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/add-environment.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/add-environment.png diff --git a/static/attachments/deployment/sap-cloud-platform/application-started.png b/static/attachments/developerportal/deploy/sap-cloud-platform/application-started.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/application-started.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/application-started.png diff --git a/static/attachments/deployment/sap-cloud-platform/binding-credentials.png b/static/attachments/developerportal/deploy/sap-cloud-platform/binding-credentials.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/binding-credentials.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/binding-credentials.png diff --git a/static/attachments/deployment/sap-cloud-platform/cloud-settings-landing-page.png b/static/attachments/developerportal/deploy/sap-cloud-platform/cloud-settings-landing-page.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/cloud-settings-landing-page.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/cloud-settings-landing-page.png diff --git a/static/attachments/deployment/sap-cloud-platform/cloud-settings.png b/static/attachments/developerportal/deploy/sap-cloud-platform/cloud-settings.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/cloud-settings.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/cloud-settings.png diff --git a/static/attachments/deployment/sap-cloud-platform/create-development.png b/static/attachments/developerportal/deploy/sap-cloud-platform/create-development.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/create-development.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/create-development.png diff --git a/static/attachments/deployment/sap-cloud-platform/custom-database.png b/static/attachments/developerportal/deploy/sap-cloud-platform/custom-database.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/custom-database.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/custom-database.png diff --git a/static/attachments/deployment/sap-cloud-platform/custom-environment-variables-unsupported.png b/static/attachments/developerportal/deploy/sap-cloud-platform/custom-environment-variables-unsupported.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/custom-environment-variables-unsupported.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/custom-environment-variables-unsupported.png diff --git a/static/attachments/deployment/sap-cloud-platform/custom-environment-variables.png b/static/attachments/developerportal/deploy/sap-cloud-platform/custom-environment-variables.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/custom-environment-variables.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/custom-environment-variables.png diff --git a/static/attachments/deployment/sap-cloud-platform/delete-app.png b/static/attachments/developerportal/deploy/sap-cloud-platform/delete-app.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/delete-app.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/delete-app.png diff --git a/static/attachments/deployment/sap-cloud-platform/delete-environment.png b/static/attachments/developerportal/deploy/sap-cloud-platform/delete-environment.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/delete-environment.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/delete-environment.png diff --git a/static/attachments/deployment/sap-cloud-platform/environment-details.png b/static/attachments/developerportal/deploy/sap-cloud-platform/environment-details.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/environment-details.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/environment-details.png diff --git a/static/attachments/deployment/sap-cloud-platform/environments-page.png b/static/attachments/developerportal/deploy/sap-cloud-platform/environments-page.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/environments-page.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/environments-page.png diff --git a/static/attachments/deployment/sap-cloud-platform/error-desktop-modeler.png b/static/attachments/developerportal/deploy/sap-cloud-platform/error-desktop-modeler.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/error-desktop-modeler.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/error-desktop-modeler.png diff --git a/static/attachments/deployment/sap-cloud-platform/error-not-bound.png b/static/attachments/developerportal/deploy/sap-cloud-platform/error-not-bound.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/error-not-bound.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/error-not-bound.png diff --git a/static/attachments/deployment/sap-cloud-platform/failed-description.png b/static/attachments/developerportal/deploy/sap-cloud-platform/failed-description.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/failed-description.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/failed-description.png diff --git a/static/attachments/deployment/sap-cloud-platform/failed-details.png b/static/attachments/developerportal/deploy/sap-cloud-platform/failed-details.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/failed-details.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/failed-details.png diff --git a/static/attachments/deployment/sap-cloud-platform/failed-environment.png b/static/attachments/developerportal/deploy/sap-cloud-platform/failed-environment.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/failed-environment.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/failed-environment.png diff --git a/static/attachments/deployment/sap-cloud-platform/failed-more-details.png b/static/attachments/developerportal/deploy/sap-cloud-platform/failed-more-details.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/failed-more-details.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/failed-more-details.png diff --git a/static/attachments/deployment/sap-cloud-platform/hanatrial-schema.png b/static/attachments/developerportal/deploy/sap-cloud-platform/hanatrial-schema.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/hanatrial-schema.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/hanatrial-schema.png diff --git a/static/attachments/deployment/sap-cloud-platform/postgresql-configurator.png b/static/attachments/developerportal/deploy/sap-cloud-platform/postgresql-configurator.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/postgresql-configurator.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/postgresql-configurator.png diff --git a/static/attachments/deployment/sap-cloud-platform/postgresql-service.png b/static/attachments/developerportal/deploy/sap-cloud-platform/postgresql-service.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/postgresql-service.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/postgresql-service.png diff --git a/static/attachments/deployment/sap-cloud-platform/sap-change-timeout.png b/static/attachments/developerportal/deploy/sap-cloud-platform/sap-change-timeout.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/sap-change-timeout.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/sap-change-timeout.png diff --git a/static/attachments/deployment/sap-cloud-platform/sap-env-0.png b/static/attachments/developerportal/deploy/sap-cloud-platform/sap-env-0.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/sap-env-0.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/sap-env-0.png diff --git a/static/attachments/deployment/sap-cloud-platform/sap-revision-built.png b/static/attachments/developerportal/deploy/sap-cloud-platform/sap-revision-built.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/sap-revision-built.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/sap-revision-built.png diff --git a/static/attachments/deployment/sap-cloud-platform/sap-transport.png b/static/attachments/developerportal/deploy/sap-cloud-platform/sap-transport.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/sap-transport.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/sap-transport.png diff --git a/static/attachments/deployment/sap-cloud-platform/service-bind-error.png b/static/attachments/developerportal/deploy/sap-cloud-platform/service-bind-error.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/service-bind-error.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/service-bind-error.png diff --git a/static/attachments/deployment/sap-cloud-platform/service-connect.png b/static/attachments/developerportal/deploy/sap-cloud-platform/service-connect.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/service-connect.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/service-connect.png diff --git a/static/attachments/deployment/sap-cloud-platform/service-tab.png b/static/attachments/developerportal/deploy/sap-cloud-platform/service-tab.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/service-tab.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/service-tab.png diff --git a/static/attachments/deployment/sap-cloud-platform/service-unbind-warning.png b/static/attachments/developerportal/deploy/sap-cloud-platform/service-unbind-warning.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/service-unbind-warning.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/service-unbind-warning.png diff --git a/static/attachments/deployment/sap-cloud-platform/service-unbind.png b/static/attachments/developerportal/deploy/sap-cloud-platform/service-unbind.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/service-unbind.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/service-unbind.png diff --git a/static/attachments/deployment/sap-cloud-platform/start-application.png b/static/attachments/developerportal/deploy/sap-cloud-platform/start-application.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/start-application.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/start-application.png diff --git a/static/attachments/deployment/sap-cloud-platform/transport-constants.png b/static/attachments/developerportal/deploy/sap-cloud-platform/transport-constants.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/transport-constants.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/transport-constants.png diff --git a/static/attachments/deployment/sap-cloud-platform/transport-deploy.png b/static/attachments/developerportal/deploy/sap-cloud-platform/transport-deploy.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/transport-deploy.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/transport-deploy.png diff --git a/static/attachments/deployment/sap-cloud-platform/transport-environments.png b/static/attachments/developerportal/deploy/sap-cloud-platform/transport-environments.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/transport-environments.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/transport-environments.png diff --git a/static/attachments/deployment/sap-cloud-platform/transport-events.png b/static/attachments/developerportal/deploy/sap-cloud-platform/transport-events.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/transport-events.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/transport-events.png diff --git a/static/attachments/deployment/sap-cloud-platform/transport-from-to.png b/static/attachments/developerportal/deploy/sap-cloud-platform/transport-from-to.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/transport-from-to.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/transport-from-to.png diff --git a/static/attachments/deployment/sap-cloud-platform/transport-services.png b/static/attachments/developerportal/deploy/sap-cloud-platform/transport-services.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/transport-services.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/transport-services.png diff --git a/static/attachments/deployment/sap-cloud-platform/unbind-service.png b/static/attachments/developerportal/deploy/sap-cloud-platform/unbind-service.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/unbind-service.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/unbind-service.png diff --git a/static/attachments/deployment/sap-cloud-platform/upload-mda.png b/static/attachments/developerportal/deploy/sap-cloud-platform/upload-mda.png similarity index 100% rename from static/attachments/deployment/sap-cloud-platform/upload-mda.png rename to static/attachments/developerportal/deploy/sap-cloud-platform/upload-mda.png diff --git a/static/attachments/deployment/sap-destination-service/destination-entity.png b/static/attachments/developerportal/deploy/sap-destination-service/destination-entity.png similarity index 100% rename from static/attachments/deployment/sap-destination-service/destination-entity.png rename to static/attachments/developerportal/deploy/sap-destination-service/destination-entity.png diff --git a/static/attachments/deployment/sap-destination-service/drag-get-destination.png b/static/attachments/developerportal/deploy/sap-destination-service/drag-get-destination.png similarity index 100% rename from static/attachments/deployment/sap-destination-service/drag-get-destination.png rename to static/attachments/developerportal/deploy/sap-destination-service/drag-get-destination.png diff --git a/static/attachments/deployment/sap-destination-service/get-destination-error-flow.png b/static/attachments/developerportal/deploy/sap-destination-service/get-destination-error-flow.png similarity index 100% rename from static/attachments/deployment/sap-destination-service/get-destination-error-flow.png rename to static/attachments/developerportal/deploy/sap-destination-service/get-destination-error-flow.png diff --git a/static/attachments/deployment/sap-destination-service/get-destination-properties.png b/static/attachments/developerportal/deploy/sap-destination-service/get-destination-properties.png similarity index 100% rename from static/attachments/deployment/sap-destination-service/get-destination-properties.png rename to static/attachments/developerportal/deploy/sap-destination-service/get-destination-properties.png diff --git a/static/attachments/deployment/sap-destination-service/sap-cockpit-destinations.png b/static/attachments/developerportal/deploy/sap-destination-service/sap-cockpit-destinations.png similarity index 100% rename from static/attachments/deployment/sap-destination-service/sap-cockpit-destinations.png rename to static/attachments/developerportal/deploy/sap-destination-service/sap-cockpit-destinations.png diff --git a/static/attachments/deployment/sap-destination-service/xsuaaenabled.png b/static/attachments/developerportal/deploy/sap-destination-service/xsuaaenabled.png similarity index 100% rename from static/attachments/deployment/sap-destination-service/xsuaaenabled.png rename to static/attachments/developerportal/deploy/sap-destination-service/xsuaaenabled.png diff --git a/static/attachments/deployment/sap-destination-with-rest/destination-entity.png b/static/attachments/developerportal/deploy/sap-destination-with-rest/destination-entity.png similarity index 100% rename from static/attachments/deployment/sap-destination-with-rest/destination-entity.png rename to static/attachments/developerportal/deploy/sap-destination-with-rest/destination-entity.png diff --git a/static/attachments/deployment/sap-destination-with-rest/rest-general.png b/static/attachments/developerportal/deploy/sap-destination-with-rest/rest-general.png similarity index 100% rename from static/attachments/deployment/sap-destination-with-rest/rest-general.png rename to static/attachments/developerportal/deploy/sap-destination-with-rest/rest-general.png diff --git a/static/attachments/deployment/sap-destination-with-rest/rest-microflow.png b/static/attachments/developerportal/deploy/sap-destination-with-rest/rest-microflow.png similarity index 100% rename from static/attachments/deployment/sap-destination-with-rest/rest-microflow.png rename to static/attachments/developerportal/deploy/sap-destination-with-rest/rest-microflow.png diff --git a/static/attachments/deployment/sap-destination-with-rest/web-service-general.png b/static/attachments/developerportal/deploy/sap-destination-with-rest/web-service-general.png similarity index 100% rename from static/attachments/deployment/sap-destination-with-rest/web-service-general.png rename to static/attachments/developerportal/deploy/sap-destination-with-rest/web-service-general.png diff --git a/static/attachments/deployment/sap-single-sign-on/app-select-sap-region.png b/static/attachments/developerportal/deploy/sap-single-sign-on/app-select-sap-region.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/app-select-sap-region.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/app-select-sap-region.png diff --git a/static/attachments/deployment/sap-single-sign-on/go-back.png b/static/attachments/developerportal/deploy/sap-single-sign-on/go-back.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/go-back.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/go-back.png diff --git a/static/attachments/deployment/sap-single-sign-on/mendix-login-page.png b/static/attachments/developerportal/deploy/sap-single-sign-on/mendix-login-page.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/mendix-login-page.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/mendix-login-page.png diff --git a/static/attachments/deployment/sap-single-sign-on/sap-login-screen.png b/static/attachments/developerportal/deploy/sap-single-sign-on/sap-login-screen.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/sap-login-screen.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/sap-login-screen.png diff --git a/static/attachments/deployment/sap-single-sign-on/select-sap-region.png b/static/attachments/developerportal/deploy/sap-single-sign-on/select-sap-region.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/select-sap-region.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/select-sap-region.png diff --git a/static/attachments/deployment/sap-single-sign-on/server-error.png b/static/attachments/developerportal/deploy/sap-single-sign-on/server-error.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/server-error.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/server-error.png diff --git a/static/attachments/deployment/sap-single-sign-on/where-to.png b/static/attachments/developerportal/deploy/sap-single-sign-on/where-to.png similarity index 100% rename from static/attachments/deployment/sap-single-sign-on/where-to.png rename to static/attachments/developerportal/deploy/sap-single-sign-on/where-to.png diff --git a/static/attachments/deployment/webhooks/validation-microflow.png b/static/attachments/developerportal/deploy/webhooks/validation-microflow.png similarity index 100% rename from static/attachments/deployment/webhooks/validation-microflow.png rename to static/attachments/developerportal/deploy/webhooks/validation-microflow.png diff --git a/static/openapi-spec/projects-v2.yaml b/static/openapi-spec/projects-v2.yaml index 6de642155aa..74a1343152b 100644 --- a/static/openapi-spec/projects-v2.yaml +++ b/static/openapi-spec/projects-v2.yaml @@ -146,7 +146,7 @@ paths: tags: - Projects summary: 'Update a project team member' - description: 'Changes the way the team member interacts with the project. Mendix and project administrators are allowed to change the team member''s project role assignment, regardless of whether the project or the user is active or not. Team members can change the `isPinned` or `isWatching` attributes, but only if they themselves are active members of the platform and their project is active.

Every request must be authenticated by a Personal Access Token containing the scope `mx:app:team:write`' + description: 'Changes the way the team member interacts with the project. Mendix and project administrators are allowed to change the team member's project role assignment, regardless of whether the project or the user is active or not. Team members can change the `isPinned` or `isWatching` attributes, but only if they themselves are active members of the platform and their project is active.

Every request must be authenticated by a Personal Access Token containing the scope `mx:app:team:write`' operationId: patch-project-member parameters: - $ref: '#/components/parameters/app-id'