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: src/cloud/architecture/scaled-architecture.md
+8-5
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The scaled architecture is available for {{site.data.var.ece}} accounts with the
12
12
13
13
## Split architecture
14
14
15
-
Historically, the Pro architecture consisted of 3 nodes, each containing a full tech stack. Now, there is a scalable infrastructure that provides a tiered solution with a minimum of 6 nodes: 3 nodes for the core database and other services and 3 nodes for the web server. This split architecture provides the capability to scale tiers independently to achieve an optimal balance of performance. The **core** tier scales vertically (increases in size), and the **web** tier scales horizontally (increases instance count) and vertically (changes instance type and size).
15
+
Historically, the Pro architecture consisted of 3 nodes, each containing a full tech stack. Now, there is a scalable infrastructure that provides a tiered solution with a minimum of 6 nodes: 3 nodes for the core database and other services and 3 nodes for the web server. This split architecture provides the capability to scale tiers independently to achieve an optimal balance of performance. The **core** tier scales vertically (increases in size), and the **web** tier scales horizontally (increases instance count) and vertically (changes instance type and size).
16
16
17
17
Scaling must use the same instance type and size for each node:
18
18
@@ -21,7 +21,7 @@ Scaling must use the same instance type and size for each node:
21
21
22
22
### Core tier scaling
23
23
24
-
There are 3 nodes (core nodes) for the database and included services, such as ElasticSearch, MariaDB, and Redis. When the core tier approaches capacity, the only way to scale is to increase the server size, such as boosting the CPU power and memory. Capacity is limited to the size of the node that is available. Because the database cluster is designed for high availability, you cannot scale horizontally in a reliable way with the technologies used.
24
+
There are 3 nodes (core nodes) for data storage, cache, and services: **ElasticSearch**, **MariaDB**, **Redis**, and more. When the core tier approaches capacity, the only way to scale is to increase the server size, such as boosting the CPU power and memory. Capacity is limited to the size of the node that is available. Because the database cluster is designed for high availability, you cannot scale horizontally in a reliable way with the technologies used.
25
25
26
26
![Core tier scaling]
27
27
@@ -31,11 +31,11 @@ You can further optimize the performance of the core tier by routing traffic bas
31
31
32
32
### Web tier scaling
33
33
34
-
There are 3 nodes (web nodes) for php-fpm processing and web traffic. In addition to vertical scaling by increasing power and memory, the web tier can scale horizontally by adding extra web servers to an existing cluster when constricted at the PHP level.
34
+
There are 3 nodes (web nodes) for processing requests and web traffic: **php-fpm** and **NGINX**. In addition to vertical scaling by increasing power and memory, the web tier can scale horizontally by adding extra web servers to an existing cluster when constricted at the PHP level.
35
35
36
36
![Web tier scaling]
37
37
38
-
This complements the vertical scaling provided by the core tier. As the core tier scales in size and power to accommodate a growing database and increase in service usage, the web tier scales in size and power, and even instances, to accommodate growing process and traffic requirements.
38
+
This complements the vertical scaling provided by the core tier. As the core tier scales in size and power to accommodate a growing database and increase in service usage, the web tier scales in size and power, and even instances, to accommodate an increase in process requests and higher traffic requirements.
39
39
40
40
Consider an example that the web node instance type is _C5.2xlarge with 8 CPU and 16Gb RAM_. The number of requests to the site increased greatly. You can add an additional C5.2xlarge node to handle the increase in php-fpm processes or you can change each instance type to _C5.4xlarge with 16 CPU and 32Gb RAM_. Adding an additional node reduces the risk of insufficient surge capacity.
41
41
@@ -46,7 +46,7 @@ Minimally, Pro projects with the Scaled architecture have 6 nodes available.
46
46
- 3 web nodes c5.2xlarge (8 CPU, 16 Gb RAM)
47
47
- 3 core nodes m5.2xlarge (8 CPU, 32 Gb RAM)
48
48
49
-
Each project is unique, however, and requires performance monitoring to properly analyze resource management. Each account includes the [New Relic Infrastructure service][nri], which automatically connects with the application data and performance analytics to provide dynamic server monitoring. As a resource reaches capacity or a degradation in performance, you can create a request to scale your infrastructure to meet the demand.
49
+
Each project is unique, however, and requires performance monitoring to properly analyze resource management. Each account includes the [New Relic Infrastructure service][nri], which automatically connects with the application data and performance analytics to provide dynamic server monitoring. Specifically, you can use the New Relic service to monitor CPU and RAM utilization to determine which nodes require additional resources. As a resource reaches capacity or you notice a degradation in performance based on the analytics, you can create a request to scale your infrastructure to meet the demand.
Copy file name to clipboardExpand all lines: src/guides/v2.3/frontend-dev-guide/bk-frontend-dev-guide.md
+6-7
Original file line number
Diff line number
Diff line change
@@ -42,9 +42,6 @@ You can apply these levels of customization to your site, where the levels requi
42
42
43
43
This requires PHP programming knowledge in addition to knowledge of all of the preceding areas.
44
44
45
-
{:.bs-callout-info}
46
-
There have been some inquiries about the status of the Visual Design Editor (VDE), which is currently part of the Magento development code base. The VDE enables assigning and unassigning themes, editing theme CSS and JS files, changing page layouts, and managing blocks and their positions on pages in a [WYSIWYG](https://glossary.magento.com/wysiwyg) mode. We'd like to clarify that to meet higher priority objectives, the VDE will _not_ be part of the initial Magento release. Future plans for the VDE will be communicated at a later point in time. You are welcome to continue to provide input on the VDE, but please note that we will not be actively reviewing or actioning these comments in the near term.
47
-
48
45
## Frontend development prerequisites {#fedg-prereqs}
49
46
50
47
To implement what is discussed in this guide, you need a working Magento installation and the following browser versions installed on your device:
@@ -53,12 +50,14 @@ To implement what is discussed in this guide, you need a working Magento install
53
50
54
51
To use this guide, you must be familiar with:
55
52
56
-
* CSS, CSS 3, and LESS
57
-
* HTML and HTML 5
53
+
*[CSS, CSS 3](https://glossary.magento.com/css)
54
+
*[LESS](https://glossary.magento.com/less)
55
+
*[HTML and HTML 5](https://glossary.magento.com/html)
Copy file name to clipboardExpand all lines: src/guides/v2.3/graphql/functional-testing.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Magento provides API functional tests that can verify extension points in GraphQ
9
9
10
10
## Creating a new GraphQL functional test
11
11
12
-
All GraphQL functional tests should inherit from the generic test case `Magento\TestFramework\TestCase\GraphQlAbstract`. It defines the `graphQlQuery()`method, which should be used to perform Web API calls from tests.
12
+
All GraphQL functional tests should be located in the `dev/tests/api-functional/testsuite/Magento/GraphQl/` directory and inherit from the generic test case `Magento\TestFramework\TestCase\GraphQlAbstract`. It defines the `graphQlQuery()`and `graphQlMutation()` methods, which should be used to perform Web API calls from tests.
13
13
14
14
The following test verifies that the schema returns the correct attribute type, given the `attribute_code` and corresponding `entity_type`.
Copy file name to clipboardExpand all lines: src/guides/v2.3/graphql/mutations/place-order.md
+15-1
Original file line number
Diff line number
Diff line change
@@ -73,5 +73,19 @@ Attribute | Data Type | Description
73
73
74
74
Attribute | Data Type | Description
75
75
--- | --- | ---
76
-
`order_id`| String | Deprecated. Use `order_number` instead
76
+
`order_id` String | The unique ID that identifies the order
77
77
`order_number` String | The unique ID that identifies the order
78
+
79
+
## Errors
80
+
81
+
Error | Description
82
+
--- | ---
83
+
`Enter a valid payment method and try again` | The payment method was not set. See [setPaymentMethodOnCart]({{ page.baseurl }}/graphql/mutations/set-payment-method.html) mutation.
84
+
`Guest email for cart is missing.` | The guest attempted to place an order but did not provide an email address. See [setGuestEmailOnCart]({{ page.baseurl }}/graphql/mutations/set-guest-email.html) mutation.
85
+
`Please check the billing address information` | The billing address was not set. See [setBillingAddressOnCart]({{ page.baseurl }}/graphql/mutations/set-billing-address.html) mutation.
86
+
`Required parameter "cart_id" is missing` | The mutation does not contain a `cart_id` parameter.
87
+
`Some addresses can't be used due to the configurations for specific countries` | The shipping method was not set. See [setShippingMethodsOnCart]({{ page.baseurl }}/graphql/mutations/set-shipping-method.html) mutation.
88
+
`Some of the products are out of stock` | One of the products in the shopping cart are currently out of stock.
89
+
`The current user cannot perform operations on cart` | An unauthorized user (guest) tried to place an order on behalf of an authorized user (customer), or a customer tried to place an order on behalf of another customer.
90
+
`The shipping method is missing. Select the shipping method and try again` | The shipping method was not set. See [setShippingMethodsOnCart]({{ page.baseurl }}/graphql/mutations/set-shipping-method.html) mutation.
91
+
`Unable to place order: A server error stopped your order from being placed. Please try to place your order again` | The shopper tried to place an order when no products are in the shopping cart.
Copy file name to clipboardExpand all lines: src/guides/v2.3/graphql/mutations/remove-item.md
+14-2
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,8 @@ mutation {
24
24
cart_id: "IeTUiU0oCXjm0uRqGCOuhQ2AuQatogjG",
25
25
cart_item_id: 14
26
26
}
27
-
){
27
+
)
28
+
{
28
29
cart {
29
30
items {
30
31
id
@@ -37,9 +38,10 @@ mutation {
37
38
grand_total{
38
39
value
39
40
currency
40
-
}
41
+
}
41
42
}
42
43
}
44
+
}
43
45
}
44
46
```
45
47
@@ -94,4 +96,14 @@ Attribute | Data Type | Description
94
96
95
97
{% include graphql/cart-object.md %}
96
98
99
+
## Errors
100
+
101
+
Error | Description
102
+
--- | ---
103
+
`Cart doesn't contain the ZZZ item.` | The item ID specified in the `cart_item_id` attribute does not exist in the requested shopping cart.
104
+
`Could not find a cart with ID "XXX"` | The specified `cart_id` value does not exist in the `quote_id_mask` table.
105
+
`Required parameter "cart_id" is missing.` | The value specified in the `cart_id` attribute is empty.
106
+
`Required parameter "cart_item_id" is missing.` | The value specified in the `cart_item_id` attribute is equal to zero.
107
+
`The current user cannot perform operations on cart "XXX"` | An unauthorized user (guest) tried to remove a product from the shopping cart of authorized user (customer), or a customer tried to remove a product from the shopping cart of another customer.
108
+
97
109
[Cart query output]({{page.baseurl}}/graphql/queries/cart.html#cart-output) provides more information about the `Cart` object.
Copy file name to clipboardExpand all lines: src/guides/v2.3/javascript-dev-guide/javascript/js_init.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ In Magento 2, you have two options for specifying declarative notation:
27
27
28
28
> This is used to target a specific HTML element. It is easier to implement and is commonly used for jQuery UI widgets. This method can only be implemented on the specified HTML tag. For example, `<nav data-mage-init='{ "<component_name>": {...} }'></nav>`. This is preferred for its concise syntax, and direct access to the HTML element.
29
29
30
-
- Using the `<script type="text/x-magento-init" />` tag
30
+
- Using the `<script type="text/x-magento-init"> ... </script>` tag
31
31
32
32
> This is used to target either a CSS selector or `*`. If the CSS selector matches multiple HTML elements, the script will run for each matched HTML element. For `*`, no HTML element is selected and the script will run once with the HTML DOM as its target. This method can be implemented from anywhere in the codebase to target any HTML element. This is preferred when direct access to the HTML element is restricted, or when there is no target HTML element.
33
33
@@ -68,7 +68,7 @@ On DOM ready, the `data-mage-init` attribute is parsed to extract component name
68
68
69
69
- If none of the previous cases is true, the component is executed with no further processing. Such a component does not require either `config` or `element`. The recommended way to declare such components is [using the `<script>` tag](#init_script).
70
70
71
-
#### Declarative notation using the `<script type="text/x-magento-init" />` tag {#decl_tag}
71
+
#### Declarative notation using the `<script type="text/x-magento-init">` tag {#decl_tag}
72
72
73
73
To call a JS component on an HTML element without direct access to the element or with no relation to a certain element, use the `<script type="text/x-magento-init">` tag and attribute syntax shown in the following example.
0 commit comments