Merge branch 'master' into akeneo-3-staging-guide-fixes

Author: poespas

.github/workflows/deploy.yaml

@@ -1,7 +1,7 @@
 name: Deploy application
 
 on:
-  pull_request:
+  pull_request_target:
   push:
     branches:
       - 'master'
@@ -17,6 +17,7 @@ jobs:
       - uses: actions/checkout@v3
         with:
           fetch-depth: 0
+          ref: ${{ github.event.pull_request.head.sha || github.sha }}
       # Declares the repository safe and not under dubious ownership.
       - name: Add repository to git safe directories
         run: git config --global --add safe.directory $GITHUB_WORKSPACE
@@ -46,12 +47,13 @@ jobs:
     environment:
       name: acceptance
       url: ${{ steps.get_brancher_hostname.outputs.BRANCHER_URL }}
-    if: github.ref != 'refs/heads/master'
+    if: github.event_name == 'pull_request_target'
     container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v3
         with:
           fetch-depth: 0
+          ref: ${{ github.event.pull_request.head.sha || github.sha }}
       - name: download build artifact
         uses: actions/download-artifact@v4
         with:
@@ -101,7 +103,7 @@ jobs:
     environment:
       name: production
       url: https://docs.hypernode.io
-    if: github.ref == 'refs/heads/master'
+    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
     container: quay.io/hypernode/deploy:latest-php8.4-node22
     steps:
       - uses: actions/checkout@v3

.github/workflows/lint.yaml

@@ -1,7 +1,7 @@
 name: Run linting and suggest changes
 
 on:
-  pull_request:
+  pull_request_target:
 
 permissions:
   contents: read
@@ -15,8 +15,10 @@ jobs:
         python-version: ['3.12']
 
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-python@v4
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+      - uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
       - name: Install dependencies

docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md

@@ -64,16 +64,18 @@ In our support documentation you will find detailed information about installing
 - [Akeneo 4](../../ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md)
 - [Akeneo 5](../../ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md)
 - [Akeneo 6](../../ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md)
+- [Akeneo 7](../../ecommerce-applications/akeneo/how-to-install-akeneo-7-on-hypernode.md)
 - [Magento 1](../../ecommerce-applications/magento-1/how-to-install-magento-1-on-hypernode.md)
 - [Magento 2](../../ecommerce-applications/magento-2/how-to-install-magento-2-on-hypernode.md)
 - [Shopware 5](../../ecommerce-applications/shopware-5/how-to-install-shopware-5-on-hypernode.md)
 - [Shopware 6](../../ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode.md)
+- [WooCommerce](../../ecommerce-applications/woocommerce/how-to-install-woocommerce-on-hypernode.md)
 
 ### Step 4 – Set up Hypernode Managed Vhosts
 
 Due to this configuration it is required to add a new vhost for every domain you want to link to your Hypernode. So you need to configure your DNS correctly and add a new vhost for the domain.
 
-To add a new vhost, for example the domainname [www.example.com](http://www.example.com), to your configuration, you can simply run the command `hypernode-manage-vhosts www.example.com`. This will create a new vhost configuration in `/data/web/nginx/www.example.com/`, using the Magento 2 template.
+To add a new vhost, for example the domain name [www.example.com](http://www.example.com), to your configuration, you can simply run the command `hypernode-manage-vhosts www.example.com`. This will create a new vhost configuration in `/data/web/nginx/www.example.com/`, using the Magento 2 template.
 
 Please note that defining the vhosts '[www.example.com](http://www.example.com)', does not automatically add 'example.com' as a vhost. You will have to manually define a vhost for this. Since most people simply want their 'example.com' to redirect to '[www.example.com](http://www.example.com)', you can simply use the `--type wwwizer` argument to set this up. This will configure the vhost to redirect all traffic to the www-version of the domain.
 

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

@@ -1,14 +1,11 @@
-______________________________________________________________________
-
+---
 myst:
-html_meta:
-description: 'Find out here how to order a domain.'
+  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
-
-______________________________________________________________________
+  - /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/ -->