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
Copy file name to clipboardExpand all lines: guides/v2.1/cloud/bk-cloud.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Amazon Web Services (AWS) powers the underlying Infrastructure as a Service (Iaa
22
22
23
23
## {{site.data.var.ct}} package
24
24
25
-
The `{{site.data.var.ct}}` package is a scalable deployment tool that simplifies the Cloud upgrade process. In 2018, we deprecated the `magento-cloud-configuration` and `ece-patches` packages in favor of providing a single package. We encourage all customers to [upgrade to use `{{site.data.var.ct}}`]({{page.baseurl}}/cloud/project/ece-tools-upgrade-project.html) as soon as possible to benefit from the package features, such as commands to create a backup of the database, apply custom patches, and verify environment configuration.
25
+
The [`{{site.data.var.ct}}` package][ece] is a scalable deployment tool that simplifies the Cloud upgrade process. In 2018, we deprecated the `magento-cloud-configuration` and `ece-patches` packages in favor of providing a single package. We encourage all customers to [upgrade to use `{{site.data.var.ct}}`]({{page.baseurl}}/cloud/project/ece-tools-upgrade-project.html) as soon as possible to benefit from the package features, such as commands to create a backup of the database, apply custom patches, and verify environment configuration.
26
26
27
27
<!-- Link definitions -->
28
28
@@ -31,3 +31,5 @@ The `{{site.data.var.ct}}` package is a scalable deployment tool that simplifies
1. Download a Magento application template from the [Magento Cloud repository](https://github.com/magento/magento-cloud). Be careful to select the branch that corresponds with the Magento version.
89
95
@@ -110,7 +116,7 @@ Continue launching your Docker environment in the default _production_ mode.
110
116
1. _Optional_: If you have a custom PHP configuration file, copy the default configuration DIST file to your custom configuration file and make any necessary changes.
111
117
112
118
```bash
113
-
cp docker/config.php.dist docker/config.php
119
+
cp .docker/config.php.dist .docker/config.php
114
120
```
115
121
116
122
Convert custom PHP configuration files to Docker ENV files.
@@ -121,12 +127,12 @@ Continue launching your Docker environment in the default _production_ mode.
121
127
122
128
This generates the following Docker ENV files:
123
129
124
-
*`docker/config.env`
130
+
* `.docker/config.env`
125
131
126
132
{: .bs-callout .bs-callout-info}
127
133
The `{{site.data.var.ct}}` version 2002.0.12 package does not support the `docker:config:convert` command.
128
134
129
-
1. _Optional_: Configure the Docker global variables in the `docker-compose.yml` file. For example, you can [enable and configure Xdebug]({{ page.baseurl }}/cloud/docker/docker-development-debug.html).
135
+
1. _Optional_: Configure the Docker global variables in the `docker-compose.yml` file. For example, you can [configure Xdebug]({{ page.baseurl }}/cloud/docker/docker-development-debug.html#configure-xdebug).
130
136
131
137
1. Build files to containers and run in the background.
132
138
@@ -138,15 +144,15 @@ Continue launching your Docker environment in the default _production_ mode.
138
144
139
145
- Build Magento in the Docker container:
140
146
141
-
```bash
142
-
docker-compose run build cloud-build
143
-
```
147
+
```bash
148
+
docker-compose run build cloud-build
149
+
```
144
150
145
151
- Deploy Magento in the Docker container:
146
152
147
-
```bash
148
-
docker-compose run deploy cloud-deploy
149
-
```
153
+
```bash
154
+
docker-compose run deploy cloud-deploy
155
+
```
150
156
151
157
{: .bs-callout .bs-callout-info}
152
158
For `{{site.data.var.ct}}` v2002.0.12, install Magento with the `docker-compose run cli magento-installer` command.
@@ -184,7 +190,7 @@ The `{{site.data.var.ct}}` version 2002.0.18 and later supports developer mode.
184
190
1. _Optional_: If you have a custom PHP configuration file, copy the default configuration DIST file to your custom configuration file and make any necessary changes.
185
191
186
192
```bash
187
-
cp docker/config.php.dist docker/config.php
193
+
cp .docker/config.php.dist .docker/config.php
188
194
```
189
195
190
196
Convert custom PHP configuration files to Docker ENV files.
@@ -195,16 +201,24 @@ The `{{site.data.var.ct}}` version 2002.0.18 and later supports developer mode.
195
201
196
202
This generates the following Docker ENV files:
197
203
198
-
*`docker/config.env`
204
+
* `.docker/config.env`
199
205
200
206
1. _Optional_: Configure the Docker global variables in the `docker-compose.yml` file. For example, you can [enable and configure Xdebug]({{ page.baseurl }}/cloud/docker/docker-development-debug.html).
201
207
202
208
1. Start the file synchronization.
203
209
210
+
For the `docker-sync` tool:
211
+
204
212
```bash
205
213
docker-sync start
206
214
```
207
215
216
+
For the `mutagen` tool:
217
+
218
+
```bash
219
+
bash ./mutagen.sh
220
+
```
221
+
208
222
1. Build files to containers and run in the background.
209
223
210
224
```bash
@@ -272,11 +286,11 @@ docker-sync stop
272
286
273
287
## Advanced usage
274
288
275
-
### Extending docker-compose.yml configuration
289
+
### Extend the Docker configuration
276
290
277
-
You can use Docker's built-in [extension mechanism](https://docs.docker.com/compose/reference/overview/#specifying-multiple-compose-files).
291
+
You can use the built-in extension mechanism of Docker to [specify multiple compose files](https://docs.docker.com/compose/reference/overview/#specifying-multiple-compose-files). The following example replaces the default value of the `ENABLE_SENDMAIL` environment variable.
278
292
279
-
1. Create a `docker-compose-dev.yml` file inside your project's root directory and add the following content:
293
+
1. Create a `docker-compose-dev.yml` file inside your project root directory and add the following content:
280
294
281
295
```yaml
282
296
version: '2'
@@ -286,8 +300,6 @@ You can use Docker's built-in [extension mechanism](https://docs.docker.com/comp
286
300
- ENABLE_SENDMAIL=true
287
301
```
288
302
289
-
This replaces the default value of the `ENABLE_SENDMAIL` environment variable.
290
-
291
303
1. Pass both configuration files while executing your commands. For example:
Copy file name to clipboardExpand all lines: guides/v2.1/cloud/docker/docker-database.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ functional_areas:
7
7
- Configuration
8
8
---
9
9
10
-
There are two ways to connect to the database. Before you begin, you can find the database credentials in the `database` section of the `docker/config.php` file. The examples use the following default credentials:
10
+
There are two ways to connect to the database. Before you begin, you can find the database credentials in the `database` section of the `.docker/config.php` file. The examples use the following default credentials:
Copy file name to clipboardExpand all lines: guides/v2.1/cloud/docker/docker-development-debug.md
+33-19Lines changed: 33 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -18,29 +18,43 @@ If you use Microsoft Windows, take the following steps before continuing:
18
18
19
19
## Enable Xdebug
20
20
21
-
To enable Xdebug, you must configure your `docker-compose.yaml` file at the time you configure your local workstation to [Launch Docker]({{ page.baseurl }}/cloud/docker/docker-config.html).
21
+
To enable Xdebug for your project, add `xdebug` to the `runtime:extensions` section of the `.magento.app.yaml` file.
22
22
23
23
```yaml
24
-
generic:
25
-
image: alpine
26
-
environment:
27
-
- PHP_MEMORY_LIMIT=2048M
28
-
- DEBUG=false
29
-
- ENABLE_SENDMAIL=false
30
-
- UPLOAD_MAX_FILESIZE=64M
31
-
- MAGENTO_ROOT=/app
32
-
- PHP_ENABLE_XDEBUG=false
33
-
- PHP_IDE_CONFIG=serverName=magento_cloud_docker
34
-
- XDEBUG_CONFIG=remote_host=host.docker.internal
35
-
env_file:
36
-
- ./docker/config.env
24
+
runtime:
25
+
extensions:
26
+
- redis
27
+
- xsl
28
+
- json
29
+
- blackfire
30
+
- newrelic
31
+
- xdebug
37
32
```
38
33
39
-
You can change any Xdebug configuration using the`XDEBUG_CONFIG` option. For example, to change the `xdebug.remote_port` option:
1. Rebuild the `docker-compose.yml` file by continuing to configure your local workstation to [launch the Docker environment]({{ page.baseurl }}/cloud/docker/docker-config.html). The following is an excerpt from the `docker-compose.yml` file that shows Docker global variables.
0 commit comments