You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: guides/v2.0/cloud/howtos/patch-magento.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,9 @@ There are two types of patches:
18
18
19
19
*[General patches](#cloud-patch-gen)
20
20
21
-
These patches are provided for all Magento Enterprise Cloud Edition customers in a GitHub repository that's referenced in your `composer.json`. To install general patches, use `composer update`, test your system, and push the patches to the remote server.
21
+
These patches are provided for all Magento Enterprise Cloud Edition customers in a GitHub repository that's referenced in your `composer.json`. We apply these patches automatically during the build phase.
22
+
23
+
To install general patches, use `composer update`, test your system, and push the patches to the remote server.
22
24
23
25
*[Custom patches](#cloud-patch-custom)
24
26
@@ -30,9 +32,8 @@ There are two types of patches:
30
32
Always test a patch your local system, then your [integration environment]({{ page.baseurl }}cloud/discover-arch.html#cloud-arch-int) system (that is, the remote Cloud server). Resolve any issues before you patch either [staging]({{ page.baseurl }}cloud/discover-arch.html#cloud-arch-stage) or [production]({{ page.baseurl }}cloud/discover-arch.html#cloud-arch-prod).
31
33
</div>
32
34
33
-
34
35
## Test general patches {#cloud-patch-gen}
35
-
*General patches* are provided for all Magento Enterprise Cloud Edition customers in a repository referenced in your `composer.json`. To apply these patches, use `composer update`.
36
+
*General patches* are provided for all Magento Enterprise Cloud Edition customers in a repository referenced in your `composer.json`. We apply patches automatically during the build phase when a patch is available. The procedure discussed in this section enables to you test a patch locally anytime you choose.
36
37
37
38
The procedure you use is slightly different, depending on the type of environment: [integration]({{ page.baseurl }}cloud/discover-arch.html#cloud-arch-int), [staging]({{ page.baseurl }}cloud/discover-arch.html#cloud-arch-stage), or [production]({{ page.baseurl }}cloud/discover-arch.html#cloud-arch-prod).
38
39
@@ -79,7 +80,7 @@ After you've successfully tested a patch locally and on your integration environ
0 commit comments