Replace absolute links with site variables

Author: dshevtsov

src/_includes/cloud/error-codes.md

@@ -46,7 +46,7 @@ Critical errors indicate a problem with the {{ site.data.var.ece }} project conf
 | 104 |  | Failed to parse the `.magento.env.yaml` file | Configuration is not defined in the `./vendor/magento/ece-tools/config/schema.yaml` file. Check that the config variable name is correct, and that it is defined. |
 | 105 |  | Unable to read the `.magento.env.yaml` file | Unable to read the `./.magento.env.yaml` file. Check file permissions. |
 | 106 |  | Unable to read the `.schema.yaml` file |  |
-| 107 | pre-deploy: clean-redis-cache | Failed to clean the Redis cache | Failed to clean the Redis cache. Check that the Redis cache configuration is correct and that the Redis service is available. See [Setup Redis service](https://devdocs.magento.com/cloud/project/services-redis.html). |
+| 107 | pre-deploy: clean-redis-cache | Failed to clean the Redis cache | Failed to clean the Redis cache. Check that the Redis cache configuration is correct and that the Redis service is available. See [Setup Redis service]({{ site.baseurl }}/cloud/project/services-redis.html). |
 | 108 | pre-deploy: set-production-mode | Command `/bin/magento maintenance:enable` failed | Check the `cloud.log` for more information. For more detailed command output, add the `VERBOSE_COMMANDS: '-vvv'` option to the `.magento.env.yaml` file. |
 | 109 | validate-config | Incorrect database configuration | Check that the `DATABASE_CONFIGURATION` environment variable is configured correctly. |
 | 110 | validate-config | Incorrect session configuration | Check that the `SESSION_CONFIGURATION` environment variable is configured correctly. The configuration must contain at least the `save` parameter. |
@@ -70,7 +70,7 @@ Critical errors indicate a problem with the {{ site.data.var.ece }} project conf
 | 128 | disable-maintenance-mode | Command `/bin/magento maintenance:disable` failed | Check the `cloud.log` for more information. Add `VERBOSE_COMMANDS: '-vvv'` into `.magento.env.yaml` for more detailed command output. |
 | 129 | install-update: reset-password | Unable to read reset password template |  |
 | 130 | install-update: cache_type | Command failed: `php ./bin/magento cache:enable` | Command `php ./bin/magento cache:enable` runs only when Magento was installed but `./app/etc/env.php` file was absent or empty at the beginning of the deployment. Check the `cloud.log` for more information. Add `VERBOSE_COMMANDS: '-vvv'` into `.magento.env.yaml` for more detailed command output. |
-| 131 | install-update | The `crypt/key`  key value does not exist in the `./app/etc/env.php` file or the `CRYPT_KEY` cloud environment variable | This error occurs if the `./app/etc/env.php` file is not present when Magento deployment begins, or if the `crypt/key` value is undefined. If you migrated the database from another environment, retrieve the crypt key value from that environment. Then, add the value to the [CRYPT_KEY](https://devdocs.magento.com/cloud/env/variables-deploy.html#crypt_key) cloud environment variable in your current environment. See [Add the Magento encryption key](https://devdocs.magento.com/cloud/setup/first-time-setup-import-import.html#encryption-key). If you accidentally removed the `./app/etc/env.php` file, use the following command to restore it from the backup files created from a previous deployment: `./vendor/bin/ece-tools backup:restore` CLI command ." |
+| 131 | install-update | The `crypt/key`  key value does not exist in the `./app/etc/env.php` file or the `CRYPT_KEY` cloud environment variable | This error occurs if the `./app/etc/env.php` file is not present when Magento deployment begins, or if the `crypt/key` value is undefined. If you migrated the database from another environment, retrieve the crypt key value from that environment. Then, add the value to the [CRYPT_KEY]({{ site.baseurl }}/cloud/env/variables-deploy.html#crypt_key) cloud environment variable in your current environment. See [Add the Magento encryption key]({{ site.baseurl }}/cloud/setup/first-time-setup-import-import.html#encryption-key). If you accidentally removed the `./app/etc/env.php` file, use the following command to restore it from the backup files created from a previous deployment: `./vendor/bin/ece-tools backup:restore` CLI command ." |
 | 132 |  | Can not connect to the Elasticsearch service | Check for valid Elasticsearch credentials and verify that the service is running |
 | 133 | validate-config | Remove Magento Braintree module configuration which is no longer supported in Magento 2.4 and later versions. | Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree support, use an official Braintree Payments extension from the Commerce Marketplace instead. |
 | 134 | validate-config | Magento 2.4.0 requires Elasticsearch service to be installed | Install Elasticsearch service |

src/_includes/layout/header-scripts.html

@@ -18,12 +18,12 @@
         label: "Functional areas",
         attribute: "functional_areas"
       }],
-      baseUrl: "https://devdocs.magento.com"
+      baseUrl: "{{ site.baseurl }}"
     },
     {
       label: "User Guide",
       name: "merchdocs",
-      baseUrl: "https://docs.magento.com/user-guide"
+      baseUrl: "{{ site.user_guide_url }}"
     },
     {
       label: "Commerce Reporting User Guide",

src/cloud/cdn/cloud-vcl-custom-snippets.md

@@ -46,7 +46,7 @@ You can create and manage custom VCL snippets from the Admin UI or by using the
 -  [Admin UI](#manage-custom-vcl-snippets-from-the-magento-admin-ui)—We recommend using the Admin UI to manage custom VCL snippets because it automates the process to validate and upload the custom snippet and apply your changes to the Fastly service configuration. Additionally, you can view and edit the custom VCL snippets added to the Fastly service configuration from the Admin UI.
 
 {:.bs-callout-info}
-You must use the Fastly API to [delete custom VCL snippets](https://devdocs.magento.com/cloud/cdn/cloud-vcl-custom-snippets.html#manage-vcl), or you can delete the contents of the snippet in the  Admin UI and upload an empty snippet. See [Delete a custom snippet](https://devdocs.magento.com/cloud/cdn/fastly-vcl-badreferer.html#delete-the-custom-vcl-snippet).
+You must use the Fastly API to [delete custom VCL snippets]({{ site.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-vcl), or you can delete the contents of the snippet in the  Admin UI and upload an empty snippet. See [Delete a custom snippet]({{ site.baseurl }}/cloud/cdn/fastly-vcl-badreferer.html#delete-the-custom-vcl-snippet).
 
 -  [Fastly API](#manage-custom-vcl-snippets-using-the-api)—Manage custom VCL snippets using the API if you cannot access the Admin UI. For example, if the site is down and you need to troubleshoot the Fastly service configuration or add a custom VCL snippet. Additionally, some operations can only be completed using the API, for example reactivating an older VCL version or viewing all the VCL snippets included in a specified the VCL version. See [API quick reference for VCL snippets](#manage-vcl).
 

src/cloud/cdn/configure-fastly.md

@@ -217,7 +217,7 @@ To update your DNS configuration for development:
       ```
 
    {:.bs-callout-info}
-   As an alternative to using the Magento CLI, you can update the Base URL from the [Admin](https://docs.magento.com/user-guide/stores/store-urls.html#configure-the-base-url).
+   As an alternative to using the Magento CLI, you can update the Base URL from the [Admin]({{ site.user_guide_url }}/stores/store-urls.html#configure-the-base-url).
 
 1. Restart web browser.
 

src/cloud/docker/docker-config-blackfire-io.md

@@ -106,7 +106,7 @@ To use Blackfire.io for performance testing in Cloud Docker:
 <!--Link definitions-->
 [Blackfire.io for {{site.data.var.ece}}]: https://blackfire.io/magento
 [Blackfire documentation]: https://support.blackfire.io/en/collections/145130-blackfire-on-magento-cloud.html
-[build or service configuration options]: https://devdocs.magento.com/cloud/docker/docker-quick-reference.html
-[Extend the Docker configuration]: https://devdocs.magento.com/cloud/docker/docker-extend.html#specify-docker-build-sources
+[build or service configuration options]: {{ site.baseurl }}/cloud/docker/docker-quick-reference.html
+[Extend the Docker configuration]: {{ site.baseurl }}/cloud/docker/docker-extend.html#specify-docker-build-sources
 [file synchronization options]: {{site.baseurl}}/cloud/docker/docker-syncing-data.html
 [Launch Docker in developer mode]: {{site.baseurl}}/cloud/docker/docker-mode-developer.html

src/cloud/docker/docker-config-sources.md

@@ -344,10 +344,10 @@ services:
 
 <!--Link definitions-->
 
-[hooks]: https://devdocs.magento.com/cloud/project/magento-app-properties.html#hooks
+[hooks]: {{ site.baseurl }}/cloud/project/magento-app-properties.html#hooks
 [.magento.app.yaml]: {{site.baseurl}}/cloud/project/magento-app.html
 [services.yaml]: {{site.baseurl}}/cloud/project/services.html
-[mounts]: https://devdocs.magento.com/cloud/project/magento-app-properties.html#mounts
+[mounts]: {{ site.baseurl }}/cloud/project/magento-app-properties.html#mounts
 [available services]: {{site.baseurl}}/cloud/project/services.html#service-versions
 [Override configuration]: {{site.baseurl}}/cloud/docker/docker-quick-reference.html#override-configuration
 [Service configuration options]: {{site.baseurl}}/cloud/docker/docker-containers.html#service-configuration-options

src/cloud/docker/docker-containers-service.md

@@ -202,7 +202,7 @@ docker-compose run --rm redis redis-cli -h redis
 **Docker base image**: [selenium/standalone-chrome/](https://hub.docker.com/r/selenium/standalone-chrome), based on the [selenium/standalone-chrome/](https://hub.docker.com/r/selenium/standalone-chrome/h) Docker image<br/>
 **Ports exposed**: `4444`<br/>
 
-The Selenium container enables the [Magento Functional Testing Framework (MFTF)](https://devdocs.magento.com/mftf/docs/introduction.html) for application testing in the Cloud Docker environment. See [Magento application testing]({{site.baseurl}}/cloud/docker/docker-test-app-mftf.html).
+The Selenium container enables the [Magento Functional Testing Framework (MFTF)]({{ site.baseurl }}/mftf/docs/introduction.html) for application testing in the Cloud Docker environment. See [Magento application testing]({{site.baseurl}}/cloud/docker/docker-test-app-mftf.html).
 
 ## Test container
 

src/cloud/docker/docker-extend.md

@@ -110,7 +110,6 @@ To add a new PHP extension:
        ],
        ...
       ```
-      {:.no-copy}
 
       In this case, the `bcmath` PHP core extension installs from `docker-php-source` images.
 
@@ -279,9 +278,9 @@ BASH
 ...
 ```
 
-[Docker build sources]: https://devdocs.magento.com/cloud/docker/docker-extend.html#specify-docker-build-sources
+[Docker build sources]: {{ site.baseurl }}/cloud/docker/docker-extend.html#specify-docker-build-sources
 [ExtensionResolver.php]: https://github.com/magento/magento-cloud-docker/tree/develop/src/Compose/Php
 [PECL]: https://pecl.php.net/
 [PHP, Docker Official Images]: https://hub.docker.com/_/php
 [multiple compose files]: https://docs.docker.com/compose/reference/overview/#specifying-multiple-compose-files
-[service versions]: https://devdocs.magento.com/cloud/docker/docker-containers.html#service-containers
+[service versions]: {{ site.baseurl }}/cloud/docker/docker-containers.html#service-containers

src/cloud/docker/docker-manage-database.md

@@ -47,7 +47,6 @@ return [
             ],
         ],
 ```
-{:.no-copy}
 
 {:.procedure}
 To connect to the database using Docker commands:
@@ -84,7 +83,6 @@ To connect to the database using Docker commands:
    | 10.0.38-MariaDB-1~xenial |
    +--------------------------+
    ```
-   {:.no-copy}
 
 {:.procedure}
 To connect to the database port:
@@ -108,7 +106,6 @@ To connect to the database port:
    magento-cloud_db-sales_1    docker-entrypoint.sh mysqld      Up       0.0.0.0:32874->3306/tcp
 
    ```
-   {:.no-copy}
 
 1. Connect to the database with port information from the previous step.
 
@@ -140,7 +137,6 @@ To connect to the database port:
    | 10.0.38-MariaDB-1~xenial |
    +--------------------------+
    ```
-   {: .no-copy}
 
 [db-image]: https://hub.docker.com/_/mariadb
 
@@ -193,6 +189,6 @@ See [Docker service containers][Docker database container] for details about the
 <!--Link definitions-->
 
 [Add the encryption key]: {{ site.baseurl}}/cloud/setup/first-time-setup-import-import.html#encryption-key
-[Docker database container]: https://devdocs.magento.com/cloud/docker/docker-containers-service.html#database-container
+[Docker database container]: {{ site.baseurl }}/cloud/docker/docker-containers-service.html#database-container
 [mysqldump]: https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html
 [Service configuration options]: {{ site.baseurl }}/cloud/docker/docker-containers.html#service-configuration-options

src/cloud/live/site-launch-checklist.md

@@ -82,7 +82,7 @@ To update DNS configuration for site launch:
       ```
 
    {:.bs-callout-info}
-   You can also update the Base URL from the [Admin](https://docs.magento.com/user-guide/stores/store-urls.html#configure-the-base-url).
+   You can also update the Base URL from the [Admin]({{ site.user_guide_url }}/stores/store-urls.html#configure-the-base-url).
 
 1. Wait a few minutes for the site to update.