Merge branch 'master' into docsearch-earch

Author: poespas

.github/workflows/cleanup_acceptance.yaml

@@ -7,7 +7,7 @@ on:
 jobs:
   cleanup:
     runs-on: ubuntu-latest
-    container: quay.io/hypernode/deploy:latest-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     environment: acceptance
     steps:
       - uses: actions/checkout@v2

.github/workflows/deploy.yaml

@@ -12,7 +12,7 @@ env:
 jobs:
   build:
     runs-on: ubuntu-latest
-    container: quay.io/hypernode/deploy:latest-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v3
         with:
@@ -47,7 +47,7 @@ jobs:
       name: acceptance
       url: ${{ steps.get_brancher_hostname.outputs.BRANCHER_URL }}
     if: github.ref != 'refs/heads/master'
-    container: quay.io/hypernode/deploy:latest-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v3
         with:
@@ -102,7 +102,7 @@ jobs:
       name: production
       url: https://docs.hypernode.io
     if: github.ref == 'refs/heads/master'
-    container: quay.io/hypernode/deploy:latest-php8.3-node20
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v3
       - name: download build artifact

bin/watch

@@ -7,7 +7,7 @@ from time import sleep
 
 
 def build_docs():
-    subprocess.check_call("bin/build_docs")
+    subprocess.run("bin/build_docs")
 
 
 def refresh_assets():

docs/conf.py

@@ -21,13 +21,14 @@
 
 # -- Project information -----------------------------------------------------
 
-project = "Docs"
+project = "Documentation"
+html_title = "Hypernode Documentation"
 current_year = datetime.now().year
 copyright = f"{current_year}, Hypernode"
 author = "Hypernode"
 
 # The full version, including alpha/beta/rc tags
-release = "dev"
+release = "latest"
 
 
 # -- General configuration ---------------------------------------------------

docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md

@@ -22,6 +22,12 @@ This can be useful for many reasons, such as:
 
 Configuring Magento 2 to start storing files in your bucket is done using a single command.
 
+Before configuring remote storage, make sure that the deprecated database media storage backend is disabled.
+
+```bash
+bin/magento setup:config:set system/media_storage_configuration/media_storage 0
+```
+
 **Hypernode Object Storage and other S3 compatible providers**
 
 If you're using Hypernode Object Storage or a different provider than AWS S3, you need to specify the `--remote-storage-endpoint` option.
@@ -39,7 +45,7 @@ bin/magento setup:config:set \
 For Hypernode Object Storage, use `main` as the bucket name and `EU` as the region. You can retrieve the remaining parameters by running `hypernode-object-storage info --with-credentials`.
 
 ```console
-app@testapp ~ # hypernode-object-storage info --with-credentials
+app@abcdef-example-magweb-cml:~$ hypernode-object-storage info --with-credentials
 +--------------------------------------+----------------+---------+-------------+-------------------------------------+---------------+---------------+
 |                 UUID                 |      Name      |   Plan  |  Hypernodes |           Management URL            |   Access Key  |   Secret Key  |
 +--------------------------------------+----------------+---------+-------------+-------------------------------------+---------------+---------------+
@@ -93,6 +99,10 @@ aws s3 sync var/import_export s3://my_bucket_name/import_export
 
 Both methods are significantly faster than Magento’s built-in sync, as aws s3 sync handles uploads concurrently.
 
+```{tip}
+More information about the `hypernode-object-storage` commands can be found in the [Object Storage documentation](../../hypernode-platform/object-storage.md).
+```
+
 ## The storage flag file in the bucket
 
 Magento's S3 implementation creates a test file called `storage.flag`, which is basically created to test if the connection works. So this is not a magic file to mark anything ([source](https://github.com/magento/magento2/blob/6f4805f82bb7511f72935daa493d48ebda3d9039/app/code/Magento/AwsS3/Driver/AwsS3.php#L104)).
@@ -121,6 +131,12 @@ If you’re using Amazon S3, ensure that your S3 bucket policies are properly co
 }
 ```
 
+## Remote storage tweaks module
+
+After configuring remote storage for Magento 2, you might run into some slower pages in the admin product grid. This is caused by an inefficient image loading mechanism found in the Magento core code. For now we have written a Magento 2 module to fix this performance problem.
+
+You can find the module on [GitHub](https://github.com/ByteInternet/magento2-remote-storage-tweaks/) and [Packagist](https://packagist.org/packages/hypernode/magento2-remote-storage-tweaks).
+
 ## Magento remote storage documentation
 
 - [Configure Remote Storage](https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/storage/remote-storage/remote-storage)

docs/ecommerce-applications/shopware-6/how-to-configure-remote-storage-for-shopware-6-x.md

@@ -43,7 +43,7 @@ shopware:
 You can get the required management URL, access key, and secret key by running `hypernode-object-storage info` with the `--with-credentials` flag:
 
 ```console
-app@testapp ~ # hypernode-object-storage info --with-credentials
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage info --with-credentials
 +--------------------------------------+----------------+---------+-------------+-------------------------------------+---------------+---------------+
 |                 UUID                 |      Name      |   Plan  |  Hypernodes |           Management URL            |   Access Key  |   Secret Key  |
 +--------------------------------------+----------------+---------+-------------+-------------------------------------+---------------+---------------+
@@ -95,6 +95,10 @@ Alternatively, you can use the AWS CLI directly:
 aws s3 sync public/media/ s3://bucket_name/media/
 ```
 
+```{tip}
+More information about the `hypernode-object-storage` command can be found in the [Object Storage documentation](../../hypernode-platform/object-storage.md).
+```
+
 ## Serving assets from your S3 bucket
 
 To serve media assets directly from your S3 bucket, you need to adjust your nginx configuration.

docs/hypernode-deploy/getting-started/configure-ci-cd.md

@@ -103,8 +103,8 @@ env:
 jobs:
   build:
     runs-on: ubuntu-latest
-    # Here we use the latest Hypernode Deploy image with PHP 8.3 and Node.js 22
-    container: quay.io/hypernode/deploy:latest-php8.3-node22
+    # Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v2
       - uses: actions/cache@v2
@@ -118,7 +118,7 @@ jobs:
         env:
           DEPLOY_COMPOSER_AUTH: ${{ secrets.DEPLOY_COMPOSER_AUTH }}
       - name: archive production artifacts
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: deployment-build
           path: build/build.tgz
@@ -137,8 +137,8 @@ jobs:
   deploy:
     needs: build
     runs-on: ubuntu-latest
-    # Here we use the latest Hypernode Deploy image with PHP 8.3 and Node.js 22
-    container: quay.io/hypernode/deploy:latest-php8.3-node22
+    # Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v2
       - name: download build artifact

docs/hypernode-deploy/pipelines/bitbucket-pipelines.md

@@ -58,8 +58,8 @@ Create the file `bitbucket-pipelines.yml` with the contents below.
 This workflow will be used in other workflows.
 
 ```yaml
-# Here we use the latest Hypernode Deploy image with PHP 8.3 and Node.js 22
-image: quay.io/hypernode/deploy:latest-php8.3-node22
+# Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22
+image: quay.io/hypernode/deploy:latest-php8.4-node22
 
 definition:
   steps:
@@ -73,9 +73,9 @@ definition:
 
 ````{note}
 Don't forget to set the specifications of the image to what your project needs. The same goes for the deploy steps.
-For example, if your project needs PHP 8.3 and Node.js 22, set the image to:
+For example, if your project needs PHP 8.4 and Node.js 22, set the image to:
 ```yaml
-image: quay.io/hypernode/deploy:latest-php8.3-node22
+image: quay.io/hypernode/deploy:latest-php8.4-node22
 ```
 ````
 

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

@@ -58,7 +58,7 @@ jobs:
   build:
     runs-on: ubuntu-latest
     # See https://quay.io/repository/hypernode/deploy?tab=tags for all possible tags.
-    container: quay.io/hypernode/deploy:latest-php8.3-node22
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
     - uses: actions/checkout@v3
     - uses: actions/cache@v3
@@ -70,7 +70,7 @@ jobs:
         ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
     - run: hypernode-deploy build -vvv
     - name: archive production artifacts
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       with:
         name: deployment-build
         path: build/build.tgz
@@ -79,11 +79,11 @@ jobs:
 
 ````{note}
 Don't forget to set the specifications of the image to what your project needs. The same goes for the deploy steps.
-For example, if your project needs PHP 8.3 and Node.js 22, set the image to:
+For example, if your project needs PHP 8.4 and Node.js 22, set the image to:
 ```yaml
 jobs:
   build:
-    container: quay.io/hypernode/deploy:latest-php8.3-node22
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     ...
 ```
 ````
@@ -113,7 +113,7 @@ jobs:
     environment:
       name: production
       url: https://www.example.com
-    container: quay.io/hypernode/deploy:latest-php8.3-node22
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
     - uses: actions/checkout@v3
     - name: download build artifact
@@ -157,7 +157,7 @@ jobs:
     environment:
       name: acceptance
       url: https://acceptance.example.com
-    container: quay.io/hypernode/deploy:latest-php8.3-node22
+    container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
     - uses: actions/checkout@v3
     - name: download build artifact

docs/hypernode-deploy/pipelines/gitlab-ci.md

@@ -49,7 +49,7 @@ This sets the container image, defines the CI/CD stages and defines the build st
 
 ```yaml
 # See https://quay.io/repository/hypernode/deploy?tab=tags for all possible tags.
-image: quay.io/hypernode/deploy:latest-php8.3-node22
+image: quay.io/hypernode/deploy:latest-php8.4-node22
 
 stages:
   - build
@@ -70,9 +70,9 @@ build:
 
 ````{note}
 Don't forget to set the specifications of the image to what your project needs.
-For example, if your project needs PHP 8.3 and Node.js 16, set the image to:
+For example, if your project needs PHP 8.4 and Node.js 16, set the image to:
 ```yaml
-image: quay.io/hypernode/deploy:latest-php8.3-node16
+image: quay.io/hypernode/deploy:latest-php8.4-node16
 ```
 ````