Merge branch 'master' into update-redis-woocommerce

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

.python-version

@@ -0,0 +1 @@
+3.11

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/ -->
 

docs/hypernode-platform/dns/dns-for-control-panel-users.md

@@ -20,7 +20,13 @@ More information about DNS settings for your webshop on Hypernode technology, fo
 
 ## Manage DNS With a Third Party
 
-Please note that Hypernode cannot provide uptime guarantees for external DNS. Your SLA does not apply in this case. When a domain name is registered externally, please keep in mind that Hypernode has no influence on the functioning of the DNS. If you don't want to transfer your domain name to Hypernode, changing the name servers to the Byte name servers is a good second option. You will need a Presence plan to be able to manage your DNS from the Service Panel. When you have the DNS set up correctly you can ask your domain name provider to change the name servers to the Byte name servers:
+Please note that Hypernode cannot provide uptime guarantees for external DNS, so your SLA does not apply in this case.
+
+If your domain name is registered with an external provider, please be aware that Hypernode has no control over the availability or functioning of that provider’s DNS services.
+
+If you prefer not to transfer your domain name to Hypernode, a good alternative is to update your domain’s nameservers to the Hypernode nameservers. To manage your DNS through the Service Panel, you will need a Presence plan.
+
+Once your DNS has been configured correctly, you can ask your domain provider to update the nameservers to the Hypernode nameservers:
 
 ns1.hypernode.com
 
@@ -94,11 +100,11 @@ Different DNS records have been created for the different types of internet traf
 
 The NS records contain the "authoritative name servers" or prevailing name servers. When your domain name is listed with Hypernode, these will always be on Byte's name servers by default. This determines that we are the party that manages the DNS records. You can also find them in the WHOIS. The Byte name servers are:
 
-nsa.byte.nl
+ns1.hypernode.com
 
-nsb.byte.nl
+ns2.hypernode.com
 
-nsc.byte.nl
+ns3.hypernode.com
 
 If you have set up other name servers, the DNS data will be downloaded from that server. Hypernode always recommends using the Byte name servers so that in the event of IP changes (if you switch from datacenter) we can switch quickly, without having to make changes to the DNS configuration. You can NOT change the name servers from the Service Panel. If you need to change the name servers (to for example Cloudflare) you can request this by sending an email to [support@hypernode.com](mailto:support@hypernode.com) (from the email address that is linked to the account).
 
@@ -114,13 +120,19 @@ This is the A record for IPv6 addresses.
 
 ### MX Records
 
-The MX records contain the host names of the mail server(s). In addition to the hostname, you can assign a priority to each MX record. For example, you can give your own mail servers a higher priority (a lower number) than our smtp2.byte.nl server. This means that smtp2.byte.nl is only used as a mail server when your own servers are not available. We also call this "fallback server". Also make sure that you do not give every MX record a priority of 10, otherwise our server will not be able to determine which record is about the primary mail server. These are the MX records of the Hypernode mail servers:
+MX records determine where email for your domain should be delivered. The value of an MX record must point to the mail server that handles incoming email for your domain. Each MX record also includes a priority: the lower the number, the higher the priority.
+
+If you use multiple mail servers, the server with the lowest priority number is treated as the primary server. A second server can be configured as a fallback by giving it a higher priority number.
+
+Make sure not all MX records use the same priority. If they do, sending servers may distribute delivery across them instead of treating one as the primary server.
+
+Example MX configuration:
 
-|             |          |               |          |
-| ----------- | -------- | ------------- | -------- |
-| **Name**    | **Type** | **Value**     | **Prio** |
-| example.com | MX       | smtp1.byte.nl | 10       |
-| example.com | MX       | smtp2.byte.nl | 20       |
+|             |          |                   |          |
+| ----------- | -------- | ----------------- | -------- |
+| **Name**    | **Type** | **Value**         | **Prio** |
+| example.com | MX       | smtp1.example.com | 10       |
+| example.com | MX       | smtp2.example.com | 20       |
 
 Always use your primary domain for your MX records. An MX record with the Name on “mail.example.nl” will only work for …@mail.example.nl addresses.
 

docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md

@@ -151,7 +151,7 @@ If you want to connect to FTP you’ll have to use the following credentials:
 - Password: **Your password**
 - Port:
   - **21** For regular FTP
-  - **2222** For SFTP (you need to opt-in first!)
+  - **2222** For SFTP
 
 ## ACTIVE Mode or PASSIVE Mode
 

docs/hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md

@@ -132,5 +132,5 @@ map $http_user_agent $development_exceptions {
 
 ## Troubleshooting
 
-- Google Pagespeed analysis uses the Google bot user agent and can therefore not be used on development nodes.
+- To allow Google Pagespeed analysis in development hypernodes you can whitelist the following IPs https://www.gstatic.com/ipranges/goog.json. PSI uses different user agents than Google bot and will be able to perform analysis on your frontend without allowing crawling.
 - In some cases, particularly if you have not yet enabled [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md), it’s possible the Basic Authentication blocks the Let’s Encrypt validation server. If you wish to make use of Let’s Encrypt on your development Hypernode, you should add the ‘letsencrypt’ user agent to the whitelist file.