From d81c8f5334975c288cc5c34e2358b96710cbc22b Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 22 Jan 2024 12:51:35 +0100 Subject: [PATCH 1/2] Updated Deploy's troubleshooting page to inclue reference to the import/export feature. --- 10/umbraco-deploy/troubleshooting.md | 12 ++++++++++++ 12/umbraco-deploy/troubleshooting.md | 12 ++++++++++++ 13/umbraco-deploy/troubleshooting.md | 12 ++++++++++++ 3 files changed, 36 insertions(+) diff --git a/10/umbraco-deploy/troubleshooting.md b/10/umbraco-deploy/troubleshooting.md index d991c610eb5..ba228d11bcf 100644 --- a/10/umbraco-deploy/troubleshooting.md +++ b/10/umbraco-deploy/troubleshooting.md @@ -28,6 +28,18 @@ In some cases, a hard limit imposed by the Cloud hosting platforms such as Azure If you find the process slow or reporting a platform timeout, there are a few options you can take. +### Consider partial restore + +If restoring, you can choose to pull down a smaller set of content via the partial restore feature. With this you select an item in the remote environment to restore. You can select to include child items. Any items related to the selected ones, for example via content or media pickers, will also be restored. + +### Consider import/export + +In addition to transfers via the backoffice, content (and schema) can be moved between environments via Deploy's import/export feature. With this a selection of Umbraco data can be exported from one environment to a `.zip` file. That file can then be imported into another environment. + +As this process requires less inter-environment communication, it's possible to transfer much larger amounts of content without running into the hard platform limits. + +[Read more about the import/export feature here](./deployment-workflow/import-export.md). + ### Review timeouts Firstly, you can review and update the [timeout settings available with Deploy](./getting-started/deploy-settings.md#timeout-settings). Increasing these from the default values may help, but won't necessarily resolve all issues. This is because, as noted, some timeouts are fixed values set by the hosting environment. diff --git a/12/umbraco-deploy/troubleshooting.md b/12/umbraco-deploy/troubleshooting.md index 28eecf04730..999f7387f9e 100644 --- a/12/umbraco-deploy/troubleshooting.md +++ b/12/umbraco-deploy/troubleshooting.md @@ -28,6 +28,18 @@ In some cases, a hard limit imposed by the Cloud hosting platforms such as Azure If you find the process slow or reporting a platform timeout, there are a few options you can take. +### Consider partial restore + +If restoring, you can choose to pull down a smaller set of content via the partial restore feature. With this you select an item in the remote environment to restore. You can select to include child items. Any items related to the selected ones, for example via content or media pickers, will also be restored. + +### Consider import/export + +In addition to transfers via the backoffice, content (and schema) can be moved between environments via Deploy's import/export feature. With this a selection of Umbraco data can be exported from one environment to a `.zip` file. That file can then be imported into another environment. + +As this process requires less inter-environment communication, it's possible to transfer much larger amounts of content without running into the hard platform limits. + +[Read more about the import/export feature here](./deployment-workflow/import-export.md). + ### Review timeouts Firstly, you can review and update the [timeout settings available with Deploy](./getting-started/deploy-settings.md#timeout-settings). Increasing these from the default values may help, but won't necessarily resolve all issues. This is because, as noted, some timeouts are fixed values set by the hosting environment. diff --git a/13/umbraco-deploy/troubleshooting.md b/13/umbraco-deploy/troubleshooting.md index 24a12f8a101..983a765d4c3 100644 --- a/13/umbraco-deploy/troubleshooting.md +++ b/13/umbraco-deploy/troubleshooting.md @@ -28,6 +28,18 @@ In some cases, a hard limit imposed by the Cloud hosting platforms such as Azure If you find the process slow or reporting a platform timeout, there are a few options you can take. +### Consider partial restore + +If restoring, you can choose to pull down a smaller set of content via the partial restore feature. With this you select an item in the remote environment to restore. You can select to include child items. Any items related to the selected ones, for example via content or media pickers, will also be restored. + +### Consider import/export + +In addition to transfers via the backoffice, content (and schema) can be moved between environments via Deploy's import/export feature. With this a selection of Umbraco data can be exported from one environment to a `.zip` file. That file can then be imported into another environment. + +As this process requires less inter-environment communication, it's possible to transfer much larger amounts of content without running into the hard platform limits. + +[Read more about the import/export feature here](./deployment-workflow/import-export.md). + ### Review timeouts Firstly, you can review and update the [timeout settings available with Deploy](./getting-started/deploy-settings.md#timeout-settings). Increasing these from the default values may help, but won't necessarily resolve all issues. This is because, as noted, some timeouts are fixed values set by the hosting environment. From b28a4c17172b1dc0df1b0cf7b7cc9851061b5935 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 30 Jan 2024 11:19:30 +0100 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: jonat123 <54025331+jonat123@users.noreply.github.com> --- 10/umbraco-deploy/troubleshooting.md | 2 +- 12/umbraco-deploy/troubleshooting.md | 2 +- 13/umbraco-deploy/troubleshooting.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-deploy/troubleshooting.md b/10/umbraco-deploy/troubleshooting.md index ba228d11bcf..128497aaf6c 100644 --- a/10/umbraco-deploy/troubleshooting.md +++ b/10/umbraco-deploy/troubleshooting.md @@ -34,7 +34,7 @@ If restoring, you can choose to pull down a smaller set of content via the parti ### Consider import/export -In addition to transfers via the backoffice, content (and schema) can be moved between environments via Deploy's import/export feature. With this a selection of Umbraco data can be exported from one environment to a `.zip` file. That file can then be imported into another environment. +In addition to transferring content via the backoffice, it is possible to move both content and schema between environments via Deploy's import/export feature. With this, a selection of Umbraco data can be exported from one environment to a .zip file. That file can then be imported into another environment. As this process requires less inter-environment communication, it's possible to transfer much larger amounts of content without running into the hard platform limits. diff --git a/12/umbraco-deploy/troubleshooting.md b/12/umbraco-deploy/troubleshooting.md index 999f7387f9e..4b805cadfb6 100644 --- a/12/umbraco-deploy/troubleshooting.md +++ b/12/umbraco-deploy/troubleshooting.md @@ -34,7 +34,7 @@ If restoring, you can choose to pull down a smaller set of content via the parti ### Consider import/export -In addition to transfers via the backoffice, content (and schema) can be moved between environments via Deploy's import/export feature. With this a selection of Umbraco data can be exported from one environment to a `.zip` file. That file can then be imported into another environment. +In addition to transferring content via the backoffice, it is possible to move both content and schema between environments via Deploy's import/export feature. With this, a selection of Umbraco data can be exported from one environment to a .zip file. That file can then be imported into another environment. As this process requires less inter-environment communication, it's possible to transfer much larger amounts of content without running into the hard platform limits. diff --git a/13/umbraco-deploy/troubleshooting.md b/13/umbraco-deploy/troubleshooting.md index 983a765d4c3..100ecae7b26 100644 --- a/13/umbraco-deploy/troubleshooting.md +++ b/13/umbraco-deploy/troubleshooting.md @@ -34,7 +34,7 @@ If restoring, you can choose to pull down a smaller set of content via the parti ### Consider import/export -In addition to transfers via the backoffice, content (and schema) can be moved between environments via Deploy's import/export feature. With this a selection of Umbraco data can be exported from one environment to a `.zip` file. That file can then be imported into another environment. +In addition to transferring content via the backoffice, it is possible to move both content and schema between environments via Deploy's import/export feature. With this, a selection of Umbraco data can be exported from one environment to a .zip file. That file can then be imported into another environment. As this process requires less inter-environment communication, it's possible to transfer much larger amounts of content without running into the hard platform limits.