diff --git a/.github/styles/UmbracoDocs/Acronyms.yml b/.github/styles/UmbracoDocs/Acronyms.yml index c6955a12adf..06de01a95d3 100644 --- a/.github/styles/UmbracoDocs/Acronyms.yml +++ b/.github/styles/UmbracoDocs/Acronyms.yml @@ -36,6 +36,7 @@ exceptions: - DELETE # HTTP DELETE method - DHL # International Shipping brand - DIBS # DIBS by Nets + - DLL # Dynamic-Link Library - DNS # Domain Name System - DOM # Document Object Model - DXP # Digital Experience Platform diff --git a/umbraco-cloud/begin-your-cloud-journey/project-features/secrets-management.md b/umbraco-cloud/begin-your-cloud-journey/project-features/secrets-management.md index 82ada5efd1b..8e00722978f 100644 --- a/umbraco-cloud/begin-your-cloud-journey/project-features/secrets-management.md +++ b/umbraco-cloud/begin-your-cloud-journey/project-features/secrets-management.md @@ -45,9 +45,9 @@ If too many secrets are added, or if secret values are too large, your environme It is recommended to: -- Keep secrets small and concise. -- Store only sensitive values as secrets (for example: API keys, connection strings). -- Use `appsettings.json` for general configuration values. +* Keep secrets small and concise. +* Store only sensitive values as secrets (for example: API keys, connection strings). +* Use `appsettings.json` for general configuration values. {% endhint %} To add a secret to your environment, follow these steps: @@ -176,6 +176,4 @@ The following prefixes are allowed for Secrets on Umbraco Cloud: It is also possible to use Secrets to save API keys, Passwords, and ReChaptcha for all our Umbraco products on Umbraco Cloud. -Do you have an existing or new secret that you want to add to a key vault that conflicts with the name restrictions? - -Then please contact Umbraco support, then we will consider it as soon as possible. +Do you have an existing or new secret that you want to add to a key vault that conflicts with the name restrictions? Contact Umbraco Support and it will be considered as soon as possible. diff --git a/umbraco-cloud/begin-your-cloud-journey/project-features/team-members/README.md b/umbraco-cloud/begin-your-cloud-journey/project-features/team-members/README.md index afa95d2f897..7f7ec9d0b0b 100644 --- a/umbraco-cloud/begin-your-cloud-journey/project-features/team-members/README.md +++ b/umbraco-cloud/begin-your-cloud-journey/project-features/team-members/README.md @@ -17,7 +17,7 @@ User Permissions for each environment can be set in the **Edit Team** page avail
* **Admin**: Has access to everything on a project. An admin can delete a project and edit the team. An admin can deploy changes between environments in the Project Portal and has access to git, as well as the Power Tools Kudu. -* **Read**: A team member with Read permissions can only view the project in the portal as well as the backoffices. They are not able to deploy or change anything on the project itself. They can clone down the project, but cannot push changes they have made locally. By default, they are added as an admin in the backoffice so they can make changes in the backoffice. If you want to change this, see Team Member Permissions in the Umbraco Backoffice below. +* **Read**: A team member with Read permissions can only view the project in the portal as well as the backoffice. They are not able to deploy or change anything on the project itself. They can clone down the project, but cannot push changes they have made locally. By default, they are added as an admin in the backoffice so they can make changes in the backoffice. If you want to change this, see Team Member Permissions in the Umbraco Backoffice below. * **Write**: A team member with Write permissions can do everything on a project except delete it and edit the team. A user with Write permissions can deploy changes between environments through the portal. They have access to the git repositories and can push local changes to the environment. * **No Access**: A team member with No access permissions cannot restart the environment, deploy changes between environments, check error logs or log files, or access Kudo in the Project Portal. They can view the project in the portal and access the backoffice. diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/local-to-cloud.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/local-to-cloud.md index 0508e26c52a..ade3ddc15b3 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/local-to-cloud.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/local-to-cloud.md @@ -60,4 +60,4 @@ To validate your local site and ensure compatibility with the updated schema, us Here, you can see the status of ongoing or completed deployment processes. The status will show whether an operation has been triggered and is in progress has been completed, or has failed. -The dashboard will show the status based on the marker files on the disk, eg. `deploy-progress`. From the **Deploy** Dashboard, it is also possible to trigger different processes. +The dashboard will show the status based on the marker files on the disk, for example, `deploy-progress`. From the **Deploy** Dashboard, it is also possible to trigger different processes. diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/README.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/README.md index 8d556f70a8f..162f794f7b7 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/README.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/README.md @@ -2,16 +2,16 @@ When you have content on your Cloud environment and clone down your project to your local machine, you need to restore the content. You will also need to use the restore option when setting up new Cloud environments. -The restore option can be used to always ensure you work with the latest content when delevoping new features. +The restore option can be used to always ensure you work with the latest content when developing new features. ## How to Restore Content You can restore the content in the following ways: -1. [Restore when starting up the project locally](./#restore-when-starting-up-the-project-locally) -2. [Workspace Restore](./#workspace-restore) -3. [Tree Restore](./#tree-restore) -4. [Partial Restore](./#partial-restore) +1. [Restore when starting up the project locally](#restore-when-starting-up-the-project-locally) +2. [Workspace Restore](#workspace-restore) +3. [Tree Restore](#tree-restore) +4. [Partial Restore](#partial-restore) ### Restore when starting up the project locally diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md index b5579e823bd..8b621f93692 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md @@ -26,7 +26,7 @@ Attaching a CI/CD pipeline to a flexible environment is currently not possible. **Centralized Management** -* With Umbraco CI/CD Flow, you can centralize the management of your deployments, tests, and workflows. This makes it easier to monitor, troubleshoot, and optimize your processes, leading to more efficient and reliable deployments. Automating deployment minimizes the risc for human errors that could have a negative effect on the target environment. +* With Umbraco CI/CD Flow, you can centralize the management of your deployments, tests, and workflows. This makes it easier to monitor, troubleshoot, and optimize your processes, leading to more efficient and reliable deployments. Automating deployment minimizes the risk for human errors that could have a negative effect on the target environment. Umbraco CI/CD Flow serves as a bridge between your existing CI/CD pipeline and Umbraco Cloud, enabling a more streamlined and automated deployment process. While it offers a number of advantages, there are also limitations that need to be considered. On the page '[Known Limitations and Considerations](knownlimitationsandconsiderations.md)' you will find a detailed list of the pros and cons of using Umbraco CI/CD Flow. diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/working-locally/legacy-umbraco-visual-studio-setup.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/working-locally/legacy-umbraco-visual-studio-setup.md index f1b8d53bb7e..7ec2631786f 100644 --- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/working-locally/legacy-umbraco-visual-studio-setup.md +++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/working-locally/legacy-umbraco-visual-studio-setup.md @@ -145,7 +145,7 @@ To use ModelsBuilder with IntelliSense in Visual Studio, you'll need to make som This will make the models of your Document Types available with IntelliSense in Visual Studio. [You can read more about configuring ModelsBuilder here](https://docs.umbraco.com/umbraco-cms/reference/templating/modelsbuilder). {% hint style="info" %} -Are using the [Visual Studio Extension for ModelsBuilder](https://marketplace.visualstudio.com/items?itemName=ZpqrtBnk.UmbracoModelsBuilderExtension\&ssr=false) and getting the error message Unauthorized when generating models? You'll need to use or create a backoffice user in your local installation. You then need to supply the credentials for this user in the Visual Studio options. This is necessary because the extension is not able to authenticate against Umbraco Id. +Are using the [Visual Studio Extension for ModelsBuilder](https://marketplace.visualstudio.com/items?itemName=ZpqrtBnk.UmbracoModelsBuilderExtension\&ssr=false) and getting the error message Unauthorized when generating models? You'll need to use or create a backoffice user in your local installation. You then need to supply the credentials for this user in the Visual Studio options. This is necessary because the extension is not able to authenticate against Umbraco ID. {% endhint %} ### Using Umbraco namespaces in your `*.Core` project diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md index ce257c458e9..10fc5ab275a 100644 --- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md +++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md @@ -90,7 +90,7 @@ When an upload fails, you can click the triangle icon to view more details about | ------------------------- | -------------------------------------------- | | ImportBackupAborted | User aborted the upload. | | ImportBackupFailedUnknown | An unknown error occurred during the upload. | -| ImportBackupFailed | Upoload took too long. | +| ImportBackupFailed | Upload took too long. | ## Restore Database diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/cloud-database/README.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/cloud-database/README.md index 7bf9b581c2e..1abb80f1a05 100644 --- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/cloud-database/README.md +++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/cloud-database/README.md @@ -81,6 +81,6 @@ and in one of these folders for IIS Express: If you're using Visual Studio 2015+ check this path: `$(solutionDir)\.vs\config\applicationhost.config` -In Visual Studio 2015+ you can also configure which `applicationhost.config` file is used by altering the `true|false` setting in the project file (eg: `MyProject.csproj`). Source: Microsoft Developer Network (MSDN) forum. +In Visual Studio 2015+ you can also configure which `applicationhost.config` file is used by altering the `true|false` setting in the project file (for example, `MyProject.csproj`). Source: Microsoft Developer Network (MSDN) forum. Now that you are all set and ready you can continue to work with your [database locally](local-database.md). diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md index 499b31ce16b..729e82bbcaf 100644 --- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md +++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md @@ -32,7 +32,7 @@ You can find and manage the value of the `DOTNET_ENVIRONMENT` environment variab Create the files in your local project clone to ensure it's added to the repository. -When the file is deployed to the Live environment, the transforms will be applied to the `appSettings.json` file in the `Root` of your project. In the case that you have mutliple mainline environments, the `appSettings.Live.json` will **only** transform the `appSettings.json` on the Live environment. +When the file is deployed to the Live environment, the transforms will be applied to the `appSettings.json` file in the `Root` of your project. In the case that you have multiple mainline environments, the `appSettings.Live.json` will **only** transform the `appSettings.json` on the Live environment. {% hint style="info" %} If you don't have a web.config you will need to create one locally as well. diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/README.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/README.md index 862d0f5e809..dab86b21d36 100644 --- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/README.md +++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/README.md @@ -131,11 +131,11 @@ There is no vulnerable data in this cookie and manipulating or stealing this coo In the future, the cookie will be set to `HttpOnly` on Umbraco Cloud to conform to best practices. This does not mean that there's anything wrong with the current way it is set. -For more information see [the related GitHub issue](https://github.com/Azure/app-service-announcements/issues/12). +For more information see the [related GitHub issue](https://github.com/Azure/app-service-announcements/issues/12). ## Deny specific IPs from accessing your website -You can block people and bots(like a malicious scanning bot) from accessing your website by adding their IP addresses to a deny-list. +You can block people and bots (like a malicious scanning bot) from accessing your website by adding their IP addresses to a deny-list. The following rule can be added to your web.config file in the `system.webServer/rewrite/rules/` section. diff --git a/umbraco-cloud/expand-your-projects-capabilities/cloud-extensions/umbraco-forms-on-cloud.md b/umbraco-cloud/expand-your-projects-capabilities/cloud-extensions/umbraco-forms-on-cloud.md index 019453208e8..12d368b38fa 100644 --- a/umbraco-cloud/expand-your-projects-capabilities/cloud-extensions/umbraco-forms-on-cloud.md +++ b/umbraco-cloud/expand-your-projects-capabilities/cloud-extensions/umbraco-forms-on-cloud.md @@ -32,7 +32,7 @@ Umbraco Forms is part of the [auto-upgrades on Umbraco Cloud](../../optimize-and To avoid having the auto-upgrades overwrite any of your custom settings, we strongly encourage that you use [config transforms](../../build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md) when you need custom configuration. Additionally, use [Themes](https://docs.umbraco.com/umbraco-forms/developer/themes) when you need to customize your forms. -Whenever a new minor version of Umbraco Forms is ready, eg. 10.x or 11.x, you will get the option to apply the upgrade to your project. When your project is eligible to receive the new version, you will see an "_Upgrade available!_" label on your left-most environment. +When a new minor version of Umbraco Forms, like 10.x or 11.x, is available, you'll have the option to upgrade your project. When your project is eligible to receive the new version, you will see an "_Upgrade available!_" label on your left-most environment. ### Version-specific changes diff --git a/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md b/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md index 2dccca56c18..2c438974cea 100644 --- a/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md +++ b/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md @@ -1003,7 +1003,7 @@ Other reasons for missing the upgrade: * Active deployments during the upgrade attempt. * Environments running different minor versions, such as one environment on 15.0.x and another on 15.1.x. -For more details, see the [Upgrades](../../optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/#the-process-of-auto-upgrading-a-umbraco-cloud-project) article. +For more details, see the [Upgrades](../../optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/README.md#the-process-of-auto-upgrading-a-umbraco-cloud-project) article. ### Do pending commits between environments derail the upgrade process? @@ -1063,7 +1063,7 @@ By default, Umbraco Cloud supports HTTP/2. No, this is not a security risk. The ARRAffinity cookie is set by the load balancer (LB) to track which server the site is on. It is a built-in feature of Azure App Service and is only useful when scaling to multiple servers. Since Umbraco Cloud does not scale sites across multiple servers, this cookie remains unused. -Learn more in our [Security](../../build-and-customize-your-solution/set-up-your-project/security/#cookies-and-security) article. +Learn more in our [Security](../../build-and-customize-your-solution/set-up-your-project/security/README.md#cookies-and-security) article. ### Can wildcard, EV, DV, or OV certificates be used on Umbraco Cloud? @@ -1077,7 +1077,7 @@ This warning appears when domain bindings are not set up correctly. Check bindin Yes. IP filtering can be added to control access. However, Umbraco Deploy must still communicate between environments, and the site should remain accessible locally. -Learn more and how to set it up in the [Security](../../build-and-customize-your-solution/set-up-your-project/security/#restrict-backoffice-access-using-ip-filtering) article. +Learn more and how to set it up in the [Security](../../build-and-customize-your-solution/set-up-your-project/security/README.md#deny-specific-ips-from-accessing-your-website) article. ### Does Umbraco Cloud use Transparent Data Encryption (TDE) for databases? @@ -1181,7 +1181,7 @@ Yes, projects created in the EU region can be moved to another region. For more You can choose a region from the **Region** drop-down list when creating a new project. -### Can a Baseline master project be in one region and a child project in another? +### Can a Baseline `master` project be in one region and a child project in another? No. Baseline projects must remain within the same region. diff --git a/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/umbraco-cloud-plans.md b/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/umbraco-cloud-plans.md index 92e45d83c61..f666b80ec42 100644 --- a/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/umbraco-cloud-plans.md +++ b/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/umbraco-cloud-plans.md @@ -4,7 +4,7 @@ description: Overview of Umbraco Cloud plans, resource quotas, and infrastructur # Plans -Umbraco Cloud plans - Starter, Standard, and Professional - run on on shared infrastructure, referred to as pools. To ensure consistent performance and prevent resource exhaustion within a pool, each website is assigned a resource quota based on its plan. Resource usage is continuously monitored to maintain stability across all sites. +Umbraco Cloud plans - Starter, Standard, and Professional - run on shared infrastructure, referred to as pools. To ensure consistent performance and prevent resource exhaustion within a pool, each website is assigned a resource quota based on its plan. Resource usage is continuously monitored to maintain stability across all sites. The shared resources used by Umbraco Cloud websites include: diff --git a/umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md b/umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md index 3f4cf28f581..88e6955e6d7 100644 --- a/umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md +++ b/umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md @@ -44,10 +44,10 @@ Umbraco Cloud will provide two DNS records: | Record Type | Name | Value/Description | |-------------|--------------------------------------|-----------------------------------------------------------------------------------------| | TXT | `_cf-custom-hostname.\` | Provided by Umbraco Cloud | -| CNAME | `_acme-challenge.\` | Points to a domain under Umbraco's control (e.g., \.xxxx.dcv.cloudflare.com) | +| CNAME | `_acme-challenge.\` | Points to a domain under Umbraco's control (for example, `\.xxxx.dcv.cloudflare.com`) | {% hint style="info" %} -DNS propagation times can vary. Changes may take a while to become active globally. Tools like https://www.nslookup.io/ can help verify that your records are live. +DNS propagation times can vary. Changes may take a while to become active globally. Tools like `https://www.nslookup.io/` can help verify that your records are live. {% endhint %} ### 3. Check Validation Status @@ -82,7 +82,7 @@ In a proxy case, you'll need to ensure that the URI `http://{custom-hostname}/.w ## Custom Certificate -If you plan to use a [custom certificate](security-certificates), the Hostname Pre-Validation method can be used to prove ownership of the hostname. This is done before binding the custom certificate. +If you plan to use a [custom certificate](security-certificates.md), the Hostname Pre-Validation method can be used to prove ownership of the hostname. This is done before binding the custom certificate. You can do this by following these steps: diff --git a/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/README.md b/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/README.md index 58dd7327499..8a1f27effb0 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/README.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/README.md @@ -1,6 +1,6 @@ # Hotfixes -When managing an Umbraco Cloud project with multiple environments, you might need to push a hotfix to your Live environment. There might be a possiblity that you have pending changes in other environments that are not ready for deployment. +When managing an Umbraco Cloud project with multiple environments, you might need to push a hotfix to your Live environment. There might be a possibility that you have pending changes in other environments that are not ready for deployment. ## Scenario @@ -18,8 +18,8 @@ Following Umbraco Cloud's workflow, you should never make changes directly to th It is possible to apply specific changes to your Live environment without breaking Umbraco Cloud workflow. Here are two approaches: -1. [Deploy hotfix with Git branching](./#deploy-hotfix-with-git-branching) -2. [Move files manually](./#move-files-manually) +1. [Deploy hotfix with Git branching](#deploy-hotfix-with-git-branching) +2. [Move files manually](#move-files-manually) ## [Deploy hotfix with Git branching](using-git.md) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/using-git.md b/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/using-git.md index 944b93fb222..53e57ab6f8a 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/using-git.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/using-git.md @@ -57,8 +57,8 @@ Before you push the newly created branch to Umbraco Cloud we need to change the ![Add Live as remote](images/live-remote.png) 3. You will be prompted to authenticate - use your Umbraco Cloud credentials. 4. You will see that the history from the Live repository is visible in the Git history. -5. Next step; hit **Push**. -6. Choose to push to the newly added remote, and write **master** to make sure you are pushing to the master branch on the Live environment. +5. Click **Push**. +6. Choose to push to the newly added remote, and write `master` to make sure you are pushing to the master branch on the Live environment. ![Choose remote](images/choose-remote.png) 7. Hit **Submit** and the push will start. diff --git a/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/README.md b/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/README.md index 7e3d03cda39..ab31a17ca44 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/README.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/README.md @@ -49,7 +49,7 @@ This describes how a Umbraco Cloud project is auto-upgraded: * The payload is a set of files (such as DLLs, and other ASP.NET website files) * The upgrader will verify that the home page of all the environments in the mainline environment is healthy, meaning they don’t return an HTTP status error. If all environments are ok, it will proceed. * The upgrader will take a snapshot of the left-most environments home page including its HTTP status code result and its HTML contents. -* The payload is deployed to the left-most environments Git repository and committed with a tag for the product version being updated. This new Git repository commit will replace the Umbraco product assembly (DLL) files along with other product files such as files located in /umbraco, /umbraco\_client folders +* The payload is deployed to the left-most environments Git repository and committed with a tag for the product version being updated. This new Git repository commit will replace the Umbraco product assembly (DLL) files along with other product files such as files located in `/umbraco`, `/umbraco_client` folders * The normal Umbraco Cloud deployment process is invoked and the repository files are deployed to the website * The upgrader will automatically ensure the web.config version and the database version are updated so that the Installer/upgrade page is not shown * The upgrader will verify that the new HTTP status code returned from the left-most environments home page is OK and will verify that the HTML contents of the home page match that of the snapshot originally taken. diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/availability-performance.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/availability-performance.md index 4f96d0c83a7..68dd9f1c9f5 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/availability-performance.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/availability-performance.md @@ -76,7 +76,7 @@ The statistics panel shows the average, maximum, and minimum response for the sh #### CPU Usage -The chart depicts the CPU time consumed by the application in the selected time range with time periods equalling the selected granularity. +The chart depicts the CPU time consumed by the application in the selected time range with time periods equaling the selected granularity. ![Cpu usage](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/AP-3-CpuUsage2.png) @@ -93,7 +93,7 @@ Cloud projects on dedicated options (or a shared plan with another granularity t #### Memory Usage -The chart shows the memory usage in private bytes consumed by the application in the selected time range with time periods equalling the selected granularity. +The chart shows the memory usage in private bytes consumed by the application in the selected time range with time periods equaling the selected granularity. ![Memory usage](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/AP-4-MemoryUsage.png) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts/README.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts/README.md index ee97d6955d7..7566df9bb23 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts/README.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts/README.md @@ -1,12 +1,12 @@ # Baseline Merge Conflicts -Here we outline how to manually resolve a merge conflict after having updated the children for a Baseline project. +This section outlines how to manually resolve a merge conflict after having updated the children for a Baseline project. -On a Baseline project you can click to _“Manage updates here”_, which enables you to push updates to your child projects from the Live environment of the Baseline project. +On a Baseline project, click _Manage updates here_. This enables you to push updates to your child projects from the Live environment of the Baseline project. ![Upgrades Baseline children](images/manage-baseline-children.gif) -Select the child projects you want to upgrade, and click **Update selected children**. The overview will then change to show the progress and status for updating the various child projects. +Select the child projects you want to upgrade, and click **Update selected children**. The overview will then change to show the progress and status for updating the different child projects. The outcome of the update will result in one of three statuses: @@ -14,27 +14,27 @@ The outcome of the update will result in one of three statuses: * Error while updating from upstream * Encountered a merge conflict so abandoning update -A merge conflict is something you currently need to handle manually in order to push future updates to the child project, which encountered a merge conflict upon updating. +A merge conflict needs to be handled manually to push future updates to the child project, which encountered a merge conflict upon updating. ![environment](images/mergeconflict.jpg) ## Resolving merge conflicts -**Note:** Since the following documentation was outlined we've made quite a few improvements to the Baseline workflow. For the most part this documentation is still relevant and we are working on getting them updated with the latest details. +**Note:** Since the following documentation was outlined there have been a few improvements to the Baseline workflow. For the most part this documentation is still relevant and we are working on getting them updated with the latest details. -In order to resolve the conflict you need to go to the **child site** open up the SCM / Kudu site for the development environment. Click the “\[link]” (see screenshot above) for the project (see screenshot above) and find clone url for the development site, which is similar to this: `https://dev-my-website-alias.scm.umbraco.io/c565ead8-7a27-4696-9ab4-dad7eba2cd2c.git` and remove everything after the last slash, so you have a url that looks like this: `https://dev-my-website-alias.scm.umbraco.io` +To resolve the conflict you need to go to the **child site** open up the Source Control Management (SCM)/Kudu site for the development environment. Click the “[link]” for the project (see screenshot above) and find clone URL for the development site, similar to `https://dev-my-website-alias.scm.umbraco.io/c565ead8-7a27-4696-9ab4-dad7eba2cd2c.git`. Remove everything after the last slash, so you have a URL that looks like `https://dev-my-website-alias.scm.umbraco.io`. ![environment](images/getcloneurl.jpg) -You will be prompted to login to the SCM / Kudu site - use the credentials you normally use to login to the Umbraco Cloud portal. Now click “Debug console” from the top menu and select “CMD”. This will take you to a command line interface from where you need to navigate to the repository folder: site / repository +You will be prompted to login to the SCM/Kudu site - use the credentials you normally use to login to the Umbraco Cloud portal. Now click “Debug console” from the top menu and select “CMD”. This will take you to a command line interface from where you need to navigate to the repository folder: site / repository ![environment](images/image03.png) -From here you need to merge the branch (upstream/master), which contains the updates which were fetched from the Baseline project. In the console enter: `git merge upstream/master` +From here you need to merge the `upstream/master` branch, which contains the updates which were fetched from the Baseline project. In the console enter: `git merge upstream/master` This will result in an output showing the files, which contains conflicts that you need to resolve in order to fully merge the two branches: -``` +```cs Auto-merging data/Revision/properties/77279e39-ed1f-428a-ad7e-258db5f9e6ee.courier CONFLICT (content): Merge conflict in data/Revision/properties/77279e39-ed1f-428a-ad7e-258db5f9e6ee.courier Auto-merging data/Revision/documents/77279e39-ed1f-428a-ad7e-258db5f9e6ee.courier @@ -42,26 +42,26 @@ CONFLICT (content): Merge conflict in data/Revision/documents/77279e39-ed1f-428a Automatic merge failed; fix conflicts and then commit the result. ``` -In the above output two files are listed and we want to pick the ones that comes from the current project (the child) - in other words we want to keep our files, as these are content changes. We use the following commands to achieve that: +In the above output, two files are listed. Pick the ones that comes from the current project (the child). In other words, keep our files, as these are content changes. Use the following commands to achieve that: -``` +```cs git checkout --ours data/Revision/properties/77279e39-ed1f-428a-ad7e-258db5f9e6ee.courier git checkout --ours data/Revision/documents/77279e39-ed1f-428a-ad7e-258db5f9e6ee.courier ``` -_Note_: If you wanted to select the files from the Baseline project instead of the ones from the current project, you should write “--theirs” instead of “--ours” in the command from above. “Ours” corresponds to the current project (the development site) and “Theirs” corresponds to the Baseline project. +_Note_: To select the files from the Baseline project instead of the ones from the current project, use “--theirs” instead of “--ours” in the command. “Ours” corresponds to the current project (the development site) and “Theirs” corresponds to the Baseline project. Now you need to add the (modified) files to Git and finally commit the changes using the following commands: -``` +```cs git add . git commit -m “Resolving merge conflicts” ``` -The merge conflict has now been resolved, and you can update your local repository with the latest changes by pulling from the development site. Please note that the changes from the commit haven’t been deployed to the website yet, as we have only applied the changes to the Git repository. In order to deploy the recent changes to the website you can push your local changes to the development site or you can use the Kudu api to trigger a deployment. You can use the following command from the Kudu Debug Console to deploy the latest changes: +The merge conflict has now been resolved, and you can update your local repository with the latest changes by pulling from the development site. The changes from the commit haven’t been deployed to the website yet, as we have only applied the changes to the Git repository. To deploy the recent changes to the website, push your local changes to the development site or use the Kudu API to trigger a deployment. You can use the following command from the Kudu Debug Console to deploy the latest changes: -``` +```cs curl https://dev-my-website-alias.scm.s1.umbraco.io/api/deployments -X PUT -H "Content-Type: Application/json" --data "{ }" --user yourusername:password ``` diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/cloud-errors.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/cloud-errors.md index c23fc3a7b90..05e9b58607d 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/cloud-errors.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/cloud-errors.md @@ -10,21 +10,15 @@ Each error code is accompanied by a clear description of the issue it represents ### Job Monitoring and Execution Errors - -
Error nameDescriptionExtended Explanation
MoveWebsiteJobMonitorFailedThe component orchestrating the job of moving the website to new hardware failed to get the latest status. An internal error causes this and can safely be retried.This error indicates a failure in retrieving the latest status of the website migration job due to an internal issue. Retry the operation as it may resolve with subsequent attempts.
MoveWebsiteJobTimedOutThe component orchestrating the job for moving the website to new hardware timed out. This error is typically caused by the repository folder being too large. Please review your repository and try again.This error occurs when the job orchestrating the website migration times out due to large repository sizes. Review repository size, optimize content, and retry the migration.
MoveWebsiteJobFailedToStartThe component orchestrating the job of moving the website to new hardware failed to start. An internal error causes this and can safely be retried.This error indicates a failure in starting the job orchestrating the website migration due to an internal issue. Retry the operation as it may resolve with subsequent attempts.
MoveWebsiteJobFailedUnhandledErrorThe component orchestrating the job of moving the website to new hardware failed with an unhandled error. An internal error causes this and can safely be retried.This error indicates a failure in the job orchestrating the website migration due to an unexpected and unhandled error. Retry the operation as it may resolve with subsequent attempts.
### Infrastructure and Configuration Errors - - -
Error nameDescriptionExtended Explanation
MoveWebsiteFailedUnableToCreateAppServiceWe were unable to allocate new hardware for the requests. An internal error causes this and can safely be retried.This error occurs when the system fails to allocate new hardware resources for website migration due to internal issues. Retry the operation as it may resolve with subsequent attempts.
MoveWebsiteFailedUnableToAttachSecretKeyStoreWe were unable to reliably connect the project's secret key store to the new infrastructure. An internal error causes this and can safely be retried.This error occurs when the system fails to establish a reliable connection between the project's secret key store and the new infrastructure during migration. Retry the operation as it may resolve with subsequent attempts.
MoveWebsiteFailedUnableToFetchDeploymentConfigurationWe are unable to fetch the deployment configuration from our hosting provider.This error occurs when the system cannot retrieve the deployment configuration required for migration from the hosting provider. Verify credentials, permissions, or connectivity settings and retry the operation.
UnhandledExceptionWhileExecutingConfigurationStepWhile updating relations between your environments, we experienced an unhandled exception. An internal error causes this and can safely be retried.This error indicates an unhandled exception occurred during updates between environments, suggesting an internal issue. Retry the operation as it may resolve with subsequent attempts.
CopySharedAppSettingsFailedAn unexpected error occurred while trying to copy shared secrets from the source environment to the new environment. Please try again, and if the problem persists, please reach out to support.This error indicates a failure while copying shared application settings or secrets from one environment to another during migration. Retry the operation and contact support if the issue persists.
CopySharedAppSettingsFailedUnhandledExceptionAn unexpected error occurred while trying to copy shared secrets from the source environment to the new environment. Please try again, and if the problem persists, please reach out to support.Similar to the previous error, indicating an unexpected and unhandled exception during the process of copying shared secrets. Retry the operation and contact support if the issue persists.
CopySharedAppSettingsFailedTimeoutExceededThe process of copying shared secrets from the source environment to the new environment took longer than expected. Please try again, and if the problem persists, please reach out to support.This error occurs when the time taken to transfer shared secrets exceeds the expected duration. Retry the operation and contact support if the issue persists.
InitializingGitRepositoryFailedAn error occurred while trying to configure new hardware. Please try again, and if the problem persists, please reach out to support.This error indicates a failure during the initialization of a Git repository on new hardware. Retry the operation and contact support if the issue persists.
UpdateRemoteFailedWe failed to update the Git remotes to adjacent environments. Please try again, and if the problem persists, please reach out to support.This error occurs when the system encounters a problem while updating Git remote configurations between environments. Retry the operation and contact support if the issue persists.
UpdateDeployConfigFailedWe failed to update the deploy configuration on your website. Please try again, and if the problem persists, please reach out to support.This error indicates a failure to update deployment configuration settings on the website. Retry the operation and contact support if the issue persists.
FetchFromRemoteFailedWe failed to fetch changes from an upstream environment. This is most likely caused by the source repository having lots of changes.This error occurs when the system encounters difficulties fetching changes from a remote repository due to a large volume of changes. Retry the operation and review repository settings.
MergeFromRemoteFailedWe failed to merge changes from an upstream environment. This is most likely caused by the two environments having Git conflicts. Please read Umbraco Cloud Git Conflict Resolution on how to resolve Git conflicts on Umbraco Cloud.This error occurs when merging changes from a remote environment fails due to Git conflicts. Follow the documentation for resolving Git conflicts specific to Umbraco Cloud environments.
SetRemoteAsTrackingFailedUnhandled error. Please reach out to support.This error suggests an unhandled error occurred while attempting to set a remote repository as tracking for changes. Contact support for assistance in diagnosing and resolving the issue.
BuildAndDeployFailedUnhandledErrorAn unhandled exception happened while trying to build and deploy your cloud repository to the website. Please review the Kudu logs and try again.This error indicates an unexpected and unhandled exception occurred during the build and deployment process of the website's cloud repository. Review Kudu logs for detailed error messages and retry the operation.
BuildAndDeployFailedAn exception happened while trying to build and deploy your cloud repository to the website. Please review the Kudu logs and try again.This error indicates an exception occurred during the build and deployment process of the website's cloud repository. Review Kudu logs for detailed error messages and retry the operation.
PlaceSqlInitializeFileFailedUnhandled error. Please reach out to support.This error indicates an unhandled error occurred while attempting to place an SQL initialization file. Contact support for assistance in diagnosing and resolving the issue.
PingWebsiteFailedWe were unable to contact your website and get a successful response. This can be caused by multiple issues such as slow boot-up times, invalid redirect rules, or missing configuration.This error occurs when attempts to contact the website fail to retrieve a successful response. Verify website settings, boot-up performance, redirects, and configuration. Retry after addressing identified issues.
DeployExtractionFailedUmbraco Deploy tried to extract changes but encountered a problem. Please review the CMS log files for detailed information.This error occurs when Umbraco Deploy encounters difficulties while extracting changes during deployment. Review CMS log files for detailed error messages and take corrective actions as necessary.
+
Error nameDescriptionExtended Explanation
MoveWebsiteFailedUnableToCreateAppServiceWe were unable to allocate new hardware for the requests. An internal error causes this and can safely be retried.This error occurs when the system fails to allocate new hardware resources for website migration due to internal issues. Retry the operation as it may resolve with subsequent attempts.
MoveWebsiteFailedUnableToAttachSecretKeyStoreWe were unable to reliably connect the project's secret key store to the new infrastructure. An internal error causes this and can safely be retried.This error occurs when the system fails to establish a reliable connection between the project's secret key store and the new infrastructure during migration. Retry the operation as it may resolve with subsequent attempts.
MoveWebsiteFailedUnableToFetchDeploymentConfigurationWe are unable to fetch the deployment configuration from our hosting provider.This error occurs when the system cannot retrieve the deployment configuration required for migration from the hosting provider. Verify credentials, permissions, or connectivity settings and retry the operation.
UnhandledExceptionWhileExecutingConfigurationStepWhile updating relations between your environments, we experienced an unhandled exception. An internal error causes this and can safely be retried.This error indicates an unhandled exception occurred during updates between environments, suggesting an internal issue. Retry the operation as it may resolve with subsequent attempts.
CopySharedAppSettingsFailedAn unexpected error occurred while trying to copy shared secrets from the source environment to the new environment. Please try again, and if the problem persists, please reach out to support.This error indicates a failure while copying shared application settings or secrets from one environment to another during migration. Retry the operation and contact support if the issue persists.
CopySharedAppSettingsFailedUnhandledExceptionAn unexpected error occurred while trying to copy shared secrets from the source environment to the new environment. Please try again, and if the problem persists, please reach out to support.Similar to the previous error, indicating an unexpected and unhandled exception during the process of copying shared secrets. Retry the operation and contact support if the issue persists.
CopySharedAppSettingsFailedTimeoutExceededThe process of copying shared secrets from the source environment to the new environment took longer than expected. Please try again, and if the problem persists, please reach out to support.This error occurs when the time taken to transfer shared secrets exceeds the expected duration. Retry the operation and contact support if the issue persists.
InitializingGitRepositoryFailedAn error occurred while trying to configure new hardware. Please try again, and if the problem persists, please reach out to support.This error indicates a failure during the initialization of a Git repository on new hardware. Retry the operation and contact support if the issue persists.
UpdateRemoteFailedWe failed to update the Git remotes to adjacent environments. Please try again, and if the problem persists, please reach out to support.This error occurs when the system encounters a problem while updating Git remote configurations between environments. Retry the operation and contact support if the issue persists.
UpdateDeployConfigFailedWe failed to update the deploy configuration on your website. Please try again, and if the problem persists, please reach out to support.This error indicates a failure to update deployment configuration settings on the website. Retry the operation and contact support if the issue persists.
FetchFromRemoteFailedWe failed to fetch changes from an upstream environment. This is most likely caused by the source repository having lots of changes.This error occurs when the system encounters difficulties fetching changes from a remote repository due to a large volume of changes. Retry the operation and review repository settings.
MergeFromRemoteFailedWe failed to merge changes from an upstream environment. This is most likely caused by the two environments having Git conflicts. Please read Umbraco Cloud Git Conflict Resolution on how to resolve Git conflicts on Umbraco Cloud.This error occurs when merging changes from a remote environment fails due to Git conflicts. Follow the documentation for resolving Git conflicts specific to Umbraco Cloud environments.
SetRemoteAsTrackingFailedUnhandled error. Please reach out to support.This error suggests an unhandled error occurred while attempting to set a remote repository as tracking for changes. Contact support for assistance in diagnosing and resolving the issue.
BuildAndDeployFailedUnhandledErrorAn unhandled exception happened while trying to build and deploy your cloud repository to the website. Please review the Kudu logs and try again.This error indicates an unexpected and unhandled exception occurred during the build and deployment process of the website's cloud repository. Review Kudu logs for detailed error messages and retry the operation.
BuildAndDeployFailedAn exception happened while trying to build and deploy your cloud repository to the website. Please review the Kudu logs and try again.This error indicates an exception occurred during the build and deployment process of the website's cloud repository. Review Kudu logs for detailed error messages and retry the operation.
PlaceSqlInitializeFileFailedUnhandled error. Please reach out to support.This error indicates an unhandled error occurred while attempting to place an SQL initialization file. Contact support for assistance in diagnosing and resolving the issue.
PingWebsiteFailedWe were unable to contact your website and get a successful response. This can be caused by multiple issues such as slow boot-up times, invalid redirect rules, or missing configuration.This error occurs when attempts to contact the website fail to retrieve a successful response. Verify website settings, boot-up performance, redirects, and configuration. Retry after addressing identified issues.
DeployExtractionFailedUmbraco Deploy tried to extract changes but encountered a problem. Please review the CMS log files for detailed information.This error occurs when Umbraco Deploy encounters difficulties while extracting changes during deployment. Review CMS log files for detailed error messages and take corrective actions as necessary.
### Website Provisioning Errors - - -
Error nameDescriptionExtended Explanation
CreateAppPlanFailedUnableToStartProvisioningWe tried to provision new infrastructure. Unfortunately, our hosting provider was not able to accommodate the request at that time. Please try again.This error occurs when the hosting provider fails to provision the new infrastructure as requested. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedUnableToScaleToMatchRequirementsWe retrieved an internal error while trying to scale the requested infrastructure. Please try again.This error occurs when scaling infrastructure to meet requirements fails due to an internal error. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedUnableScaleToRequirementTimedOutThe operation to scale infrastructure to your requirements took longer than anticipated. Please try again.This error occurs when the operation to scale infrastructure exceeds the expected time limit. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedScaleOperationTimedOutThe operation to scale infrastructure to your requirements took longer than anticipated. Please try again.Similar to the previous error, indicating the operation to scale infrastructure exceeds the expected time limit. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedUnhandledErrorAn internal error happened while modifying infrastructure. Please try again or reach out to support.This error indicates an internal error occurred while modifying infrastructure settings. Retry the operation after some time or contact support for further assistance.
+
Error nameDescriptionExtended Explanation
CreateAppPlanFailedUnableToStartProvisioningWe tried to provision new infrastructure. Our hosting provider was not able to accommodate the request at that time. Please try again.This error occurs when the hosting provider fails to provision the new infrastructure as requested. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedUnableToScaleToMatchRequirementsWe retrieved an internal error while trying to scale the requested infrastructure. Please try again.This error occurs when scaling infrastructure to meet requirements fails due to an internal error. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedUnableScaleToRequirementTimedOutThe operation to scale infrastructure to your requirements took longer than anticipated. Please try again.This error occurs when the operation to scale infrastructure exceeds the expected time limit. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedScaleOperationTimedOutThe operation to scale infrastructure to your requirements took longer than anticipated. Please try again.Similar to the previous error, indicating the operation to scale infrastructure exceeds the expected time limit. Retry the operation after some time or contact support for further assistance.
CreateAppPlanFailedUnhandledErrorAn internal error happened while modifying infrastructure. Please try again or reach out to support.This error indicates an internal error occurred while modifying infrastructure settings. Retry the operation after some time or contact support for further assistance.
### Environment Creation and Deletion Errors diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/colliding-datatypes.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/colliding-datatypes.md index 1c13b0ebbd6..b7589074352 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/colliding-datatypes.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/colliding-datatypes.md @@ -22,7 +22,7 @@ Open the error message by clicking **More info**. In the case illustrated above, there are four data types and each has two `UDA files`. -What this means is that a file has been generated for each data type on both the Live and the left-most environment. The Umbraco Deploy engine needs to create one instance of each data type but is currently not able to do so, since it doesn't know which files to build the data types based on. +What this means is that a file has been generated for each Data Type on both the Live and the left-most environment. The Umbraco Deploy engine needs to create one instance of each Data Type. Currently, it is not able to do so, since it doesn't know which files to build the data types based on. See the steps below on how to resolve the issue. @@ -38,4 +38,4 @@ See the steps below on how to resolve the issue. When you've followed these steps, go through your left-most environment and make sure everything has been created as expected. -The final step you need to take before your left-most environment is completely in sync with your Live environment is to [restore the content](../../../../build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/). +The final step you need to take before your left-most environment is in sync with your Live environment is to [restore the content](../../../../build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/). diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/duplicate-dictionary-items.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/duplicate-dictionary-items.md index d4e3f5ddf18..d2057266403 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/duplicate-dictionary-items.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/duplicate-dictionary-items.md @@ -4,7 +4,7 @@ Has your Umbraco Cloud project been using Courier in the past and have you been ## Cause -Due to how Umbraco Courier has been handling dictionary items in the past, old sites having used Courier to transfer these - are currently very likely to see errors when trying to use Umbraco Deploy with these items. +Umbraco Courier has previously managed dictionary items in a way that may cause issues. Older sites that used Courier for these transfers are likely to encounter errors when using Umbraco Deploy. Courier handled dictionary items only using their `ItemKey` (alias) and did not take into account that dictionary items also carried a unique identifier. Since this unique identifier was not known or handled by Courier - it would not be carried over to other environments when these dictionary items were deployed. As Courier never cared about or used this unique identifier - everything seemed to be in order most of the time. @@ -48,7 +48,7 @@ You can find more details about UDA files in this article: [Generating UDA files ## Fixing -In order to fix this issue, it is required that all dictionary items are aligned to have the same unique identifier for a specific `ItemKey` across all environments. The easiest way of doing this is to select an environment where you believe all your dictionary items are mostly correct, remove any duplicated items, and then ensure that the changes are pushed to your other environments: +To fix this issue, it is required that all dictionary items are aligned to have the same unique identifier for a specific `ItemKey` across all environments. The easiest way to do this is to select an environment with correct dictionary items. Remove any duplicated items, and then push changes to the other environments: 1. Ensure you do not have any duplicated dictionary items in your UDA files. If you do - these will need to be cleaned up as a first step. 2. Ensure you remove all duplicate entries in the backoffice if any. diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/schema-mismatches.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/schema-mismatches.md index 9ef73fa24d2..a2582b53d37 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/schema-mismatches.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/schema-mismatches.md @@ -22,7 +22,7 @@ To resolve this error, check for pending deployments on the source environments. If there are no pending deployments in your source environment, there are two ways to go about resolving the schema mismatch: -1. Make a minor change to the schema with mismatches in the source environment (in the example above, it would be the **Contact Us** document type). +1. Make a minor change to the schema with mismatches in the source environment (in the example above, it would be the **Contact Us** Document Type). 2. Deploy the change to the next environment. * This will update your schema in the target environment and ensure it is in sync with the source environment. diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/structure-error.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/structure-error.md index 239b448ed0c..094493c0886 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/structure-error.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/structure-error.md @@ -71,7 +71,7 @@ For this example, it’s decided that the Document Type currently used on the Li In order to figure out which of the two colliding `.uda` files are the one for the Document Type being used on the Live environment follow these steps: -1. Connect to the database of the Live environment using the [connect to your cloud database locally tutorial](../../../../build-and-customize-your-solution/set-up-your-project/databases/cloud-database/#connecting-to-your-cloud-database-locally). +1. Connect to the database of the Live environment using the [connect to your cloud database locally tutorial](../../../../build-and-customize-your-solution/set-up-your-project/databases/cloud-database/README.md#connecting-to-your-cloud-database-locally). 2. Run one of the following queries on the database, depending on the type you see the error with * Run the following query, if the error states that the error is a `Collisions for entity type "document-type"`: @@ -116,9 +116,9 @@ We strongly recommend that you resolve this locally since this will ensure that {% endhint %} 1. Clone down the Development environment to your local machine. -2. Run the project locally and verify that you get the same extraction error as on your Cloud environments (_HINT: look for a `deploy-failed` marker in your local `/deploy` folder_). +2. Run the project locally and verify that you get the same extraction error as on your Cloud environments (Look for a `deploy-failed` marker in your local `/deploy` folder). * When you run the project, you should see an error message in the browser once the site starts to build. -3. Remove the wrong `.uda` file (It's the one we did not find in the live environment just before) from the `/deploy/revision` folder - you will not be able to see the Document Type in the backoffice because of the failed extraction. +3. Remove the wrong `.uda` file (It's the one we did not find in the live environment before) from the `/deploy/revision` folder - you will not be able to see the Document Type in the backoffice because of the failed extraction. 4. Open the Umbraco Backoffice and go to Settings -> Deploy to see the Deploy dashboard. 5. Select `Schema deployment from data files` in the dropdown. 6. You will now see a `deploy-complete` marker in your local `/deploy` folder. @@ -139,4 +139,4 @@ When the push from local to the Development environment has been completed, refr Sometimes you might need to run another schema deployment on your Cloud environment after deploying to turn your environment green. To do this, follow the steps described in the [schema deployment guide](../../../../build-and-customize-your-solution/handle-deployments-and-environments/deployment/deploy-dashboard.md). -The final step is to deploy the pending changes from Development to your Live environment, to ensure everything is completely in sync. +The final step is to deploy the pending changes from Development to your Live environment, to ensure everything is in sync. diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md index a8adfe334de..8a02846717a 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md @@ -5,14 +5,14 @@ We have gathered a list of frequently asked questions below that have something ## I’m using BuzzHybrid / DonutCaching / LatestHotStuff / other custom add-ins or I’ve created my own data types - do I need to do anything special? -Probably not! In most cases including the custom files (and configuration) is enough for Umbraco Cloud to understand how to deploy your site. In some cases, namely where you’ve created a data type that serializes data or otherwise stores property data in a non-standard format, you’ll need to also create a corresponding value connector. Fortunately these are created using the samples [here](https://github.com/umbraco/Umbraco.Deploy.ValueConnectors) +Probably not! In most cases including the custom files (and configuration) is enough for Umbraco Cloud to understand how to deploy your site. When you create a Data Type that serializes data or stores property data in a non-standard format, create a corresponding value connector. These are created using the samples mentioned at [Umbraco.Deploy.ValueConnectors](https://github.com/umbraco/Umbraco.Deploy.ValueConnectors) - -## I press the “Deploy to Staging/Live” button, then nothing happens. What’s going on? +## I press the “Deploy to Staging/Live” button, then nothing happens. What’s going on? Umbraco Cloud uses web sockets to communicate between your browser session and the remote environment. For the following scenarios you may find that deployments (and other operations) do not complete successfully. At this time there is not a workaround to this requirement. + * If your connection to the internet doesn’t support web sockets * You are behind a proxy server or firewall that blocks web sockets, or * If the web socket connection is in any other way not supported diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md index 9c1afbe92d2..5ae7aabceb9 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/log-files.md @@ -72,7 +72,7 @@ This will delete 90% of the oldest logs that are unread and leave you with 10% o It is possible to enable IIS Logging on each of your Umbraco Cloud environments. There is a rolling size limit on the log files of 100 MB. This means that once the limit is reached, the oldest log files will be overwritten by new ones. {% hint style="info" %} -Do note that the IIS logging will be automatically turned off after 12 hours. It's not possible to have them enabled for longer at once due to possible performance degradation while the logging is enabled. +The IIS logging will be automatically turned off after 12 hours. It's not possible to have them enabled for longer at once due to possible performance degradation while the logging is enabled. {% endhint %} You can enable the logging from the **Advanced** menu found under _Settings_ in the project overview for the project. The logs will be accessible from KUDU in `C:\home\LogFiles\http`. @@ -84,5 +84,5 @@ Find more information about IIS Logging on [the Official Microsoft Documentation {% hint style="info" %} IIS Logging is only available if your project is on a Professional plan. -See our [Cloud Pricing plans](https://umbraco.com/umbraco-cloud-pricing/) for more details on various tiers. +For more details on the different tiers, see the [Cloud Pricing plans](https://umbraco.com/umbraco-cloud-pricing/). {% endhint %} diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-backoffice.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-backoffice.md index ba793418149..77a1dab2214 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-backoffice.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-backoffice.md @@ -23,18 +23,18 @@ If your issue is not covered above, here are some general guidelines on what you The first thing to ensure is that any schema changes have been pushed through Git or deployed between environments so the environments are in sync. -Another thing to check would be the log files, relevant information can often be found in the [umbracoTraceLogs](log-files.md#umbraco-logs) for both the source and target environments, so make sure to check both. +Another thing to check would be the log files. Relevant information can often be found in the [umbracoTraceLogs](log-files.md#umbraco-logs) for both the source and target environments, so make sure to check both. -If you have issues with new user emails / Umbraco Forms emails not being sent it is likely because your SMTP settings are not being set or configured correctly. Make sure to read the [SMTP Documentation ](../../../build-and-customize-your-solution/set-up-your-project/project-settings/smtp-settings.md)for Umbraco Cloud. +If you have issues with new user emails/Umbraco Forms emails not being sent, check your SMTP settings for correct configuration. Make sure to read the [SMTP Settings](../../../build-and-customize-your-solution/set-up-your-project/project-settings/smtp-settings.md) article. ## If the error is something not loading in the backoffice -This can have many different causes, and as such we don't have specific guides on this, but to narrow it down there are some things you should check: +There can be different causes for this issue, so we don't have specific guides. However, here are some things to check to narrow it down: * Do you have any rewrite rules? Often rewrite rules that are not set up correctly will cause issues with the backoffice, make sure that the following are negated: - * ^/umbraco - * ^/DependencyHandler.axd - * ^/App\_Plugins + * `^/umbraco` + * `^/DependencyHandler.axd` + * `^/App_Plugins` * You can see examples of how to set up rewrites correctly in the [Rewrites on Cloud](../../../go-live/manage-hostnames/rewrites-on-cloud.md) article. * Do you get any errors in your browser console that may help you figure it out? * Do you get any errors in your umbracoTraceLog? diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-frontend.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-frontend.md index 22fbe7881da..3fd74de0dd1 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-frontend.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-frontend.md @@ -16,9 +16,9 @@ A **500 error** will show a generic error message like the one shown above or th A **blank page or a page that is not loading** is likely due to bad rewrite rules ending in a rewrite loop. Make sure you do not rewrite anything on these paths: -* ^/umbraco -* ^/DependencyHandler.axd -* ^/App\_Plugins +* `^/umbraco` +* `^/DependencyHandler.axd` +* `^/App_Plugins` You can see examples of how to set up rewrites correctly in the [Rewrites on Cloud](../../../go-live/manage-hostnames/rewrites-on-cloud.md) article. diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-siteperformance.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-siteperformance.md index 3b056313431..0783adf26d8 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-siteperformance.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/troubleshooting-siteperformance.md @@ -2,7 +2,7 @@ CPU issues can be many different things. Below I will give some advice on narrowing down the issue and trying to find out what is causing the problems. The first thing to do is try to find out when the trouble started. The friendly Umbraco Support will supply you with a graph of your CPU usage for the past 24 hours. Here you will likely notice a spot where it starts going up. -You can get in touch with the friendly support by either sending an email to contact@umbraco.com or by using the chat in either the Backoffice or from umbraco.com. +You can contact Support by sending an email to `contact@umbraco.com` or using the chat option in the Backoffice or on [umbraco.com](https://umbraco.com/). ## Resources that can help you @@ -15,11 +15,11 @@ If you have Google Analytics (GA) set up for your site, then you should check th If you know when your site started having issues, then you should compare that time to your Umbraco log. Often you will find errors that help you narrow it down or other things that could be the cause. If for example, the CPU performance issues started when you are building your search indexes then there is a good chance that the two are related. Be aware that some errors may appear due to maxing out your resources, they may not be related to the cause! {% hint style="info" %} -If you are unsure which log file corresponds to the time, you can get a list of the latest log files in Kudu by going to the logs folder `~/Umbraco/logs`then typing in: +To find the latest log files in Kudu, go to the logs folder `~/Umbraco/logs` and type: `ls -t | head -5` -This will sort the files by last edit time, and only show you the top 5 results. +This will sort the files by last edited time and display only the top 5 results. {% endhint %} ## [Common issues](https://docs.umbraco.com/umbraco-cms/reference/common-pitfalls) @@ -28,15 +28,15 @@ This will sort the files by last edit time, and only show you the top 5 results. ### Excessive indexing -It is not great for performance to have too many custom indexes. Each index adds to the performance requirements, and often the things that you want to achieve can be done in simpler and better performant ways by limiting the number of indexes and instead narrowing your searches. +It is not great for performance to have too many custom indexes. Each index increases performance requirements. Achieving your goals can often be simpler and more efficient by reducing the number of indexes and narrowing your searches instead. ### Accessing the database -Doing operations against your database can become a performance issue if you do it in the wrong way. If you for example get some data from the database in your views, then you may do a database operation for each visitor to that page. Can quickly become a problem. Please be aware that using any Umbraco Service will also include the database, and often the info you need can be retrieved from the cache instead! +Performing operations on your database can lead to performance issues if not done correctly. For instance, if you retrieve data from the database in your views, this could result in a database operation for each visitor to that page. This can quickly become problematic. Using any Umbraco service also involves the database, and often, the information you need can be retrieved from the cache instead. ### Scheduled jobs -Scheduled jobs can be very nice, but you have to think about how often they should run and how taxing they are on your site's performance. If for example you want to rebuild your cache every 5 minutes but it takes 6 minutes to do so you will run into a lot of trouble! +Scheduled jobs are nice, but you have to think about how often they should run and how taxing they are on your site's performance. For example, rebuilding your cache every 5 minutes when it takes 6 minutes can cause significant issues. * [Reference](https://docs.umbraco.com/umbraco-cms/reference/scheduling) diff --git a/umbraco-cloud/release-notes/archive/overview-2022/2022-01-06-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2022/2022-01-06-releasenotes.md index 1e44c4431ad..dbac9856471 100644 --- a/umbraco-cloud/release-notes/archive/overview-2022/2022-01-06-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2022/2022-01-06-releasenotes.md @@ -38,7 +38,7 @@ We have ensured that the potential baselines are loaded much faster to ensure a ### [Blob storage connection information](../../../build-and-customize-your-solution/handle-deployments-and-environments/media/azure-blob-storage/connect-to-azure-storage-explorer.md) -The blob storage connection information for a project was previously displayed only in Kudu which was not convenient to find. A developer should spend as much time as possible developing fantastic solutions and less time in Kudu. Therefore you can copy the connection informantion directly from the portal and post it into Azure Blob Explorer whenever needed. +The blob storage connection information for a project was previously displayed only in Kudu which was not convenient to find. A developer should spend as much time as possible developing fantastic solutions and less time in Kudu. Therefore you can copy the connection information directly from the portal and post it into Azure Blob Explorer whenever needed. ![BlobStorage](https://user-images.githubusercontent.com/93588665/151602205-2784ec6c-1142-4221-9bf4-0ba9727ff8f6.gif) diff --git a/umbraco-cloud/release-notes/archive/overview-2022/2022-02-15-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2022/2022-02-15-releasenotes.md index 823f14146d8..a0bd1a9fefd 100644 --- a/umbraco-cloud/release-notes/archive/overview-2022/2022-02-15-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2022/2022-02-15-releasenotes.md @@ -12,7 +12,7 @@ We recently launched the same details for the pending invites shown on the team Project team members will now see the **actual user group memberships** of the project’s backoffice users. This is an improvement to the previous listing where only the default backoffice user group for each backoffice user was shown. -!\[image] +![image] Shortly we will enable portal users to specify the backoffice user groups that the invitee should have as default. @@ -20,7 +20,7 @@ Doing so will ease the onboarding process of new backoffice users. ### Usage limit warnings -Each project in Umbraco Cloud Portal has a set of **usage limits** depending on which plan the project is on. The usage limits for Cloud and Heartcore projects can be seen [here](https://umbraco.com/umbraco-cloud-pricing/) and [here](https://umbraco.com/umbraco-heartcore-pricing/), respectively. The current usage of a project can be seen on the project usage page, available from the Project Settings menu. +Each project in Umbraco Cloud Portal has a set of **usage limits** depending on which plan the project is on. The usage limits can be seen on the [Umbraco Cloud Pricing](https://umbraco.com/umbraco-cloud-pricing/) and [Umbraco Heartcore Pricing](https://umbraco.com/umbraco-heartcore-pricing/) pages respectively. The current usage of a project can be seen on the project usage page, available from the Project Settings menu. You will now be notified in the portal when either the media storage or bandwidth usage of a project has exceeded the 90%. Initially, you will see a **tag on the project page** if either the bandwidth or the media storage has exceeded 90% of the plan limits. The example below shows a project with both usage limits crossed. diff --git a/umbraco-cloud/release-notes/archive/overview-2022/2022-03-02-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2022/2022-03-02-releasenotes.md index 72d4a6c7be8..7b9501ba331 100644 --- a/umbraco-cloud/release-notes/archive/overview-2022/2022-03-02-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2022/2022-03-02-releasenotes.md @@ -14,7 +14,7 @@ Webhooks for Umbraco Heartcore projects are now fired from either of the two sta ![image](https://user-images.githubusercontent.com/93588665/156560443-93d1a81a-ac7a-460f-b8cc-351409782fe4.png) -These two static outgoing IPs make it possible to allow webhook communication to bypass firewall restrictions for any external services. If you need to use a CIDR (Classless Inter-Domain Routing) Range for the IPs: 20.86.53.156/31. +These two static outgoing IPs make it possible to allow webhook communication to bypass firewall restrictions for any external services. If you need to use a Classless Inter-Domain Routing (CIDR) Range for the IPs: 20.86.53.156/31. ### Bandwidth usage top 10 (Beta) diff --git a/umbraco-cloud/release-notes/archive/overview-2022/2022-08-19-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2022/2022-08-19-releasenotes.md index cdb2e527b3a..43784d1978b 100644 --- a/umbraco-cloud/release-notes/archive/overview-2022/2022-08-19-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2022/2022-08-19-releasenotes.md @@ -14,7 +14,7 @@ You can access Dedicated Resources from the Settings menu on your Cloud project. ![ProjectsDashboard](../../images/DedicatedResourceMvp.gif) -Dedicated Resources is currntly available for projects on **Professional** and **Enterprise** plans. More options will be added later in the year to make the feature available for Starter and Standard plans as well. +Dedicated Resources is currently available for projects on **Professional** and **Enterprise** plans. More options will be added later in the year to make the feature available for Starter and Standard plans as well. ## Projects Dashboard (Beta) diff --git a/umbraco-cloud/release-notes/archive/overview-2022/README.md b/umbraco-cloud/release-notes/archive/overview-2022/README.md index 3e2abe5815d..afc0626fcd0 100644 --- a/umbraco-cloud/release-notes/archive/overview-2022/README.md +++ b/umbraco-cloud/release-notes/archive/overview-2022/README.md @@ -10,7 +10,7 @@ description: >- ### Key Takeaways -* **Secrets Management** - Secure your secrets in Azure key vaults in an intuitive user interface and easy access to secrets during the run-time of your Umbraco solution. +* **Secrets Management** - Secure your secrets in Azure key vaults in an intuitive user interface and access to secrets during the run-time of your Umbraco solution. * **Organization Project view** - You will now see a lot more information for each of your organization projects on the project page under your organization. * **Updated public access page** - We have added the option to specify a name when you choose to specify a new entry to the allowlist for an environment. * **Kudu quick link in Projects Dashboard** - You now have the option to navigate to Kudu for a cloud project environment from the "Projects Dashboard". @@ -73,7 +73,7 @@ description: >- * **Content Comparison** - Explore the new feature in Umbraco Deploy feature that enables you to preview content changes prior to transferring them to another environment. * **Bandwidth Usage Top 10 for resources** - Wondering which resources of your Umbraco Cloud project contributes to the most bandwidth usage? Now you can find the answer in the new bandwidth Top 10 for resources on the project usage page. -## [February 2022](./#february-2022) +## [February 2022](2022-02-15-releasenotes.md) ### Key Takeaways diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-01-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-01-releasenotes.md index f05fd61848b..8f4a548bf2b 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-01-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-01-releasenotes.md @@ -36,7 +36,7 @@ Naming secrets is subject to some restrictions to ensure that reserved words and However, it is now possible to change parameters for namespaces related to adding a Simple Mail Transfer Protocol (SMTP) to the Umbraco CMS, saving the Umbraco Forms API key, or using ReChaptcha for Umbraco Forms. -These namesspaces are: +These namespaces are: * Umbraco:CMS:Global:Smtp * Umbraco:Forms:Security:FormsApiKey diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md index 2e242e3278e..4dd30459008 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md @@ -12,11 +12,11 @@ We're excited to introduce our latest security feature in Umbraco Cloud - _organ With this new feature, you can **enforce MFA for all members in your organization**, ensuring that everyone follows the same security protocols. You can customize the authentication method required for each member, depending on your organization's security policies and preferences. -The organization-enforced method will **override any MFA setting that the member has registred**. And ensure that the user will have to use the specified MFA method when during his login session involving UmbracoID. +The organization-enforced method will **override any MFA setting that the member has registered**. And ensure that the user will have to use the specified MFA method when during his login session involving UmbracoID. ![Cloud-artboard](../../images/MfaEnforcedOrganizationMethod.gif) -This organization-enforced MFA feature is easy to set up and manage and can help you protect your organization's data and resources in Umbraco Cloud. Enforcing MFA on all the members of your organization is a vital step in assuring your cloud projects and backoffices are secured from unauthorized access. +This organization-enforced MFA feature is effective to set up and manage, helping protect your organization's data and resources in Umbraco Cloud. Enforcing MFA on all the members of your organization is a vital step in assuring your cloud projects and backoffice are secured from unauthorized access. ## New Project Creation Flow diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-03-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-03-releasenotes.md index 07f6ccc0a26..e8e5d35df01 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-03-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-03-releasenotes.md @@ -12,13 +12,13 @@ We've expanded the **baseline feature to** include the **East US and South UK re If you have had experience working with Umbraco Cloud baselines, you will know that the basic idea about baselines. You have a project that contains your standard Umbraco packages/components, configured with default Document Types, which can be used as baseline for future projects. When you've made changes to your Baseline project, you can push these changes out to the child projects with a click of a button. -If you primarily have been working with Umbraco Cloud in the US or UK regions and accordingly are not that familiar with the Umbraco Cloud baseline feature you can read more about it at [Umbraco Docs](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines), or see an introduction at the [Umbraco Learning Base](https://www.youtube.com/watch?v=Ci1Hm-bH98Y) on how to work with baseline in Umbraco Cloud. +If you've been using Umbraco Cloud in the US or UK regions and aren't familiar with the baseline feature, see the [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) article. Additionally, you can find an introductory video on how to work with baselines in Umbraco Cloud at the [Umbraco Learning Base](https://www.youtube.com/watch?v=Ci1Hm-bH98Y) channel. ## Simplified Access to Project Team Page As an administrator of your organization in Umbraco Cloud, you now have access to the **Edit Team** page of **Umbraco cloud projects in your organization**. -The project team page can easily be accessed from the overview showing all the organization's projects. The administrator can by clicking the icon listed to the right of the individual project. He will be able to invite users to the project team with a set of permissions and backoffice user group memberships. He can also revoke access to the project of an existing project team member. +The project team page can be accessed from the overview showing all the organization's projects. The administrator can by clicking the icon listed to the right of the individual project. He will be able to invite users to the project team with a set of permissions and backoffice user group memberships. He can also revoke access to the project of an existing project team member. ![OrgAdminEditUserPage](../../images/OrgAdminEditUserPage.gif) @@ -38,8 +38,8 @@ With this new feature, you can track your website's bandwidth usage over time an The newest feature to launch in the new front end stack is “Upgrade project” flow. It replaces the current upgrade plan feature while adding a more modern and visually appealing design. -While you can still change the project plan you’ll also get the opportunity to change to a new dedicated option or go back to a shared resource during the flow. And like the new project creation flow launched in the February update, you will see a summary at the very end before accepting the upgrade. +You can change the project plan and opt for a dedicated option or return to a shared resource during the flow. And like the new project creation flow launched in the February update, you will see a summary at the end before accepting the upgrade. ![UpgradeProject](../../images/UpgradeProject.gif) -With this new flow, you can easily upgrade your existing projects to a new upgrade plan and even a new dedicated plan within only a few minutes. +With this new flow, you can quickly upgrade your existing projects to a new upgrade or dedicated plan in a few minutes. diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-05-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-05-releasenotes.md index 7f4054e1820..c5b26660224 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-05-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-05-releasenotes.md @@ -5,7 +5,7 @@ * **Availability & Performance** - With Umbraco Cloud's user-friendly interface, you will receive a new set of tools to monitor and optimize your cloud projects effectively. * **Specific views for dedicated and shared project plans** - The Availability & Performance feature will show different views for CPU Usage and Memory usage, highlighting a comparison to the plan quota for shared plans. * **What the future will bring to the feature** - More exciting features and enhancements will be added to Availability & Performance in the future. -* **Removal of minify feature in Umbraco Cloud** - The option to activate minification of static ressources for cloud projects in Umbraco Cloud has been removed. +* **Removal of minify feature in Umbraco Cloud** - The option to activate minification of static resources for cloud projects in Umbraco Cloud has been removed. ## Availability & Performance diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-08-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-08-releasenotes.md index 47ae928e203..fbc70b43610 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-08-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-08-releasenotes.md @@ -42,4 +42,4 @@ New users to Umbraco get the option to explore the new trial flow for Umbraco Cl And maybe it is also something for you! Whether you're an experienced developer or new to web development, this enhanced trial flow caters to your needs. Embrace Umbraco Cloud or Umbraco Heartcore with confidence, benefitting from a robust and user-friendly environment. -Experience the upgraded trial flow today at [try.umbraco.com](https://try.umbraco.com/) for Umbraco Cloud projects and [try.umbraco.com/heartcore](https://try.umbraco.com/heartcore) for Heartcore projects. +Try out the enhanced trial experience today for [Umbraco Cloud Projects](https://try.umbraco.com/) and [Umbraco Heartcore](https://try.umbraco.com/heartcore) projects. diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md index 68da86b9f0b..081d7879488 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md @@ -16,8 +16,8 @@ The new "Shared Secrets" panel lets you define secrets that are critical during **The key benefits of shared secrets are:** * **Universal Access**: Shared secrets offer you the convenience of a one-time setup. Once a shared secret is set, it will be seamlessly integrated into existing environments and any new environment you create. -* **Enhanced Security**: Just like environment-specific secrets, shared secrets are securely stored in Azure Key Vault, with end-to-end encryption, ensuring that they are only exposed during runtime. -* **Ideal for Private NuGet Feeds**: If your project uses a private NuGet feed, shared secrets provide an easy way to securely manage feed credentials. This way, you don't have to manually configure each environment, making your DevOps process much smoother. +* **Enhanced Security**: Like environment-specific secrets, shared secrets are securely stored in Azure Key Vault, with end-to-end encryption, ensuring that they are only exposed during runtime. +* **Ideal for Private NuGet Feeds**: If your project uses a private NuGet feed, shared secrets provide a way to securely manage feed credentials. This way, you don't have to manually configure each environment, making your DevOps process much smoother. Besides the new shared secrets, we still have the **Environment Secrets**: For secrets that are specific to individual environments, continue to use the existing "Environment Secrets" panel. These secrets remain locked to the selected environment and won't be accessible by others. diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md index 7060957b625..f93d5120c9c 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md @@ -17,7 +17,7 @@ The basic flow is depicted in the sequence diagram below. Whether you're a CI/CD novice or a seasoned developer, we offer tailored guidance for a frictionless deployment experience. If you're starting from scratch, our thorough documentation outlines how to establish a CI/CD pipeline with popular platforms like Azure DevOps or GitHub Actions. For those with an existing setup, integrate effortlessly with Umbraco Cloud's specialized hosting features. -Our [documentation](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/umbraco-cicd) serves as a roadmap, detailing various routes tailored to your needs. Learn how to invoke the Umbraco Cloud API from within your CI/CD pipeline, explore the specific endpoint details, or discover how to call this endpoint from an already established pipeline. Each path culminates in a seamless, automated deployment experience, empowering you to deploy with confidence. +The [Umbraco CI/CD Flow](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/umbraco-cicd) article serves as a roadmap, detailing different routes tailored to your needs. Learn to invoke the Umbraco Cloud API in your CI/CD pipeline, explore endpoint details, or call the endpoint from an existing pipeline. Each path culminates in a seamless, automated deployment experience, empowering you to deploy with confidence. ## Automatic Upgrades for Minor Versions @@ -29,6 +29,6 @@ For those running existing Cloud projects, you can opt-in to enable Automatic Mi If you're starting a new Cloud project, the feature will be enabled by default, ensuring you're always running on the latest and most secure version across Umbraco CMS, Umbraco Forms, and Umbraco Deploy. -With Automatic Minor Upgrades, you can enjoy several benefits. First, you'll save a significant amount of time, allowing you to focus on more important aspects of your project. Second, you'll have access to the latest features and enhancements across all key components. Lastly, the most recent security patches are applied automatically, giving you peace of mind. +With Automatic Minor Upgrades, you can enjoy different benefits. First, you'll save a significant amount of time, allowing you to focus on more important aspects of your project. Second, you'll have access to the latest features and enhancements across all key components. Lastly, the most recent security patches are applied automatically, giving you peace of mind. For further details, please consult our Upgrading Documentation where you'll find details regarding the upgrade process. Our support team is also on standby to assist with any queries you may have. diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-12-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-12-releasenotes.md index c1fcea1cbe7..6ad3f81fdff 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/2023-12-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-12-releasenotes.md @@ -53,4 +53,4 @@ The initiative also includes optimizing default settings for new projects where After a successful beta phase, the Umbraco CI/CD Flow is now fully operational. This feature, designed to refine and streamline the development process in Umbraco, is now out of beta and available for all users. This full-scale launch of the CI/CD Flow promises to enhance the development experience in Umbraco, offering robust and reliable tools for continuous integration and delivery. -Our [CI/CD documentation](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/umbraco-cicd) serves as a roadmap, detailing various routes tailored to your needs. Learn how to invoke the Umbraco Cloud API from within your CI/CD pipeline, explore the specific endpoint details, or discover how to call this endpoint from an already established pipeline. Each path culminates in a seamless, automated deployment experience, empowering you to deploy with confidence. +The [Umbraco CI/CD Flow](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/umbraco-cicd) article serves as a roadmap, detailing different routes tailored to your needs. Learn to invoke the Umbraco Cloud API in your CI/CD pipeline, explore endpoint details, or call the endpoint from an existing pipeline. Each path culminates in a seamless, automated deployment experience, empowering you to deploy with confidence. diff --git a/umbraco-cloud/release-notes/archive/overview-2023/README.md b/umbraco-cloud/release-notes/archive/overview-2023/README.md index 2a389bd700e..da59a5cf061 100644 --- a/umbraco-cloud/release-notes/archive/overview-2023/README.md +++ b/umbraco-cloud/release-notes/archive/overview-2023/README.md @@ -57,7 +57,7 @@ description: Get an overview of release notes for each month in 2023. #### Key Takeaways -* **Reset Authenticator App settings** - It is now an easy task for your cloud organization administrator to reset your authenticator app settings if you start using a new mobile or want to switch to another authenticator app. +* **Reset Authenticator App settings** - Your cloud organization administrator can reset your authenticator app settings if you start using a new mobile or want to switch to another authenticator app. * **Other Umbraco Cloud updates** - Umbraco Cloud has been updated with a few other features and updates worth mentioning. ### [March 2023](2023-03-releasenotes.md) diff --git a/umbraco-cloud/release-notes/archive/overview-2024/2024-01-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2024/2024-01-releasenotes.md index 466e37598d1..b5639b8bb1f 100644 --- a/umbraco-cloud/release-notes/archive/overview-2024/2024-01-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2024/2024-01-releasenotes.md @@ -3,7 +3,7 @@ ## Key Takeaways * **Self-Service Cipher Suite Management** - Effortlessly manage and disable cipher suites on the Security page for tailored efficient control. -* **Project Invitation Renewal Request** - Easily request a resend of expired Umbraco Cloud project invitations with this new 'Request New Invitation' feature. +* **Project Invitation Renewal Request** - Request a resend of expired Umbraco Cloud project invitations with the 'Request New Invitation' feature. ## [Self-Service Cipher Suite Management](../../../build-and-customize-your-solution/set-up-your-project/security/managing-transport-security.md#cipher-suite-management) @@ -13,7 +13,7 @@ We understand that managing security settings is a critical aspect of any cloud ![Disable Cipher Suites](../../images/DisableCipherSuites.gif) -The interface for this feature has been designed with simplicity in mind. You can now adjust your security settings with just a few clicks, saving you time and effort and allowing you to focus on the more critical aspects of your work. We believe this streamlined approach will significantly enhance your overall efficiency and ease of use. +The interface for this feature has been designed with simplicity in mind. You can adjust your security settings with a few clicks, saving time and effort for you to focus on the critical aspects of your work. This streamlined approach will enhance your overall efficiency and ease of use. ## Project Invitation Renewal Request @@ -23,6 +23,6 @@ When an invitation expires, you'll on the “Pending Invites” page under your ![Request New Project Invite](../../images/ResendProjectInvite.gif) -This new feature aims to significantly reduce any friction caused by expired project invites, ensuring seamless and uninterrupted collaboration across teams and organizations in Umbraco Cloud. +This new feature aims to reduce any friction caused by expired project invites, ensuring seamless and uninterrupted collaboration across teams and organizations in Umbraco Cloud. -This feature is just a glimpse of what's to come. Stay tuned for more updates aimed at enhancing your Umbraco Cloud experience! +This feature is a glimpse of what's to come. Stay tuned for more updates aimed at enhancing your Umbraco Cloud experience! diff --git a/umbraco-cloud/release-notes/archive/overview-2024/2024-02-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2024/2024-02-releasenotes.md index 211551170a1..cec0387dacf 100644 --- a/umbraco-cloud/release-notes/archive/overview-2024/2024-02-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2024/2024-02-releasenotes.md @@ -12,7 +12,7 @@ The "Project History Page," today released as a beta release, provides a detaile ![Project History Page](../../images/ProjectHistory.gif) -Each entry in the overview is interactive, allowing you to click on it for more detailed information. This feature ensures that you have easy access to in-depth details about each event, further enhancing your insight into your project's history and ongoing activities. +Each entry in the overview is interactive, allowing you to click on it for more detailed information. This feature ensures that you have access to in-depth details about each event. It enhances your insight into the project's history and ongoing activities. The overview today concentrates on activities spurred by users and Umbraco Cloud. However, our vision for the future is more expansive. As we diligently work on enhancing and refining this feature, the "Project History Page" is set to evolve into an all-encompassing overview. It will offer an unparalleled glimpse into the entirety of events that have transpired throughout your cloud project's existence. diff --git a/umbraco-cloud/release-notes/archive/overview-2024/2024-03-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2024/2024-03-releasenotes.md index 59ab04af08f..1c45baaae99 100644 --- a/umbraco-cloud/release-notes/archive/overview-2024/2024-03-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2024/2024-03-releasenotes.md @@ -8,12 +8,12 @@ With the introduction of the Point-In-Time Recovery (PITR) feature on the new "Backups" page, managing backups of your cloud projects database has never been more straightforward. This new feature empowers you with the flexibility to export backups of your Umbraco database directly from Azure on your terms. Perfect for those moments right before a significant update, during troubleshooting, or when you need to revert recent changes. -All previous backups are neatly organized for easy access. From this list, you can opt to download the .bacpac file or delete any backup. Accessing the new page requires admin permission on the cloud project. +All previous backups are neatly organized for ease of access. From this list, you can opt to download the .bacpac file or delete any backup. Accessing the new page requires admin permission on the cloud project. ![Backup Database Example](../../images/BackupDbExample.gif) Looking ahead, we're enhancing this feature to include the ability to import and swap database backups, which will add another layer of flexibility to your data management strategy. We're also planning to broaden the backup solution to encompass media files, aiming for a comprehensive approach that ensures every aspect of your project is securely backed up. -So next time you're gearing up for a big change, head over to the "Backups" page, and with just a few clicks, you can secure your project's data. Stay tuned for more updates and enhancements designed to make your experience even better. +So next time you're up for a big change, go to the "Backups" page and with a few clicks, see your project's data. Stay tuned for more updates and enhancements designed to make your experience even better. -You can read more about how to use the feature in the[ Backup documentation.](../../../build-and-customize-your-solution/set-up-your-project/databases/backups.md#backup-on-umbraco-cloud) +You can read more about how to use the feature in the [Backup documentation](../../../build-and-customize-your-solution/set-up-your-project/databases/backups.md#backup-on-umbraco-cloud). diff --git a/umbraco-cloud/release-notes/archive/overview-2024/2024-07-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2024/2024-07-releasenotes.md index 4ccbdc62175..e0e77f4a2db 100644 --- a/umbraco-cloud/release-notes/archive/overview-2024/2024-07-releasenotes.md +++ b/umbraco-cloud/release-notes/archive/overview-2024/2024-07-releasenotes.md @@ -12,8 +12,8 @@ The Sustainability Dashboard is available now to all Umbraco Cloud users. It is ## [Improved error codes and logs](https://docs.umbraco.com/umbraco-cloud/troubleshooting/cloud-errors) -Many operations on Cloud are complex, whether you are pushing Code changes to another environment, upgrading a plan, or adding and removing environments, etc. Most of the time, the operation works as it should, and you can go about your day and continue delivering value to your customers. Sometimes these operations fail for various reasons and require reaching out to support to figure out what is happening and how to get unstuck. With this new addition, we have logs right at your fingertips to help you figure out what went wrong. +Many operations on Cloud are complex, whether you are pushing Code changes to another environment, upgrading a plan, or adding and removing environments, etc. Most of the time, the operation works as it should, and you can go about your day and continue delivering value to your customers. Sometimes these operations fail for different reasons and require reaching out to support to figure out what is happening and how to get unstuck. With this new addition, we have logs right at your fingertips to help you figure out what went wrong. ## Security Issue Fixed in UmbracoID -Thanks to a report from [Joshua Nibbs](https://www.linkedin.com/in/joshua-nibbs/) a high-severity issue has been mitigated, significantly enhancing the security of your projects on Umbraco Cloud. +Thanks to a report from Joshua Nibbs a high-severity issue has been mitigated, enhancing the security of your projects on Umbraco Cloud. diff --git a/umbraco-cloud/release-notes/archive/overview-2024/README.md b/umbraco-cloud/release-notes/archive/overview-2024/README.md index 30422c0b399..7d23c48e53b 100644 --- a/umbraco-cloud/release-notes/archive/overview-2024/README.md +++ b/umbraco-cloud/release-notes/archive/overview-2024/README.md @@ -67,4 +67,4 @@ description: Get an overview of release notes for each month in 2024. #### Key Takeaways * **Self-Service Cipher Suite Management** - Effortlessly manage and disable cipher suites on the Security page for tailored, efficient control. -* **Project Invitation Renewal Request** - Easily request a resend of expired Umbraco Cloud project invitations with this new 'Request New Invitation' feature. +* **Project Invitation Renewal Request** - Request a resend of expired Umbraco Cloud project invitations with this new 'Request New Invitation' feature. diff --git a/umbraco-cloud/release-notes/archive/overview-2024/august-2024.md b/umbraco-cloud/release-notes/archive/overview-2024/august-2024.md index 059def65c20..76b931da894 100644 --- a/umbraco-cloud/release-notes/archive/overview-2024/august-2024.md +++ b/umbraco-cloud/release-notes/archive/overview-2024/august-2024.md @@ -2,7 +2,7 @@ ## [Import Database](../../../build-and-customize-your-solution/set-up-your-project/databases/backups.md#upload-database) -A new level of flexibility has arrived in Umbraco Cloud—Database Import. You can now easily import your database into any environment within your project, whether from an existing site or a local development setup. +A new level of flexibility has arrived in Umbraco Cloud—Database Import. You can now import your database into any environment within your project, whether from an existing site or a local development setup.
Upload database to Umbraco Cloud.

Upload database to Umbraco Cloud.

@@ -22,12 +22,10 @@ The Database Restore feature also allows you to tailor each environment with the ## [Update to availability & Performance](../../../optimize-and-maintain-your-site/monitor-and-troubleshoot/availability-performance.md#platform-and-cms-events) -The Performance and Availability page in Umbraco Cloud now provides even more transparency with the addition of Boot Status insights. You can now easily see whether an environment experienced a **hot** or **cold** boot, giving you a clearer picture of your site’s performance. +The Performance and Availability page in Umbraco Cloud now provides even more transparency with the addition of Boot Status insights. You can now see whether an environment experienced a **hot** or **cold** boot, giving you a clearer picture of your site’s performance.
Hot and cold boot.

Hot and cold boot.

-A **cold** **boot** occurs when the application is starting from scratch, which generally takes a bit longer as all dependencies need to be reloaded. On the other hand, a **hot** **boot** happens when the application is restarted but retains cached data, making the process significantly faster. +A **cold** **boot** occurs when the application is starting from scratch, which generally takes a bit longer as all dependencies need to be reloaded. On the other hand, a **hot** **boot** happens when the application is restarted but retains cached data, making the process faster. This new insight helps you better understand what might be impacting your site's startup times and gives you the ability to optimize accordingly. Whether troubleshooting or wanting to monitor your site's performance more closely, knowing the difference between **hot** and **cold** boots is key to keeping everything running smoothly. - -\