Merge branch 'master' into docsearch-earch

poespas · web-flow · commit aba3aa488dc2 · 2025-07-07T14:26:16.000+02:00
diff --git a/docs/about-hypernode/support/scope-of-support.md b/docs/about-hypernode/support/scope-of-support.md
@@ -72,12 +72,6 @@ The goal of the onboarding process is to assist new customers in migrating their
 
 1. Basic Migration
    With a basic migration we will assist the customer in migrating their eCommerce platform as is. This means that we will make sure that the webshop is working on our Hypernode platform, but we will not look into any optimizations that can be done.
-1. Hyperformance
-   With a Hyperformance migration we will not only assist the customer in migrating their eCommerce platform to our Hypernode platform, we will also focus on optimizing the shop to guarantee the best performance on our Hypernode platform. We will be looking at the following things:
-   1. Caching
-   1. Image optimization
-   1. Static file optimization
-   1. Recommending any changes to be done within the eCommerce platform itself
 1. What is not included in onboarding
    1. Email migration
    1. Custom Varnish configuration
diff --git a/docs/best-practices/performance/how-to-fix-performance-issues-caused-by-bots-and-crawlers.md b/docs/best-practices/performance/how-to-fix-performance-issues-caused-by-bots-and-crawlers.md
@@ -55,7 +55,7 @@ GET /clothing/pants.html?color=1181_1188_1500 HTTP/1.1 Mozilla/5.0 (compatible;
 It is clear that the “size” and “color” parameters are used for layered navigation, because they define subsets of your catalogue. For normal indexing, you only want /clothing.html and /clothing/pants.html indexed. To block bots in this case, you should add this to `/data/web/nginx/server.layered_navigation:`
 
 ```nginx
-if ($http_user_agent ~* 'http|bot|crawl|spider') {
+if ($http_user_agent ~* 'http|bot|crawl|spider|GoogleOther') {
     set $is_bot 1;
 }
 # Here, you should define the layered navigation urls.
diff --git a/docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md b/docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md
@@ -23,7 +23,7 @@ On the first working day after the detection, our customer will receive a e-mail
 
 The output of the daily scan we perform, is written to `/var/log/mwscan.log`. If the scanner hits on a file, please review the file. In most of the cases, the malware has been uploaded by a unsecure downloader folder or Magmi plugin. Try to find how the file has been uploaded. Replace the file with the originating file distributed by the developer or when it is not used, remove the file.
 
-If you find web shells, malicious files, and/or injected PHP code that are not yet recognised by `mwscan`, please report them by filing an issues on [the Github repository](https://github.com/gwillem/magento-malware-scanner)of this containing the files as described in the [contribution documentation](https://github.com/gwillem/magento-malware-scanner/blob/master/CONTRIBUTING.md)
+If you find web shells, malicious files, and/or injected PHP code that are not yet recognised by `mwscan`, please report them by filing an issues on [the Github repository](https://github.com/gwillem/magento-malware-scanner) of this containing the files as described in the [contribution documentation](https://github.com/gwillem/magento-malware-scanner/blob/master/CONTRIBUTING.md)
 
 ## Scan Your Files for Known Web Shells and Malware Manually
 
diff --git a/docs/best-practices/testing/how-to-check-if-everything-works.md b/docs/best-practices/testing/how-to-check-if-everything-works.md
@@ -18,7 +18,7 @@ Use the steps below to test everything in your shop.
 
 **NB:** When browsing your preview shop, double check that you don’t end up on your production shop by following a hardcoded link.
 
-A bigger checklist is available [on the Github account](https://gist.github.com/peterjaap/10016278)of one of our well appreciated technical partners Peter Jaap (Elgentos).
+A bigger checklist is available [on the Github account](https://gist.github.com/peterjaap/10016278) of one of our well appreciated technical partners Peter Jaap (Elgentos).
 
 - Test all storefronts *(use the storefront view in MageReport Premium (only for Magento 1.x versions)).*
 - Test front pages, categories and product pages.
@@ -51,7 +51,7 @@ grep -Ri memcache /data/web/public/app/etc
 - Test for images, css, js and mixed content warnings.
 - Test if all static content is loaded: View the console in your browser to check if there are javascript errors or 404 errors on stylesheets and js files.
 - Test if [the Magento API is accessible when used](../../ecommerce-applications/magento-2/how-to-enable-the-magento-2-api.md).
-- Test if the sitemap is accessible for [Magento 1](../../ecommerce-applications/magento-1/how-to-create-a-sitemap-xml-for-magento-1-x.md)or [Magento 2](../../ecommerce-applications/magento-2/how-to-create-a-sitemap-xml-for-magento-2-x.md).
+- Test if the sitemap is accessible for [Magento 1](../../ecommerce-applications/magento-1/how-to-create-a-sitemap-xml-for-magento-1-x.md) or [Magento 2](../../ecommerce-applications/magento-2/how-to-create-a-sitemap-xml-for-magento-2-x.md).
 - Test if [you can easily download the robots.txt file](../../ecommerce-applications/magento-1/how-to-create-a-robots-txt-for-your-magento-1-shop.md) (Or for [Magento 2](../../ecommerce-applications/magento-2/how-to-create-a-robots-txt-for-magento-2-x.md)).
 - Test product and price import and export routines.
 - Test product push mechanisms for search engines.
diff --git a/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md b/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md
@@ -103,6 +103,6 @@ After installing and configuring Nginx, you can visit your WordPress at `/blog/`
 
 ## Multisite
 
-It is possible to set up a multisite environment in WordPress. To do this, refer to the [original WordPress documentation about creating multisites](https://codex.wordpress.org/Create_A_Network)and the article [about configuring WordPress on Nginx](https://wordpress.org/support/article/nginx/).
+It is possible to set up a multisite environment in WordPress. To do this, refer to the [original WordPress documentation about creating multisites](https://codex.wordpress.org/Create_A_Network) and the article [about configuring WordPress on Nginx](https://wordpress.org/support/article/nginx/).
 
 *Please note that it won’t work in all cases due to the fact that certain Nginx configurations cannot be changed. At the moment we are still looking into a solution that will work for everyone.*
diff --git a/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md b/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md
@@ -91,7 +91,7 @@ magerun --root-dir=/data/web/staging config:set web/secure/base_url https://$SHO
 magerun --root-dir=/data/web/staging cache:flush
 ```
 
-If you have many storefronts, that all should be changed it's easier to use [our script](https://gist.github.com/hn-support/faf03c5898f5553b7fd9f4059709aef4)to change the base URL's of your staging environment.
+If you have many storefronts, that all should be changed it's easier to use [our script](https://gist.github.com/hn-support/faf03c5898f5553b7fd9f4059709aef4) to change the base URL's of your staging environment.
 
 To use this script:
 
diff --git a/docs/ecommerce-applications/shopware-5/how-to-setup-a-multistore-in-shopware.md b/docs/ecommerce-applications/shopware-5/how-to-setup-a-multistore-in-shopware.md
@@ -29,7 +29,6 @@ A subshop is just be what you need if you like to use the Shopware installation
 
 - Main shop: `hypernode.com`
 - Subshop: `byte.nl`
-- Subshop: `hyperformance.nl`
 
 ### Language Shop
 
diff --git a/docs/ecommerce-applications/woocommerce/how-to-configure-converter-for-media-plugin-for-wordpress-woocommerce.md b/docs/ecommerce-applications/woocommerce/how-to-configure-converter-for-media-plugin-for-wordpress-woocommerce.md
@@ -67,7 +67,7 @@ location ~ /wp-content/(?<path>.+)\.(?<ext>jpe?g|png|gif|webp)$ {
 # END Converter for Media
 ```
 
-Place the above configuration in `/data/web/server.media.conf.` Once you save the file, NGINX will automatically reload, and if something goes wrong, you will be notified.
+Place the above configuration in `/data/web/nginx/server.media.conf` Once you save the file, NGINX will automatically reload, and if something goes wrong, you will be notified.
 
 ## Test the Configuration
 
diff --git a/docs/hypernode-deploy/applications/config-for-nextjs.md b/docs/hypernode-deploy/applications/config-for-nextjs.md
@@ -1,7 +1,7 @@
 # Config for NextJS
 
 ```{note}
-NextJS is not officially supported on the Hypernode Platform. So please use this at your own risk,.
+NextJS is not officially supported on the Hypernode Platform. So please use this at your own risk.
 ```
 
 Configuration to use as Hypernode Deploy deploy.php for a NextJS webserver application:
diff --git a/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md b/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md
@@ -57,7 +57,7 @@ Syncing a domain to your Hypernode will immediately change the domain's DNS reco
 
 #### The steps:
 
-1. [Log in to your Control Panel](https://my.hypernode.com/)with your customer email and password and select "domains."
+1. [Log in to your Control Panel](https://my.hypernode.com/) with your customer email and password and select "domains."
 1. Here you will find a list of your domain names.
 1. Click on your domain name.
 1. In your next view, you can **link**\* the domain to your Hypernode.
diff --git a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-outgoing-email.md b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-outgoing-email.md
@@ -36,7 +36,7 @@ To check if your DNS records have been configured correctly, please check our on
 - The second and third records are needed for automatic DKIM signing and DMARC
 - The fourth record is the SPF record. Please make sure you include spf.***example***.hypernode.io in your DNS's SPF record.
 
-Please check our [DNS validato](https://my.hypernode.com/dns/check/)r to confirm email can be sent successfully.
+Please check our [DNS validator](https://my.hypernode.com/dns/check/) to confirm email can be sent successfully.
 
 ## Additional audit options
 
diff --git a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md
@@ -17,7 +17,7 @@ When you want to use Office365 and your domain is registered with Hypernode or h
 
 ## Validation Record
 
-When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://my.hypernode.com/)and follow the next steps:
+When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://my.hypernode.com/) and follow the next steps:
 
 1. Log in to the Service Panel (my.hypernode.com).
 1. Select the domain from the domain overview.
diff --git a/docs/hypernode-platform/object-storage.md b/docs/hypernode-platform/object-storage.md
@@ -31,3 +31,5 @@ glob:
 object-storage/getting-started
 object-storage/*
 ```
+
+To get started with Hypernode Object Storage, check out our [Getting started](object-storage/getting-started.md) guide for a detailed overview of the system architecture and features.
diff --git a/docs/hypernode-platform/object-storage/basic-commands.md b/docs/hypernode-platform/object-storage/basic-commands.md
@@ -0,0 +1,137 @@
+---
+myst:
+  html_meta:
+    description: Learn about the basic commands for managing Hypernode Object Storage
+    title: Hypernode Object Storage | Basic Commands
+---
+
+# Basic Commands
+
+This guide covers the fundamental commands for managing your Hypernode Object Storage workspace. These commands allow you to create, view, update, and cancel your object storage workspace.
+
+## Creating a Workspace
+
+The `create` command initializes a new Object Storage workspace.
+
+```console
+hypernode-object-storage create
+```
+
+### Options
+
+- `--name`: Specify a custom name for your workspace
+- `--plan`: Select a storage plan (e.g., OS50GB, OS200GB)
+- `--coupon`: Apply a coupon code for discounts
+
+### Example
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage create --name my-storage --plan OS200GB
+```
+
+## Viewing Workspace Information
+
+The `info` command displays details about your current Object Storage workspace.
+
+```console
+hypernode-object-storage info
+```
+
+### Options
+
+- `--with-credentials`: Display sensitive credentials
+- `--verbose`: Show detailed debug information
+- `-F {text,json}`: Choose output format (text or JSON)
+
+### Example Output
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage info
+UUID         | d8770125-6c90-4770-b00f-1716f699990a
+Name         | example-storage
+Plan         | OS200GB
+Versioning   | Disabled
+Hypernodes   | example
+Endpoint URL | **sensitive**
+Access Key   | **sensitive**
+Secret Key   | **sensitive**
+```
+
+### JSON Output Example
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage info -F json
+{
+  "UUID": "2667238b-9976-437f-98f5-cd7491b76fd8",
+  "Name": "my workspace",
+  "Plan": {
+    "code": "OS200GB",
+    "name": "Growth Node",
+    "description": "Great for expanding stores",
+    "price": 2000,
+    "storage_size_in_gb": 200,
+    "is_popular": true
+  },
+  "Versioning": false,
+  "Hypernodes": "example",
+  "Credentials": {
+    "management_url": "**sensitive**",
+    "access_key": "**sensitive**",
+    "secret_key": "**sensitive**"
+  }
+}
+```
+
+## Updating Workspace Settings
+
+The `update` command allows you to modify your Object Storage workspace settings.
+
+```console
+hypernode-object-storage update
+```
+
+### Options
+
+- `--enable-versioning`: Enable object versioning
+- `--disable-versioning`: Disable object versioning
+
+### Example
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage update --enable-versioning
+Enabling versioning...
+Versioning enabled successfully!
+```
+
+```{note}
+Enabling versioning increases storage usage as each version of an object is stored separately. Consider your storage plan size when enabling this feature.
+```
+
+## Canceling a Workspace
+
+The `cancel` command initiates the cancellation process for your Object Storage workspace.
+
+```console
+hypernode-object-storage cancel
+```
+
+### Important Notes
+
+1. **Cancellation Timing**
+
+   - Cancellation takes effect at the end of the current billing period
+   - You will be billed for the full period
+
+1. **Data Retention**
+
+   - Data remains accessible for 7 days after cancellation
+   - Use this period to retrieve any needed data
+
+### Example
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage cancel
+Are you sure you want to cancel your Object Storage workspace? [y/N]: y
+Cancellation initiated. Your workspace will be canceled at the end of the current billing period.
+Data will remain accessible for 7 days after cancellation.
+```
diff --git a/docs/hypernode-platform/object-storage/cancellation.md b/docs/hypernode-platform/object-storage/cancellation.md
diff --git a/docs/hypernode-platform/object-storage/dynamic-upscaling.md b/docs/hypernode-platform/object-storage/dynamic-upscaling.md
@@ -15,6 +15,46 @@ When Dynamic Upscaling is enabled, the system monitors your usage and upgrades y
 
 ## Managing Dynamic Upscaling
 
-Dynamic Upscaling can be enabled or disabled through the Control Panel.
+### Control Panel
 
-Go to the Control Panel, select the Object Storage workspace you want to enable/disable Dynamic Upscaling for, and toggle the Dynamic Upscaling switch.
+Dynamic Upscaling can be enabled or disabled through the Control Panel:
+
+1. Go to the Control Panel
+1. Select the Object Storage workspace
+1. Toggle the Dynamic Upscaling switch
+
+### Command Line Interface
+
+You can also manage Dynamic Upscaling using the CLI. First, ensure you have the basic commands set up as described in [Basic Commands](basic-commands.md#updating-workspace-settings).
+
+To enable Dynamic Upscaling:
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage update --enable-dynamic-upscaling
+Enabling dynamic upscaling...
+Dynamic upscaling enabled successfully!
+```
+
+To disable Dynamic Upscaling:
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage update --disable-dynamic-upscaling
+Disabling dynamic upscaling...
+Dynamic upscaling disabled successfully!
+```
+
+To check the current status of Dynamic Upscaling:
+
+```console
+app@abcdef-example-magweb-cmbl:~$ hypernode-object-storage info
+UUID         | d8770125-6c90-4770-b00f-1716f699990a
+Name         | example-storage
+Plan         | OS200GB
+Versioning   | Disabled
+Dynamic Upscaling | Enabled
+Hypernodes   | example
+```
+
+```{note}
+When Dynamic Upscaling is enabled, your plan will automatically upgrade when you reach 99% of your current storage limit. This may result in higher costs, so monitor your usage regularly.
+```
diff --git a/docs/hypernode-platform/object-storage/getting-started.md b/docs/hypernode-platform/object-storage/getting-started.md
@@ -62,7 +62,13 @@ Secret Key   | **sensitive**
 1. Click your workspace.
 1. Click the **Show credentials** button in the top-right corner.
 
+## Setting up your application
+
 You can use the credentials and the URL now to configure remote storage for your application with the help of the following articles:
 
 1. [How to configure remote storage for Magento 2.x](../../ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md)
 1. [How to configure remote storage for Shopware 6.x](../../ecommerce-applications/shopware-6/how-to-configure-remote-storage-for-shopware-6-x.md)
+
+## Setting up Nginx
+
+After setting up Object Storage, you will want to configure your Nginx to serve assets directly from your storage bucket. Learn how to do this using Hypernode Managed Vhosts in our [Object Storage and Hypernode Managed Vhosts](../nginx/hypernode-managed-vhosts.md#object-storage-and-hypernode-managed-vhosts) article.
diff --git a/docs/hypernode-platform/object-storage/interactive-explorer.md b/docs/hypernode-platform/object-storage/interactive-explorer.md
@@ -0,0 +1,22 @@
+---
+myst:
+  html_meta:
+    description: Learn how to use the interactive explorer of Hypernode Object Storage
+    title: Hypernode Object Storage | Interactive Explorer
+---
+
+# Interactive Explorer
+
+Hypernode Object Storage provides an interactive terminal interface for exploring and managing your objects. The `explore` command launches a user-friendly terminal UI that makes it easy to navigate through your storage, view object versions, and perform common operations.
+
+## Explore
+
+Launch the interactive explorer with:
+
+```console
+hypernode-object-storage explore
+```
+
+This opens a terminal UI that looks like this:
+
+![](_res/stu_screenshot.png)
diff --git a/docs/hypernode-platform/object-storage/managing-objects.md b/docs/hypernode-platform/object-storage/managing-objects.md
diff --git a/docs/hypernode-platform/tools/how-to-configure-automatic-logfile-rotation.md b/docs/hypernode-platform/tools/how-to-configure-automatic-logfile-rotation.md
diff --git a/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md b/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md
diff --git a/docs/hypernode-platform/tools/how-to-use-node-js-and-npm-on-hypernode.md b/docs/hypernode-platform/tools/how-to-use-node-js-and-npm-on-hypernode.md
diff --git a/docs/services/control-panel/how-to-use-the-dns-check.md b/docs/services/control-panel/how-to-use-the-dns-check.md
diff --git a/docs/services/magereport/magereport-premium.md b/docs/services/magereport/magereport-premium.md
diff --git a/docs/troubleshooting/performance/how-to-solve-the-front-controller-reached-100-router-match-iterations-error.md b/docs/troubleshooting/performance/how-to-solve-the-front-controller-reached-100-router-match-iterations-error.md

Original file line number	Diff line number	Diff line change
`@@ -55,7 +55,7 @@ GET /clothing/pants.html?color=1181_1188_1500 HTTP/1.1 Mozilla/5.0 (compatible;`
`55`	`55`	It is clear that the “size” and “color” parameters are used for layered navigation, because they define subsets of your catalogue. For normal indexing, you only want /clothing.html and /clothing/pants.html indexed. To block bots in this case, you should add this to `/data/web/nginx/server.layered_navigation:`
`56`	`56`
`57`	`57`	```nginx
`58`		`-if ($http_user_agent ~* 'http\|bot\|crawl\|spider') {`
	`58`	`+if ($http_user_agent ~* 'http\|bot\|crawl\|spider\|GoogleOther') {`
`59`	`59`	`set $is_bot 1;`
`60`	`60`	`}`
`61`	`61`	`# Here, you should define the layered navigation urls.`