Merge branch 'master' into update-redis-woocommerce

Author: TimVNL

docs/ecommerce-applications/magento-2/how-to-configure-redis-for-magento-2.md

@@ -134,6 +134,7 @@ After enabling the second Redis instance you need to change the configured Redis
 ```console
 $ cd /data/web/magento2
 $ bin/magento setup:config:set \
+    --session-save=redis \
     --session-save-redis-port=6378 \
     --session-save-redis-db=0
 ```
@@ -149,15 +150,15 @@ Furthermore you need to add the following line to your crontab:
 To verify whether your configuration is working properly, first clear your session store:
 
 ```console
-$ rm /data/web/public/var/sessions/*
+$ rm /data/web/magento2/var/sessions/*
 ```
 
 Now open the site in your browser and hit `F5` a few times or log in to the admin panel. If all is well, no additional sessions files should be written to `/data/web/var/sessions`, but instead to the Redis database:
 
 To verify whether your configuration is working properly, first clear your session store:
 
 ```console
-$ redis-cli -n 2 keys '*'
+$ redis-cli -p 6378 keys '*'
 ```
 
 ## Troubleshooting

docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md

@@ -0,0 +1,43 @@
+______________________________________________________________________
+
+myst:
+html_meta:
+description: 'Find out here how to order a domain.'
+redirect_from:
+
+- /en/getting-started/how-to-order/how-to-order-a-domain-presence-plan/
+- /getting-started/how-to-order/how-to-order-a-domain-presence-plan.html
+
+______________________________________________________________________
+
+<!-- source: https://support.hypernode.com/en/getting-started/how-to-order/how-to-order-a-domain-presence-plan/ -->
+
+# How to Order a Domain
+
+To order a domain you will need a Hypernode as the domain needs to be linked to it during the ordering process.
+
+## How to Order
+
+To order a domain, please follow the steps below:
+
+1. Log into the [Hypernode control panel](https://my.hypernode.com/domain/)
+1. Go to the 'Domains' tab and press Order domain
+1. Enter the domain name that you want to register with/transfer to Hypernode.
+1. When you want to transfer a domain, our ordering system will recognize you want to order an existing domain and will ask you if you want to transfer the domain or only manage the DNS. These steps will not initiate a transfer right away. If you want to transfer the domain to Hypernode you can choose the option 'Transfer to Hypernode'.
+1. Make a selection of the Hypernode it needs to link to.
+1. Select the Legal owner or fill in the information.
+1. After completing your order you can either transfer your domain with the authorisation token or manage the DNS after providing the domain registrar with the new nameservers.
+
+## FAQ
+
+**What extensions do you offer?**
+
+A complete list of extensions we offer can be found [here](../../services/domain-procedures/which-tlds-does-hypernode-offer.md).
+
+**How can I transfer my domain?**
+
+You can read a detailed description of the step-by-step plan [here](../../services/domain-procedures/how-to-use-domains-in-the-control-panel.md#transfer-an-existing-domain-to-hypernode).
+
+**How can I order an SSL certificate?**
+
+You can read a detailed description of the step-by-step plan [here](../../hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#buy-an-ssl-certificate-via-hypernode-recommended).

docs/getting-started/how-to-order/how-to-order-a-domain.md

@@ -97,6 +97,32 @@ return $configuration;
 
 This automatically enables split static deployment for optimal build performance.
 
+### High-Performance Static Content Deployment (Experimental)
+
+```{warning}
+This feature is experimental and may cause unexpected issues. Test thoroughly in a staging environment before using in production.
+```
+
+For Hyvä-based stores, you can enable a Go-based static content deployer that is **230-380x faster** than Magento's native `setup:static-content:deploy` command. Typical deployment times drop from ~115 seconds to ~0.3-0.5 seconds.
+
+```php
+<?php
+
+namespace Hypernode\DeployConfiguration;
+
+$configuration = new ApplicationTemplate\Magento2(['nl_NL', 'en_US']);
+
+$configuration->setMagentoThemes([
+    'Vendor/theme' => 'nl_NL en_US',
+]);
+
+$configuration->enableHighPerformanceStaticDeploy();
+
+return $configuration;
+```
+
+For more information, see the [Hypernode Deploy v4.8.0 changelog](https://changelog.hypernode.com/hypernode-deploy-v4-8-0/).
+
 ### Defining custom steps
 
 You potentially need to add custom steps to the deployment, for example to build npm assets or do server actions after deployment.

docs/hypernode-deploy/applications/config-for-magento-2.md

@@ -61,6 +61,7 @@ jobs:
     - run: hypernode-deploy build -vvv
       env:
         SSH_PRIVATE_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
+        DEPLOY_COMPOSER_AUTH: ${{ secrets.DEPLOY_COMPOSER_AUTH }}
     - name: archive production artifacts
       uses: actions/upload-artifact@v4
       with:

docs/hypernode-deploy/pipelines/github-actions.md

@@ -37,9 +37,9 @@ set $storecode "example_storecode";
 ```
 
 ```{important}
-If you have a multistore, with hypernode-manage-vhost enabled AND you are using Varnish.
-You'd have to prefix the file with `varnish` instead of `server`, like `varnish.storecode`.
-This way these multistore requests will go through varnish and will then be rewritten accordingly with the `varnish.storecode` configuration.
+If you have a multistore with `hypernode-manage-vhost` enabled **and** you are using Varnish, you need to prefix the file with `varnish` instead of `server`, like `varnish.storecode`. This way multistore requests will go through Varnish and be rewritten accordingly using the `varnish.storecode` configuration.
+
+This does **not** apply if your Hypernode is running behind a load balancer (e.g. a cluster setup). In that case, you should keep using `server.storecode` instead.
 ```
 
 ### Use a different Store Type

docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md

@@ -128,3 +128,48 @@ rewrite ^/fr/(.*)$ http://yourshop.fr/$1 permanent;
 This will also maintain subfolders and query strings (such as <http://yourshop.com/fr/subfolder?arguments>).
 
 If the move is only temporary, you should use redirect instead of permanent.
+
+## Redirects using mapping
+
+The map directive allows you to define conditional logic outside of your main server block. This keeps your configuration:
+
+- Easier to read
+- More scalable for large numbers of redirects
+- More efficient than stacking multiple if statements
+
+You will define your redirects in two parts:
+
+1. A mapping configuration (placed in an `/data/web/nginx/http.*` file)
+1. A rewrite rule (placed in a `/data/web/nginx/server.*` file)
+
+Step 1: Define the Redirect Mapping
+
+`/data/web/nginx/http.*`
+
+```nginx
+map $uri $out_redirect {
+~/the-location-you-want-to-redirect /new-location;
+}
+```
+
+You can expand this map with multiple rules:
+
+```nginx
+map $uri $out_redirect {
+~/old-page /new-page;
+~/blog/(.*) /articles/$1;
+~/deprecated /;
+}
+```
+
+Step 2: Apply the Redirect in the Server Block
+
+`/data/web/nginx/server.*`
+
+```nginx
+if ($out_redirect) {
+rewrite 301 $out_redirect;
+}
+```
+
+Using `map` for redirects in NGINX provides a clean, scalable, and efficient way to manage URL rewrites. By separating logic from execution, your configuration remains easy to maintain even as the number of redirects grows.

docs/hypernode-platform/nginx/how-to-use-nginx.md

@@ -0,0 +1,18 @@
+---
+myst:
+  html_meta:
+    description: This table of contents gives you a summary of all Hypernode platform
+      knowledge base articles that include information about redis.
+    title: Redis | Hypernode platform
+---
+
+# Redis
+
+```{toctree}
+---
+caption: Table of Contents
+maxdepth: 1
+glob:
+---
+redis/*
+```

docs/hypernode-platform/redis.md

@@ -0,0 +1,101 @@
+---
+myst:
+  html_meta:
+    description: Changing the Redis eviction policy on Hypernode with hypernode-systemctl.
+      Learn which policies are available and how to verify the active Redis maxmemory-policy.
+    title: Changing the Redis eviction policy on Hypernode
+---
+
+# Changing the Redis eviction policy
+
+You can change the Redis `maxmemory-policy` with `hypernode-systemctl settings redis_eviction_policy`. This policy determines which keys Redis can evict when memory is full.
+
+## Available policies
+
+The following values are supported for `redis_eviction_policy`:
+
+- `noeviction`
+- `allkeys-lru`
+- `allkeys-lfu`
+- `allkeys-random`
+- `volatile-lru`
+- `volatile-lfu`
+- `volatile-ttl`
+- `volatile-random`
+
+```{infomation}
+By default, Redis on Hypernode uses the `volatile-lru` eviction policy.
+```
+
+## Check the current policy
+
+To view the current Redis eviction policy:
+
+```bash
+hypernode-systemctl settings redis_eviction_policy
+```
+
+## Change the policy
+
+Use the following command to change the Redis eviction policy:
+
+```bash
+hypernode-systemctl settings redis_eviction_policy <policy>
+```
+
+For example:
+
+```bash
+hypernode-systemctl settings redis_eviction_policy allkeys-lru
+```
+
+## Policy explanation
+
+### `noeviction`
+
+Redis will not evict any keys when memory is full. New write operations
+that require memory will fail.
+
+### `allkeys-lru`
+
+Redis can evict any key and removes the least recently used keys first.
+
+### `allkeys-lfu`
+
+Redis can evict any key and removes the least frequently used keys first.
+
+### `allkeys-random`
+
+Redis can evict any key and removes keys at random.
+
+### `volatile-lru`
+
+Redis only evicts keys with an expiration time and removes the least
+recently used keys first.
+
+This is the default policy on Hypernode.
+
+### `volatile-lfu`
+
+Redis only evicts keys with an expiration time and removes the least
+frequently used keys first.
+
+### `volatile-ttl`
+
+Redis only evicts keys with an expiration time and prefers keys that will
+expire soonest.
+
+### `volatile-random`
+
+Redis only evicts keys with an expiration time and removes those keys at
+random.
+
+## Important considerations
+
+- Eviction only takes place when Redis reaches its memory limit.
+- Policies starting with `allkeys-` can evict any key, including keys without a TTL.
+- Even with an `allkeys-` policy, Redis can still run into memory pressure if keys cannot be evicted fast enough to keep up with writes.
+- Setting a TTL on cache keys is still recommended, even when using an `allkeys-` policy.
+- Policies starting with `volatile-` only apply to keys with a TTL.
+- If not enough keys have a TTL, Redis may not be able to evict enough data with a `volatile-` policy, and write operations may fail.
+- Changing the policy does not remove existing keys immediately.

docs/hypernode-platform/redis/how-to-change-redis-eviction-policy.md

@@ -6,6 +6,7 @@ myst:
     title: How to flush the Redic cache? | Hypernode
 redirect_from:
   - /en/hypernode/tools/how-to-flush-the-redis-cache/
+  - /hypernode-platform/tools/how-to-flush-the-redis-cache/
 ---
 
 <!-- source: https://support.hypernode.com/en/hypernode/tools/how-to-flush-the-redis-cache/ -->