-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Cloud Docker 1.2.0 Release #8199
Changes from 17 commits
b1d1b60
3477b59
b678eb1
caa18a7
e2d21ea
7f8ebe1
842dad4
909f032
c0f3893
a95939d
dbc2cb3
a277458
501e099
381895a
2294c72
73b76a7
ce4262f
b90c8ec
0fbb5c7
dc13081
ddad989
1762a11
61b9b71
32433ee
04c75c0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -75,6 +75,20 @@ See [Important Elasticsearch configuration][] in the Elasticsearch documentation | |
{:.bs-callout-info} | ||
If your Cloud project uses Magento version 2.3.5 or earlier with MySQL search, add the `--no-es` option to skip the Elasticsearch container configuration when you generate the Docker Compose configuration file: `ece-docker build:compose --no-es`. | ||
|
||
### Elasticsearch plugins | ||
|
||
The `analysis-icu` and `analysis-phonetic` plugins are installed by default and can not be skipped. | ||
If you use Elasticsearch 6.5 and later, the default Elasticsearch plugins configured in `.magento/services.yaml` are installed automatically along with any custom plugins added to the `services.yaml`. When you generate the `docker-compose.yaml` file, custom plugins are added to the `ES_PLUGINS` environment configuration option. | ||
|
||
You can change the list of plugins to install by updating the configuration for the `ES_PLUGINS` variable: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe add a little more description about the example. Something like "The following example adds the..." |
||
|
||
```yaml | ||
services: | ||
elasticsearch: | ||
environment: | ||
- 'ES_PLUGINS=analysis-stempel analysis-nori' | ||
``` | ||
|
||
### Troubleshooting | ||
|
||
On some Linux systems, when you launch the Docker environment, the Elasticsearch service fails to start and the following error displays: | ||
|
@@ -168,6 +182,14 @@ docker-compose run --rm redis redis-cli -h redis | |
|
||
The Selenium container, based on the [selenium/standalone-chrome/](https://hub.docker.com/r/selenium/standalone-chrome/h), enables the [Magento Functional Testing Framework (MFTF)](https://devdocs.magento.com/mftf/docs/introduction.html) for Magento application testing in the Cloud Docker environment. See [Magento application testing]({{site.baseurl}}/cloud/docker/docker-test-app-mftf.html). | ||
|
||
## Test container | ||
|
||
**Container name**: test<br/> | ||
**Docker base image**: [magento/magento-cloud-docker-php][php-cloud], which is based on the [php](https://hub.docker.com/_/php) Docker image<br/> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why say based-on here when it is in the following paragraph? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Handled inconsistently. Moved "based on ... Docker image" to the header info for all containers. |
||
**Ports exposed**: None<br/> | ||
|
||
The Test container, based on the [magento/magento-cloud-docker-php][php-cloud] Docker image has a writable file system and is used for Magento application testing in the Cloud Docker environment. See [Magento application testing]({{site.baseurl}}/cloud/docker/docker-test-app-mftf.html). | ||
meker12 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## TLS container | ||
|
||
**Container name**: tls<br/> | ||
|
Uh oh!
There was an error while loading. Please reload this page.