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.
By default, the TLS container is included with the Docker Compose configuration. However, you can generate a configuration without TLS by adding the `--no-tls` option to the `ece-docker build:compose` command.
222
+
221
223
The TLS termination proxy container facilitates the Varnish SSL termination over HTTPS.
222
224
223
225
- The default port for TLS communication is `443`.
The Web container uses NGINX to handle web requests after TLS and Varnish. This container passes all requests to the FPM container to serve the PHP code. See [Request flow]({{site.baseurl}}/cloud/docker/docker-containers.html#request-flow).
269
271
272
+
This container provides two NGINX configuration options for building the Docker configuration:
273
+
274
+
- `--nginx-worker-processes`to set the number of worker processes for NGINX. The default is `1`.
275
+
- `--nginx-worker-connections`to set the maximum number of connections that each worker process can handle simultaneously. The default is `1024`.
276
+
270
277
The NGINX configuration for this container is the standard Magento [nginx config], which includes the configuration to auto-generate NGINX certificates for the container. You can customize the NGINX configuration by mounting a new configuration file using a volume.
| [selenium][selenium-container]| Selenium | `--with-selenium`<br>`--selenium-version`<br>`--selenium-image`| Any | Enables Magento application testing using the Magento Functional Testing Framework (MFTF)
55
55
| [test][test-container]| PHP CLI | `--with-test`| Any | Optional container with a writable file system for running tests
56
-
| [tls][tls-container] | SSL Endpoint | `--tls-port` | nginx 1.19-1.2.0, latest | Terminates SSL, can be configured to pass to varnish or nginx. Use the `--tls-port` option to change the default port (443).
56
+
| [tls][tls-container] | SSL Endpoint | `--tls-port`<br/>`--no-tls` | nginx 1.19-1.2.0, latest | Terminates SSL, can be configured to pass to varnish or nginx. Use the `--tls-port` option to change the default port (443).<br/>Use the `--no-tls` option to disable tls.
57
57
| [varnish][varnish-container] | Varnish | `--no-varnish` | 4, 6.2 | Varnish is provisioned by default. Use the `--no-varnish` option to skip Varnish service installation.
58
-
| [web][web-container] | NGINX | `--nginx` | 1.19-1.2.0, latest | Use the `--nginx` option to install a specific nginx version.
58
+
| [web][web-container] | NGINX | `--nginx`<br/>`--nginx-worker-processes`<br/>`--nginx-worker-connections` | 1.19-1.2.1, latest | Use the `--nginx` option to install a specific nginx version.<br/>Use the `--nginx-worker-processes` option to define the number of NGINX worker processes. The default is 1.<br/>Use the `--nginx-worker-connections` option to define the maximum number of connections that each worker process can handle simultaneously. The default is 1024 NGINX worker connections per process.
59
59
60
60
Use the following command to view all available options for the `ece-docker build:compose` command:
Copy file name to clipboardExpand all lines: src/cloud/release-notes/mcd-release-notes.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,32 @@ The release notes include:
16
16
- {:.new}New features
17
17
- {:.fix}Fixes and improvements
18
18
19
+
## v1.2.1
20
+
*Release date: December 21, 2020*<br/>
21
+
22
+
- {:.new}<!--MCLOUD-7259-->**NGINX command options**–Added build command options to change the number of NGINX `worker_processes` and NGINX `worker_connections` for TLS and Web services. The `worker_process` parameter retains the ability to set the value to `auto`. Examples:
- {:.new}<!--MCLOUD-7259-->**TLS command option**–Added build command option to create a configuration without the TLS service. Example:
30
+
31
+
```terminal
32
+
./vendor/bin/ece-docker build:compose --no-tls
33
+
```
34
+
35
+
- {:.new}<!--MCLOUD-7259-->**NGINX memory consumption**–Reduced the memory consumed by the NGINX process for TLS and Web services.
36
+
37
+
- {:.new}<!--No ticket -->**Blackfire**–Disabled Blackfire PHP extension by default in the Cloud Docker image.
38
+
39
+
- {:.fix}<!--MCLOUD-7232-->**PHP-FPM container**–Fixed PHP-FPM container health check by changing the `WEB_PORT` from `80` to `8080`.
40
+
41
+
- {:.fix}<!--MCLOUD-7442-->**Invalid volume naming**–Fixed an error with invalid volume naming in developer mode.
42
+
43
+
- {:.fix}<!--Issue 295-->**NGINX upstream port**—Updated the Docker NGINX 1.19 image to use port 8080 to avoid an infinite loop. *[Fix submitted by Adarsh Manickam](https://github.com/magento/magento-cloud-docker/pull/296).*
title: Revert from a split database to a single database
4
+
ee_only: true
5
+
functional_areas:
6
+
- Configuration
7
+
- System
8
+
- Setup
9
+
---
10
+
11
+
For {{ site.data.var.ee }} customers who have implemented [Split Database]({{ page.baseurl }}/config-guide/multi-master/multi-master.html), the following topic describes how to revert or migrate back to a single database. We recommend that {{ site.data.var.ee }} merchants currently using Split Database who are upgrading to 2.4.2 and above review these steps, as well as our [announcement](https://community.magento.com/t5/Magento-DevBlog/Deprecation-of-Split-Database-in-Magento-Commerce/ba-p/465187) on the planned deprecation of Split Database.
12
+
13
+
Reverting from a split database to a single database implementation involves creating backups of the `magento_quote` and `magento_sales` databases before loading them into the single `magento_main` database.
14
+
15
+
In this example, we log in to all three databases, which are installed on the same host (`magento2-mysql`) as the "root" user. You must replace these values with the appropriate values for your databases.
16
+
17
+
1. Create a backup of the `magento_quote` database:
1. Load the `magento_quote` database into the `magento_main` database:
30
+
31
+
```bash
32
+
mysql -h "magento2-mysql" -u root -p magento_main < ./quote.sql
33
+
```
34
+
35
+
1. Load the `magento_sales` database into the `magento_main` database:
36
+
37
+
```bash
38
+
mysql -h "magento2-mysql" -u root -p magento_main < ./sales.sql
39
+
```
40
+
41
+
1. Drop the `magento_sales` database:
42
+
43
+
```bash
44
+
mysql -h "magento2-mysql" -u root -p -e "DROP DATABASE magento_sales;"
45
+
```
46
+
47
+
1. Drop the `magento_quote` database:
48
+
49
+
```bash
50
+
mysql -h "magento2-mysql" -u root -p -e "DROP DATABASE magento_quote;"
51
+
```
52
+
53
+
1. Remove the deployment configuration for `checkout` and `sales` in the `connections` and `resources` sections of the `env.php` file.
54
+
1. Restore foreign keys:
55
+
56
+
```bash
57
+
bin/magento setup:upgrade
58
+
```
59
+
60
+
## Verify your work
61
+
62
+
To verify that your single database implementation is working properly, perform the following tasks and verify that data is added to the `magento_main` database tables using a database tool like [phpMyAdmin]({{ page.baseurl }}/install-gde/prereq/optional.html#install-optional-phpmyadmin):
63
+
64
+
1. Verify that foreign keys have been restored. For example, the `QUOTE_STORE_ID_STORE_STORE_ID` key in the `quote` database table.
65
+
1. Verify that customers can place orders from the storefront.
66
+
1. Verify that orders created before reverting the split database to a single database are available in the Admin.
Copy file name to clipboardExpand all lines: src/guides/v2.3/extension-dev-guide/proxies.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,3 +73,13 @@ With the proxy used in place of `SlowLoading`, the `SlowLoading` class will not
73
73
Because DI configuration is used to inject a proxy, proxies can be dropped in to replace their corresponding classes - or proxy replacements _removed_ - without touching application code.
74
74
75
75
As a practical example of a proxy, you can see the [StoreManager]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Store/Model/StoreManager.php){:target="_blank"} class and then see the generated `StoreManager` proxy class.
76
+
77
+
The following excerpt from the Magento code passes the `storeManager` argument as a proxy to the `Magento\Store\Model\Resolver\Store` class. The `StoreManagerInterface` model is defined as a proxy class by the added `Proxy` at the end of the original class in the `di.xml` file.
0 commit comments