From a115544b47917343bda514f61c9836e6c66383f3 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 13 May 2019 11:19:47 -0400 Subject: [PATCH 01/33] Added header for 2002.0.19 release notes --- guides/v2.1/cloud/release-notes/cloud-tools.md | 3 +++ guides/v2.2/cloud/release-notes/cloud-tools.md | 4 ++++ guides/v2.3/cloud/release-notes/cloud-tools.md | 3 +++ 3 files changed, 10 insertions(+) diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index 4a66ffb0625..947f15608f0 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -30,6 +30,9 @@ The release notes include: - {:.new}New features - {:.fix}Fixes and improvements +## v2002.0.19 + + ## v2002.0.18 - {:.new}**Docker Updates**— diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index b8ca8c390e6..5553abfc88c 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -30,6 +30,10 @@ The release notes include: - {:.new}New features - {:.fix}Fixes and improvements +## v2002.0.19 + + + ## v2002.0.18 - {:.new}**Docker Updates**— diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md index 9c96847c25b..de7af58fb06 100644 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ b/guides/v2.3/cloud/release-notes/cloud-tools.md @@ -30,6 +30,9 @@ The release notes include: - {:.new}New features - {:.fix}Fixes and improvements +## v2002.0.19 + + ## v2002.0.18 - {:.new}**Docker Updates**— From aced8c2c151f7f391cec11651e0bde8718d203d2 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Tue, 14 May 2019 16:09:30 -0400 Subject: [PATCH 02/33] Add FORCE_UPDATE_URLS deploy variable doc (#4516) - Added the FORCE_UPDATE_URLS deploy variable to update Magento base URLs when deploying Magento Commerce Cloud projects to production and staging environments. - Updated the release notes for 2002.0.19 --- guides/v2.1/cloud/env/variables-deploy.md | 20 ++++++++++++++++--- .../v2.1/cloud/release-notes/cloud-tools.md | 3 +++ guides/v2.2/cloud/env/variables-deploy.md | 19 +++++++++++++++--- .../v2.2/cloud/release-notes/cloud-tools.md | 2 ++ .../v2.3/cloud/release-notes/cloud-tools.md | 4 ++++ 5 files changed, 42 insertions(+), 6 deletions(-) diff --git a/guides/v2.1/cloud/env/variables-deploy.md b/guides/v2.1/cloud/env/variables-deploy.md index a6dae8625d8..f31c2875803 100644 --- a/guides/v2.1/cloud/env/variables-deploy.md +++ b/guides/v2.1/cloud/env/variables-deploy.md @@ -124,6 +124,19 @@ stage: {:.bs-callout .bs-callout-info} The {{ site.data.var.ece }} deploy process always enables Google Analytics on Production environments. +### `FORCE_UPDATE_URLS` + +- **Default**—`true` +- **Version**—Magento 2.1.4 and later + +On deployment to Pro and Starter staging and production environments, this variable replaces Magento base URLs in the database with the project URLs specified by the [`MAGENTO_CLOUD_ROUTES`]({{ page.baseurl}}/cloud/env/variables-cloud.html) variable. Use this setting to override the default behavior of the [UPDATE_URLS](#update_urls) variable which is ignored when deploying to staging and production environments. + +```yaml +stage: + deploy: + FORCE_UPDATE_URLS: true +``` + ### `GENERATED_CODE_SYMLINK` - **Default**—`true` @@ -424,7 +437,10 @@ stage: - **Default**—`true` - **Version**—Magento 2.1.4 and later -On deployment, replace Magento base URLs in the database with project URLs. This is useful for local development, where base URLs are set up for your local environment. When you deploy to a Cloud environment, we change the URLs so you can access your storefront and Magento Admin using project URLs. +On deployment, replace Magento base URLs in the database with the project URLs specified by the [`MAGENTO_CLOUD_ROUTES`]({{ page.baseurl }}/cloud/env/variables-cloud.html) variable. This is useful for local development, where base URLs are set up for your local environment. +When you deploy to a Cloud environment, we change the URLs so you can access your storefront and Magento Admin using project URLs. + +If you need to update URLs when deploying to Pro or Starter staging and production environments, use the [`FORCE_UPDATE_URLS`](#force_update_urls) variable. ```yaml stage: @@ -432,8 +448,6 @@ stage: UPDATE_URLS: false ``` -You should set this variable to `false` _only_ in Staging or Production environments, where the base URLs cannot change. For Pro, we already set this to `false` for you. - ### `VERBOSE_COMMANDS` - **Default**—_Not set_ diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index 947f15608f0..77d91585161 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -32,6 +32,9 @@ The release notes include: ## v2002.0.19 +- {:.new}**Environment variable updates**— + + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. ## v2002.0.18 diff --git a/guides/v2.2/cloud/env/variables-deploy.md b/guides/v2.2/cloud/env/variables-deploy.md index e67c680214c..8c9f7f25d2c 100644 --- a/guides/v2.2/cloud/env/variables-deploy.md +++ b/guides/v2.2/cloud/env/variables-deploy.md @@ -194,6 +194,19 @@ stage: {:.bs-callout .bs-callout-info} The {{ site.data.var.ece }} deploy process always enables Google Analytics on Production environments. +### `FORCE_UPDATE_URLS` + +- **Default**—`true` +- **Version**—Magento 2.1.4 and later + +On deployment to Pro or Starter staging and production environments, this variable replaces Magento base URLs in the database with the project URLs specified by the [`MAGENTO_CLOUD_ROUTES`]({{page.baseurl}}/cloud/env/variables-cloud.html) variable. Use this setting to override the default behavior of the [UPDATE_URLS](#update_urls) deploy variable which is ignored when deploying to staging or production environments. + +```yaml +stage: + deploy: + FORCE_UPDATE_URLS: true +``` + ### `MYSQL_USE_SLAVE_CONNECTION` - **Default**—`false` @@ -512,7 +525,9 @@ stage: - **Default**—`true` - **Version**—Magento 2.1.4 and later -On deployment, replace Magento base URLs in the database with project URLs. This is useful for local development, where base URLs are set up for your local environment. When you deploy to a Cloud environment, we change the URLs so you can access your storefront and Magento Admin using project URLs. +On deployment, replace Magento base URLs in the database with the project URLs specified by the [`MAGENTO_CLOUD_ROUTES`]({{page.baseurl}}/cloud/env/variables-cloud.html) variable. This is useful for local development, where base URLs are set up for your local environment. When you deploy to a Cloud environment, we change the URLs so you can access your storefront and Magento Admin using project URLs. + +If you need to update URLs when deploying to Pro or Starter staging and production environments, use the [`FORCE_UPDATE_URLS`](#force_update_urls) variable. ```yaml stage: @@ -520,8 +535,6 @@ stage: UPDATE_URLS: false ``` -You should set this variable to `false` _only_ in Staging or Production environments, where the base URLs cannot change. For Pro, we already set this to `false` for you. - ### `VERBOSE_COMMANDS` - **Default**—_Not set_ diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index 5553abfc88c..ff418313e36 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -32,7 +32,9 @@ The release notes include: ## v2002.0.19 +- {:.new}**Environment variable updates**— + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. ## v2002.0.18 diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md index de7af58fb06..89122cadae1 100644 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ b/guides/v2.3/cloud/release-notes/cloud-tools.md @@ -32,6 +32,10 @@ The release notes include: ## v2002.0.19 +- {:.new}**Environment variable updates**— + + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + ## v2002.0.18 From 0e94bfeef29b5daa0dc12d3b6d8d25bcdafacf2b Mon Sep 17 00:00:00 2001 From: hguthrie Date: Wed, 15 May 2019 10:18:04 -0500 Subject: [PATCH 03/33] MAGECLOUD-2973 db table prefixes (#4511) * MAGECLOUD-2973 db table prefixes * updates from technical review --- guides/v2.1/cloud/env/variables-deploy.md | 41 ++++++++++++++++ .../v2.1/cloud/release-notes/cloud-tools.md | 4 +- guides/v2.2/cloud/env/variables-deploy.md | 47 ++++++++++++++++++- .../v2.2/cloud/release-notes/cloud-tools.md | 4 +- .../v2.3/cloud/release-notes/cloud-tools.md | 3 +- 5 files changed, 94 insertions(+), 5 deletions(-) diff --git a/guides/v2.1/cloud/env/variables-deploy.md b/guides/v2.1/cloud/env/variables-deploy.md index f31c2875803..7c0e3a6b411 100644 --- a/guides/v2.1/cloud/env/variables-deploy.md +++ b/guides/v2.1/cloud/env/variables-deploy.md @@ -103,6 +103,47 @@ stage: _merge: true ``` +Also, you can configure a table prefix. + +{: .bs-callout .bs-callout-warning} +If you do not use the merge option with the table prefix, you must provide default connection settings or the deploy fails validation. + +The following example uses the `ece_` table prefix with default connection settings instead of using the `_merge` option: + +```yaml +stage: + deploy: + DATABASE_CONFIGURATION: + connection: + default: + username: user + host: host + dbname: magento + password: password + table_prefix: 'ece_' +``` + +Sample output: + +```terminal +MariaDB [main]> SHOW TABLES; ++-------------------------------------+ +| Tables_in_main | ++-------------------------------------+ +| ece_admin_passwords | +| ece_admin_system_messages | +| ece_admin_user | +| ece_admin_user_session | +| ece_adminnotification_inbox | +| ece_amazon_customer | +| ece_authorization_rule | +| ece_cache | +| ece_cache_tag | +| ece_captcha_log | +..... +``` +{: .no-copy} + ### `ENABLE_GOOGLE_ANALYTICS` - **Default**—`false` diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index 77d91585161..df6efceb0ad 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -34,7 +34,9 @@ The release notes include: - {:.new}**Environment variable updates**— - - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + + - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). ## v2002.0.18 diff --git a/guides/v2.2/cloud/env/variables-deploy.md b/guides/v2.2/cloud/env/variables-deploy.md index 8c9f7f25d2c..ca71fc37a6f 100644 --- a/guides/v2.2/cloud/env/variables-deploy.md +++ b/guides/v2.2/cloud/env/variables-deploy.md @@ -98,8 +98,9 @@ By default, the deployment process overwrites all settings in the `env.php` file #### To see a list of message queue consumers: - ./bin/magento queue:consumers:list - +```bash +./bin/magento queue:consumers:list +``` ### `CRYPT_KEY` - **Default**—_Not set_ @@ -133,6 +134,48 @@ stage: _merge: true ``` +Also, you can configure a table prefix. + +{: .bs-callout .bs-callout-warning} +If you do not use the merge option with the table prefix, you must provide default connection settings or the deploy fails validation. + +The following example uses the `ece_` table prefix with default connection settings instead of using the `_merge` option: + +```yaml +stage: + deploy: + DATABASE_CONFIGURATION: + connection: + default: + username: user + host: host + dbname: magento + password: password + table_prefix: 'ece_' +``` + +Sample output: + +```terminal +MariaDB [main]> SHOW TABLES; ++-------------------------------------+ +| Tables_in_main | ++-------------------------------------+ +| ece_admin_passwords | +| ece_admin_system_messages | +| ece_admin_user | +| ece_admin_user_session | +| ece_adminnotification_inbox | +| ece_amazon_customer | +| ece_authorization_rule | +| ece_cache | +| ece_cache_tag | +| ece_captcha_log | +..... +``` +{: .no-copy} + + ### `ELASTICSUITE_CONFIGURATION` - **Default**—_Not set_ diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index ff418313e36..811163a9a3c 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -34,7 +34,9 @@ The release notes include: - {:.new}**Environment variable updates**— - - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + + - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). ## v2002.0.18 diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md index 89122cadae1..63a95f529b2 100644 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ b/guides/v2.3/cloud/release-notes/cloud-tools.md @@ -34,8 +34,9 @@ The release notes include: - {:.new}**Environment variable updates**— - - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). ## v2002.0.18 From 678f47035c2d394a4f1a8191e3782a69099cf5cf Mon Sep 17 00:00:00 2001 From: Oleg Posyniak Date: Tue, 21 May 2019 10:21:10 -0500 Subject: [PATCH 04/33] MAGECLOUD-3569: Improve UX by adding scripts (#4565) --- guides/v2.1/cloud/docker/docker-config.md | 8 ++++---- guides/v2.1/cloud/docker/docker-database.md | 6 +++--- .../v2.1/cloud/docker/docker-development-debug.md | 2 +- guides/v2.1/cloud/docker/docker-development.md | 6 +++--- guides/v2.1/cloud/docker/docker-quick-reference.md | 14 ++++++++++++++ 5 files changed, 25 insertions(+), 11 deletions(-) diff --git a/guides/v2.1/cloud/docker/docker-config.md b/guides/v2.1/cloud/docker/docker-config.md index 845d7e13c41..bc39d1f7231 100644 --- a/guides/v2.1/cloud/docker/docker-config.md +++ b/guides/v2.1/cloud/docker/docker-config.md @@ -96,7 +96,7 @@ Continue launching your Docker environment in the default _production_ mode. 1. _Optional_: Copy the raw configuration files. ```bash - cp docker/config.php.dist docker/config.php + cp .docker/config.php.dist .docker/config.php ``` 1. _Optional_: Convert the PHP configuration files to Docker ENV files. @@ -107,7 +107,7 @@ Continue launching your Docker environment in the default _production_ mode. This command generates the following Docker ENV files: - * `docker/config.env` + * `.docker/config.env` {: .bs-callout .bs-callout-info} The `{{site.data.var.ct}}` version 2002.0.12 package does not support the `docker:config:convert` command. @@ -170,7 +170,7 @@ The `{{site.data.var.ct}}` version 2002.0.18 and later supports developer mode. 1. _Optional_: Copy the raw configuration files. ```bash - cp docker/config.php.dist docker/config.php + cp .docker/config.php.dist .docker/config.php ``` 1. _Optional_: Convert the PHP configuration files to Docker ENV files. @@ -181,7 +181,7 @@ The `{{site.data.var.ct}}` version 2002.0.18 and later supports developer mode. This command generates the following Docker ENV files: - * `docker/config.env` + * `.docker/config.env` 1. _Optional_: Configure the Docker global variables in the `docker-compose.yaml` file. For example, you can [enable and configure Xdebug]({{ page.baseurl }}/cloud/docker/docker-development-debug.html). diff --git a/guides/v2.1/cloud/docker/docker-database.md b/guides/v2.1/cloud/docker/docker-database.md index 9b6b516b289..fdb87089e41 100644 --- a/guides/v2.1/cloud/docker/docker-database.md +++ b/guides/v2.1/cloud/docker/docker-database.md @@ -7,9 +7,9 @@ functional_areas: - Configuration --- -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: +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: -> Filename: `docker/config.php` +> Filename: `.docker/config.php` ```php?start_inline=1 return [ @@ -85,4 +85,4 @@ return [ | 10.0.38-MariaDB-1~xenial | +--------------------------+ ``` - {: .no-copy} \ No newline at end of file + {: .no-copy} diff --git a/guides/v2.1/cloud/docker/docker-development-debug.md b/guides/v2.1/cloud/docker/docker-development-debug.md index c227aa22cbd..f03a41b1746 100644 --- a/guides/v2.1/cloud/docker/docker-development-debug.md +++ b/guides/v2.1/cloud/docker/docker-development-debug.md @@ -33,7 +33,7 @@ generic: - PHP_IDE_CONFIG=serverName=magento_cloud_docker - XDEBUG_CONFIG=remote_host=host.docker.internal env_file: - - ./docker/config.env + - ./.docker/config.env ``` You can change any Xdebug configuration using the`XDEBUG_CONFIG` option. For example, to change the `xdebug.remote_port` option: diff --git a/guides/v2.1/cloud/docker/docker-development.md b/guides/v2.1/cloud/docker/docker-development.md index 19e481147aa..a4453b1a0d7 100644 --- a/guides/v2.1/cloud/docker/docker-development.md +++ b/guides/v2.1/cloud/docker/docker-development.md @@ -76,11 +76,11 @@ The database container is based on the `mariadb:10` image. #### To import a database dump: -Place the SQL file into the `docker/mysql/docker-entrypoint-initdb.d` folder. +Place the SQL file into the `.docker/mysql/docker-entrypoint-initdb.d` folder. The `{{site.data.var.ct}}` package imports and processes the SQL file the next time you build and start the Docker environment using the `docker-compose up` command. -Although it is a more complex approach, you can use GZIP by _sharing_ the `.sql.gz` file using the `docker/mnt` directory and importing it inside the Docker container. +Although it is a more complex approach, you can use GZIP by _sharing_ the `.sql.gz` file using the `.docker/mnt` directory and importing it inside the Docker container. ## Varnish container @@ -90,7 +90,7 @@ The TLS termination proxy container, based on the [magento/magento-cloud-docker ## Sharing data between host machine and container -You can share files easily between your machine and a Docker container by placing the files in the `docker/mnt` directory. You can find the files in the `/mnt` directory the next time you build and start the Docker environment using the `docker-compose up` command. +You can share files easily between your machine and a Docker container by placing the files in the `.docker/mnt` directory. You can find the files in the `/mnt` directory the next time you build and start the Docker environment using the `docker-compose up` command. ## Sendmail service diff --git a/guides/v2.1/cloud/docker/docker-quick-reference.md b/guides/v2.1/cloud/docker/docker-quick-reference.md index 7ef7387abe2..8e53e99b810 100644 --- a/guides/v2.1/cloud/docker/docker-quick-reference.md +++ b/guides/v2.1/cloud/docker/docker-quick-reference.md @@ -50,3 +50,17 @@ php ./vendor/bin/ece-tools list | grep docker | ------------ | ---------------- | ------------------ | Mode | `--mode`, `-m` | production, developer +## bin/docker + +Action | Command +:----- | :------ +Pull latest images | pull +Destroy, re-create and start containers | up +Destroy containers | down +Build application | build +Deploy application | up +Re-build and re-deploy application | redeploy +Connect to bash | bash +Stop containers | stop +Start containers | start +Restart containers | restart From d00333664fcb968d9923fa1e722466b2e3d0cb09 Mon Sep 17 00:00:00 2001 From: hguthrie Date: Tue, 21 May 2019 10:27:32 -0500 Subject: [PATCH 05/33] MAGECLOUD-3545 add release note for exclude list (#4542) --- guides/v2.1/cloud/release-notes/cloud-tools.md | 4 +++- guides/v2.2/cloud/release-notes/cloud-tools.md | 4 +++- guides/v2.3/cloud/release-notes/cloud-tools.md | 4 +++- 3 files changed, 9 insertions(+), 3 deletions(-) diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index df6efceb0ad..398b7a62cdf 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -32,12 +32,14 @@ The release notes include: ## v2002.0.19 -- {:.new}**Environment variable updates**— +- {:.new}**Environment variable updates**— - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). +- {:.fix}Added the `pub/static/.htaccess` file to the exclude list. + ## v2002.0.18 - {:.new}**Docker Updates**— diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index 811163a9a3c..4a1c82f1510 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -32,12 +32,14 @@ The release notes include: ## v2002.0.19 -- {:.new}**Environment variable updates**— +- {:.new}**Environment variable updates**— - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). +- {:.fix}Added the `pub/static/.htaccess` file to the exclude list. + ## v2002.0.18 - {:.new}**Docker Updates**— diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md index 63a95f529b2..aa1ffe2c4f8 100644 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ b/guides/v2.3/cloud/release-notes/cloud-tools.md @@ -32,12 +32,14 @@ The release notes include: ## v2002.0.19 -- {:.new}**Environment variable updates**— +- {:.new}**Environment variable updates**— - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). +- {:.fix}Added the `pub/static/.htaccess` file to the exclude list. + ## v2002.0.18 - {:.new}**Docker Updates**— From efd823d7a8f26ac17137de44a2252565a3b2d113 Mon Sep 17 00:00:00 2001 From: hguthrie Date: Wed, 12 Jun 2019 11:05:34 -0500 Subject: [PATCH 06/33] MAGECLOUD-3258 warm cache with multiple pages (#4720) * MAGECLOUD-3258 warm cache with multiple pages * Improved example using regexp --- .../v2.1/cloud/env/variables-post-deploy.md | 60 +++++++++++++------ .../v2.1/cloud/release-notes/cloud-tools.md | 2 + .../v2.2/cloud/release-notes/cloud-tools.md | 4 +- .../v2.3/cloud/release-notes/cloud-tools.md | 4 +- 4 files changed, 50 insertions(+), 20 deletions(-) diff --git a/guides/v2.1/cloud/env/variables-post-deploy.md b/guides/v2.1/cloud/env/variables-post-deploy.md index c0ddedbec81..146f14f6c59 100644 --- a/guides/v2.1/cloud/env/variables-post-deploy.md +++ b/guides/v2.1/cloud/env/variables-post-deploy.md @@ -20,25 +20,49 @@ stage: - **Default**— `index.php` - **Version**—Magento 2.1.4 and later -Customize the list of pages used to preload the cache in the `post_deploy` stage. +Customize the list of pages used to preload the cache in the `post_deploy` stage. You must configure the post-deploy hook. See the [hooks section][] of the `.magento.app.yaml` file. -```yaml -stage: - post-deploy: - WARM_UP_PAGES: - - "index.php" - - "index.php/customer/account/create" -``` +- **single pages**—Specify a single page to add to the cache. You do not have to indicate the default base URL. The following example caches the `BASE_URL/index.php` page: -You must configure the post-deploy hook. See [hooks section of the `.magento.app.yaml` file]({{ page.baseurl }}/cloud/project/project-conf-files_magento-app.html#hooks). + ```yaml + stage: + post-deploy: + WARM_UP_PAGES: + - "index.php" + ``` -Also, you can configure the cache to preload pages for [multiple domains]({{ page.baseurl }}/cloud/project/project-multi-sites.html). +- **multiple domains**—List multiple URLs. The following example caches pages from two domains: -```yaml -stage: - post-deploy: - WARM_UP_PAGES: - - 'test' - - 'http://example1.com/test' - - 'http://example2.com/test' -``` \ No newline at end of file + ```yaml + stage: + post-deploy: + WARM_UP_PAGES: + - 'http://example1.com/test' + - 'http://example2.com/test' + ``` + +- **multiple pages**—Use the following format to cache multiple pages according to a specific regular expression pattern: + + ```terminal + :: + ``` + + - `entity_type`: Choose `category` or `cms-page` + - `store_id`: Use the ID of the store or an asterisk (\*) for all stores + - `pattern`: Use a `regexp` pattern to filter the URLs or an asterisk (\*) for all pages + + The following example caches all category pages for store 1, any category pages that begin with `car_` and do not end with `html` for store 2, any category pages that begin with `tires_` for store 3, and all `cms` pages: + + ```yaml + stage: + post-deploy: + WARM_UP_PAGES: + - "category:1:*" + - "category:2:|car_.*?\.html|" + - "category:3:|tires_.*|" + - cms-page:*:* + ``` + +[hooks section]: {{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#hooks +[CMS]: https://glossary.magento.com/cms/ +[Content elements]: https://docs.magento.com/m2/ce/user_guide/cms/content-elements.html \ No newline at end of file diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index dded69d6aa1..67c7c807ae8 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -34,6 +34,8 @@ The release notes include: - {:.new}**Environment variable updates**— + - {:.fix}You can configure the **WARM_UP_PAGES** environment variable to cache single pages, multiple domains, and multiple pages. See the expanded definition in the [post-deploy variables]({{page.baseurl}}/cloud/env/variables-post-deploy.html#warm_up_pages) content. + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index 92e26ca58bb..92e783af90f 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -34,7 +34,9 @@ The release notes include: - {:.new}**Environment variable updates**— - - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + - {:.fix}You can configure the **WARM_UP_PAGES** environment variable to cache single pages, multiple domains, and multiple pages. See the expanded definition in the [post-deploy variables]({{page.baseurl}}/cloud/env/variables-post-deploy.html#warm_up_pages) content. + + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{page.baseurl}}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md index 2acf47a3a80..77ec2f218be 100644 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ b/guides/v2.3/cloud/release-notes/cloud-tools.md @@ -34,7 +34,9 @@ The release notes include: - {:.new}**Environment variable updates**— - - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. + - {:.fix}You can configure the **WARM_UP_PAGES** environment variable to cache single pages, multiple domains, and multiple pages. See the expanded definition in the [post-deploy variables]({{page.baseurl}}/cloud/env/variables-post-deploy.html#warm_up_pages) content. + + - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{page.baseurl}}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). From 0e0d588bc2fad9c285f7eb3e8369048bcb506ebe Mon Sep 17 00:00:00 2001 From: Oleksandr Shmyheliuk Date: Thu, 13 Jun 2019 13:16:42 -0500 Subject: [PATCH 07/33] MAGECLOUD-3258: warm cache with multiple pages (#4749) * MAGECLOUD-3258: warm cache with multiple pages * MAGECLOUD-3258: warm cache with multiple pages --- .../v2.1/cloud/env/variables-post-deploy.md | 22 ++++++++++++------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/guides/v2.1/cloud/env/variables-post-deploy.md b/guides/v2.1/cloud/env/variables-post-deploy.md index 146f14f6c59..3fb17594e60 100644 --- a/guides/v2.1/cloud/env/variables-post-deploy.md +++ b/guides/v2.1/cloud/env/variables-post-deploy.md @@ -44,23 +44,29 @@ Customize the list of pages used to preload the cache in the `post_deploy` stage - **multiple pages**—Use the following format to cache multiple pages according to a specific regular expression pattern: ```terminal - :: + :: ``` - `entity_type`: Choose `category` or `cms-page` - - `store_id`: Use the ID of the store or an asterisk (\*) for all stores - - `pattern`: Use a `regexp` pattern to filter the URLs or an asterisk (\*) for all pages + - `pattern|url`: Use a `regexp` pattern or an exact match `url` to filter the URLs, or use an asterisk (\*) for all pages + - `store_id|store_code`: Use the ID or Code of the store or an asterisk (\*) for all stores - The following example caches all category pages for store 1, any category pages that begin with `car_` and do not end with `html` for store 2, any category pages that begin with `tires_` for store 3, and all `cms` pages: + The following example caches: + - all category pages for store with ID 1 + - category page `cars` for store with code `store_en` + - cms page `contact` for all stores + - any category page that contains `car_` and ends with `html` for store with ID 2 + - any category page that contains `tires_` for store with code `store_gb` ```yaml stage: post-deploy: WARM_UP_PAGES: - - "category:1:*" - - "category:2:|car_.*?\.html|" - - "category:3:|tires_.*|" - - cms-page:*:* + - "category:*:1" + - "category:cars:store_en" + - "cms-page:contact:* + - "category:|car_.*?\\.html$|:2" + - "category:|tires_.*|:store_gb" ``` [hooks section]: {{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#hooks From 35812747e13fc2bd858c28c8e9ae6e700c95c7aa Mon Sep 17 00:00:00 2001 From: hguthrie Date: Thu, 20 Jun 2019 10:16:28 -0500 Subject: [PATCH 08/33] MAGECLOUD-3813 ece-tools reference (#4787) * Add link to variable for convenience * MAGECLOUD-3813 ece-tools reference * add repo link * Update ece-tools-reference.md * oops, forgot to update later version * Update from feedback --- _data/toc/cloud-guide.yml | 3 + .../cloud/note-ece-tools-release-info.md | 2 +- guides/v2.1/cloud/bk-cloud.md | 4 +- .../cloud/docker/docker-quick-reference.md | 22 ---- guides/v2.1/cloud/env/variables-cloud.md | 29 ++++- guides/v2.1/cloud/env/variables-deploy.md | 4 +- .../cloud/reference/ece-tools-reference.md | 111 ++++++++++++++++++ .../v2.1/cloud/release-notes/cloud-tools.md | 19 +-- guides/v2.2/cloud/env/variables-cloud.md | 25 +++- guides/v2.2/cloud/env/variables-deploy.md | 4 +- .../cloud/reference/ece-tools-reference.md | 1 + .../v2.2/cloud/release-notes/cloud-tools.md | 19 +-- .../cloud/reference/ece-tools-reference.md | 1 + .../v2.3/cloud/release-notes/cloud-tools.md | 19 +-- 14 files changed, 190 insertions(+), 73 deletions(-) create mode 100644 guides/v2.1/cloud/reference/ece-tools-reference.md create mode 120000 guides/v2.2/cloud/reference/ece-tools-reference.md create mode 120000 guides/v2.3/cloud/reference/ece-tools-reference.md diff --git a/_data/toc/cloud-guide.yml b/_data/toc/cloud-guide.yml index 62ee7fcc099..0da95222453 100644 --- a/_data/toc/cloud-guide.yml +++ b/_data/toc/cloud-guide.yml @@ -38,6 +38,9 @@ pages: - label: Magento Cloud CLI url: /cloud/reference/cli-ref-topic.html + - label: ece-tools package + url: /cloud/reference/ece-tools-reference.html + - label: Git url: /cloud/reference/git-integration.html diff --git a/_includes/cloud/note-ece-tools-release-info.md b/_includes/cloud/note-ece-tools-release-info.md index fd73802ea25..37c894de57a 100644 --- a/_includes/cloud/note-ece-tools-release-info.md +++ b/_includes/cloud/note-ece-tools-release-info.md @@ -1,2 +1,2 @@ -{: .bs-callout .bs-callout-info} +{: .bs-callout-info} For current {{ site.data.var.ece }} release information, see [Release notes for ece-tools]({{ page.baseurl }}/cloud/release-notes/cloud-tools.html). \ No newline at end of file diff --git a/guides/v2.1/cloud/bk-cloud.md b/guides/v2.1/cloud/bk-cloud.md index 9c4d84146d0..5db9eb146f6 100644 --- a/guides/v2.1/cloud/bk-cloud.md +++ b/guides/v2.1/cloud/bk-cloud.md @@ -22,7 +22,7 @@ Amazon Web Services (AWS) powers the underlying Infrastructure as a Service (Iaa ## {{site.data.var.ct}} package -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. +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. @@ -31,3 +31,5 @@ The `{{site.data.var.ct}}` package is a scalable deployment tool that simplifies [Cloud Stack]: {{site.baseurl}}/common/images/cloud/CloudStack.png {: width="804px" height="721px"} + +[ece]: {{page.baseurl}}/cloud/reference/ece-tools-reference.html diff --git a/guides/v2.1/cloud/docker/docker-quick-reference.md b/guides/v2.1/cloud/docker/docker-quick-reference.md index 8ed578fbce3..e70874272df 100644 --- a/guides/v2.1/cloud/docker/docker-quick-reference.md +++ b/guides/v2.1/cloud/docker/docker-quick-reference.md @@ -22,28 +22,6 @@ Resume Docker environment | `docker-compose start` List images | `docker-compose images` List containers and ports | `docker-compose ps`, or `docker ps` -## ece-tools - -Action | Command -:----- | :------ -Builds the docker environment in [production mode]({{page.baseurl}}/cloud/docker/docker-config.html#launch-modes) by default and verifies configured service versions. | `docker:build` -Builds the docker environment in [developer mode]({{page.baseurl}}/cloud/docker/docker-config.html#launch-modes). | `docker:build --mode="developer"` -Convert PHP configuration files to Docker ENV files. | `docker:config:convert` - -The following example lists the `{{site.data.var.ct}}` Docker commands: - -```bash -php ./vendor/bin/ece-tools list | grep docker -``` - -```terminal - docker - docker:build Build docker configuration - docker:build:integration Build test docker configuration - docker:config:convert Convert raw config to .env files configuration -``` -{: .no-copy} - ### Build options | Option | Key | Available values diff --git a/guides/v2.1/cloud/env/variables-cloud.md b/guides/v2.1/cloud/env/variables-cloud.md index ccc637f7042..f4113aa79fa 100644 --- a/guides/v2.1/cloud/env/variables-cloud.md +++ b/guides/v2.1/cloud/env/variables-cloud.md @@ -13,7 +13,7 @@ functional_areas: Environment variables that are specific to {{site.data.var.ece}} use the `MAGENTO_CLOUD_*` prefix: Variable | Description ------------ | --------------- +-------- | --------------- `MAGENTO_CLOUD_APP_DIR` | The absolute path to the application directory. `MAGENTO_CLOUD_APPLICATION` | A base64-encoded JSON object that describes the application. It maps to the `.magento.app.yaml` file content and has subkeys. `MAGENTO_CLOUD_APPLICATION_NAME` | The name of the application configured in the `.magento.app.yaml` file. @@ -25,13 +25,13 @@ Variable | Description `MAGENTO_CLOUD_TREE_ID` | The tree ID for the application, which corresponds to the SHA of the tree in Git. `MAGENTO_CLOUD_VARIABLES` | A base64-encoded JSON object with key-value pairs, such as `"key":"value"`. -{:.bs-callout .bs-callout-warning} +{:.bs-callout-warning} To [add environment variables to override configuration settings]({{ site.baseurl }}/guides/v2.2/config-guide/prod/config-reference-var-name.html) using the [Project Web Interface]({{ page.baseurl }}/cloud/project/project-webint-basic.html#project-conf-env-var), you must prepend the variable name with `env:` as in the following example. ![Environment variable example]({{ site.baseurl }}/common/images/cloud_env_var_example.png) Since values can change over time, it is best to inspect the variable at runtime and use it to configure your application. For example, we use the `MAGENTO_CLOUD_RELATIONSHIPS` variable to retrieve environment-related relationships as follows: -```php +```php?start_inline=1 /** * Get relationships information from MagentoCloud environment variable. * @@ -41,4 +41,25 @@ Since values can change over time, it is best to inspect the variable at runtime { return json_decode(base64_decode($_ENV["MAGENTO_CLOUD_RELATIONSHIPS"]), true); } -``` \ No newline at end of file +``` + +#### To view environment variables: + +You can use the `env:config:show` command from [the `{{site.data.var.ct}}` package]({{page.baseurl}}/cloud/reference/ece-tools-reference.html) to show a list of variables for the current environment. + +```bash +php ./vendor/bin/ece-tools env:config:show variables +``` + +Sample output for the `variables` option: + +```terminal +Magento Cloud Environment Variables: ++-----------------------------------+----------------------------------+ +| Variable name | Value | ++-----------------------------------+----------------------------------+ +| ADMIN_EMAIL | magentoadmin@company.com | +| ADMIN_PASSWORD | 123123q | ++-----------------------------------+----------------------------------+ +``` +{: .no-copy} \ No newline at end of file diff --git a/guides/v2.1/cloud/env/variables-deploy.md b/guides/v2.1/cloud/env/variables-deploy.md index 51a925e2c7a..f2acb979763 100644 --- a/guides/v2.1/cloud/env/variables-deploy.md +++ b/guides/v2.1/cloud/env/variables-deploy.md @@ -332,7 +332,7 @@ stage: - **Default**—_Not set_ - **Version**—Magento 2.1.4 and later -You can configure specific locales per theme as long as the theme is not excluded using the `SCD_EXCLUDE_THEMES` variable during deployment. This is ideal if you want to speed up the deployment process by reducing the amount of unnecessary theme files. For example, you can deploy the _magento/backend_ theme in English and a custom theme in other languages. +You can configure specific locales per theme as long as the theme is not excluded using the [`SCD_EXCLUDE_THEMES` variable](#scd_exclude_themes) during deployment. This is ideal if you want to speed up the deployment process by reducing the amount of unnecessary theme files. For example, you can deploy the _magento/backend_ theme in English and a custom theme in other languages. The following example deploys the `Magento/backend` theme with three locales: @@ -461,7 +461,7 @@ stage: - **Default**—`true` - **Version**—Magento 2.1.4 and later -Generates symlinks for static content. This setting is vital in the Pro Production environment for the three-node cluster. When this variable is set to `false`, it must copy every file during the deployment, which increases deployment time. +Generates symlinks for static content. This setting is vital in the Pro Production environment for the three-node cluster. When this variable is set to `false`, it must copy every file during the deployment, which increases deployment time. Setting the [`SCD_ON_DEMAND` variable]({{page.baseurl}}/cloud/env/variables-global.html#scd_on_demand) to `true` disables this variable. If you generate static content during the build phase, it creates a symlink to the content folder. If you generate static content during the deploy phase, it writes directly to the content folder. diff --git a/guides/v2.1/cloud/reference/ece-tools-reference.md b/guides/v2.1/cloud/reference/ece-tools-reference.md new file mode 100644 index 00000000000..2176b8583b3 --- /dev/null +++ b/guides/v2.1/cloud/reference/ece-tools-reference.md @@ -0,0 +1,111 @@ +--- +group: cloud-guide +title: ece-tools reference +functional_areas: + - Cloud +--- + +The `{{site.data.var.ct}}` package is a set of scripts and tools designed to manage and deploy {{site.data.var.ece}} projects. The `{{site.data.var.ct}}` package simplifies many {{site.data.var.ece}} processes, such as Docker environment deployment, cron management, and project verification. You can view and contribute to the open-source [ece-tools repository on Github](https://github.com/magento/ece-tools). + +{% include cloud/note-ece-tools-package.md %} + +The `{{site.data.var.ct}}` package is compatible with {{site.data.var.ee}}—starting with version 2.1.4—and contains scripts and {{site.data.var.ece}} commands designed to help manage your code and automatically build and deploy your projects. + +#### To list the available `{{site.data.var.ct}}` commands: + +```bash +php ./vendor/bin/ece-tools list +``` + +## Build and deploy + +The `{{site.data.var.ct}}` package performs operations for the build, deploy, and post-deploy stages for launching your {{site.data.var.ece}} application. By default, these commands are in the [hooks property][hooks] of the `.magento.app.yaml` configuration file. + +## Docker configuration generator + +The `{{site.data.var.ct}}` package provides all the commands necessary to [launch a Docker development environment]({{page.baseurl}}/cloud/docker/docker-config.html). + +Command | Action +:------ | :------ +`docker:build` | Builds the docker environment in [production mode][mode] by default and verifies configured service versions. +`docker:build --mode="developer"` | Builds the docker environment in [developer mode][mode]. +`docker:config:convert` | Convert PHP configuration files to Docker ENV files. + +The following example lists the `{{site.data.var.ct}}` Docker commands: + +```bash +php ./vendor/bin/ece-tools list | grep docker +``` + +Sample response: + +```terminal + docker + docker:build Build docker configuration + docker:config:convert Convert raw config to .env files configuration +``` +{: .no-copy} + +## Services, routes, and variables + +You can use the `{{site.data.var.ct}}` package to display detailed information about the Base64-encoded [Cloud variables][cloudvar] used in any Cloud environment. The following command shows all services, routes, and variables. + +```bash +php ./vendor/bin/ece-tools env:config:show +``` + +To display a specific set of information, use the following format: + +```bash +php ./vendor/bin/ece-tools env:config:show