Merge pull request #2320 from spryker/Redirct-fixes

Redirect fixes on a couple of pages
spryker · Nov 22, 2023 · d069346 · d069346
2 parents bfa5df8 + eea473f
commit d069346
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 8 deletions.
diff --git a/docs/scos/dev/architecture/module-api/performance-and-scalability.md b/docs/scos/dev/architecture/module-api/performance-and-scalability.md
@@ -22,6 +22,7 @@ redirect_from:
   - /v2/docs/en/performance-scalability
   - /v1/docs/performance-scalability
   - /v1/docs/en/performance-scalability
+  - /docs/scos/dev/setup/scalability.html
 related:
   - title: Semantic versioning - major vs. minor vs. patch release
     link: docs/scos/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.html

diff --git a/.../scos/dev/guidelines/performance-guidelines/front-end-performance-guidelines.md b/.../scos/dev/guidelines/performance-guidelines/front-end-performance-guidelines.md
@@ -13,6 +13,7 @@ redirect_from:
   - /v6/docs/front-end-performance-guidelines
   - /v6/docs/en/front-end-performance-guidelines
   - /docs/scos/dev/guidelines/front-end-performance-guidelines.html
+  - /docs/scos/dev/tuning-up-performance/202204.0/performance-guidelines.html#frontend-performance
 related:
   - title: General performance guidelines
     link: docs/scos/dev/guidelines/performance-guidelines/general-performance-guidelines.html

diff --git a/docs/scos/dev/guidelines/performance-guidelines/general-performance-guidelines.md b/docs/scos/dev/guidelines/performance-guidelines/general-performance-guidelines.md
@@ -23,6 +23,7 @@ redirect_from:
   - /v1/docs/performance-guidelines
   - /v1/docs/en/performance-guidelines
   - /docs/scos/dev/guidelines/performance-guidelines.html
+  - /docs/scos/dev/tuning-up-performance/202204.0/performance-guidelines.html
 related:
   - title: Architecture performance guidelines
     link: docs/scos/dev/guidelines/performance-guidelines/architecture-performance-guidelines.html
@@ -56,14 +57,14 @@ For performance reasons, always use the newest stable version of PHP, as every n
 
 Make sure that Opcache is activated and properly configured:
 
-| CONFIGURATION  | PURPOSE   | PRODUCTION | DEVELOPMENT |
-| ------------- | ----------------- | ---------- | ----------- |
-| `opcache.enable`    | Activates Opcache for web requests. Most developers disable this on development environments to avoid outdated code in caches. However, you can also activate it and check for changed files via `validate_timestamps` and `revalidate_freq` configurations. | 1     | 0   |
-| `opcache.enable_cli`   | Activates Opcache for console commands.     | 1    | 0   |
-| `opcache.max_accelerated_files` | Spryker and all the used open-source libraries contain a lot of PHP classes, so this value should be high (max is 100k). | ?  | 8192  |
-| `opcache.memory_consumption`  | To avoid an automatic reset of the Opcache, these values must be high enough. You can look into the PHP info (for exaample, in Zed, browse to `/maintenance/php-info`) to see the current usage. You can count the number of classes in your codebase to get an idea of a good value. | ?       |             |
-| `opcache.validate_timestamps`  | Boolean values that activate the check for the updated code. This check is time-consuming and must be disabled in production environments. However, you need to flush the cache during deployments—for example, by restarting PHP. | 0  | 1  |
-| `opcache.revalidate_freq`  | Configures the frequency of checks if enabled by the `validate_timestamps` configuration. *0* means *on every request*,  which is recommended for development environments if you want to program with activated Opcache.	0	0 | 0  | 0  |
+| CONFIGURATION                   | PURPOSE                                                                                                                                                                                                                                                                               | PRODUCTION | DEVELOPMENT |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ----------- |
+| `opcache.enable`                | Activates Opcache for web requests. Most developers disable this on development environments to avoid outdated code in caches. However, you can also activate it and check for changed files via `validate_timestamps` and `revalidate_freq` configurations.                          | 1          | 0           |
+| `opcache.enable_cli`            | Activates Opcache for console commands.                                                                                                                                                                                                                                               | 1          | 0           |
+| `opcache.max_accelerated_files` | Spryker and all the used open-source libraries contain a lot of PHP classes, so this value should be high (max is 100k).                                                                                                                                                              | ?          | 8192        |
+| `opcache.memory_consumption`    | To avoid an automatic reset of the Opcache, these values must be high enough. You can look into the PHP info (for exaample, in Zed, browse to `/maintenance/php-info`) to see the current usage. You can count the number of classes in your codebase to get an idea of a good value. | ?          |             |
+| `opcache.validate_timestamps`   | Boolean values that activate the check for the updated code. This check is time-consuming and must be disabled in production environments. However, you need to flush the cache during deployments—for example, by restarting PHP.                                                    | 0          | 1           |
+| `opcache.revalidate_freq`       | Configures the frequency of checks if enabled by the `validate_timestamps` configuration. *0* means *on every request*,  which is recommended for development environments if you want to program with activated Opcache.	0	0                                                         | 0          | 0           |
 
 ```php
 zend_extension=opcache.so

diff --git a/docs/scos/dev/guidelines/performance-guidelines/performance-guidelines.md b/docs/scos/dev/guidelines/performance-guidelines/performance-guidelines.md
@@ -3,6 +3,7 @@ title: Performance guidelines
 description: This guidelines explains how to optimize the performance of your website.
 template: concept-topic-template
 redirect_from:
+  - /docs/scos/dev/tuning-up-performance/202204.0/performance-guidelines.html
 ---
 
 Performance guidelines help you analyze and optimize performance of your website from different perspectives: