Update wording across our docs now that all Hypernodes use Managed Vhosts

docs/best-practices/testing/how-to-go-live-with-your-hypernode.md

@@ -71,9 +71,9 @@ Only if you use Hypernode’s WWW-redirection service, ensure that the base URL
 
 Flush the cache of Magento on the Hypernode. (`magerun cache:flush`)
 
-## Step 7: Set up Hypernode Managed Vhosts
+## Step 7: Set up Your 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.
+You need 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.
 

docs/ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode.md

@@ -14,13 +14,11 @@ redirect_from:
 
 Akeneo 3 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 5.7, PHP 7.2 and Elasticsearch 6.x**, so it won’t affect your shop negatively. Installing Akeneo version 3.x may take up to 15 minutes.
 
-## Managed Vhosts
+## Create a Vhost for a (Sub)Domain
 
-Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
+Ensure you have a vhost for your Akeneo domain.
 
-## Create a Managed_vhost for a (Sub)Domain
-
-If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
+If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
 
 ```bash
 hypernode-manage-vhosts akeneo.example.hypernode.io --type akeneo --https --force-https

docs/ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md

@@ -15,13 +15,11 @@ redirect_from:
 
 Akeneo 4 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.3 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 4.x may take up to 15 minutes.
 
-## Managed Vhosts
+## Create a Vhost for a (Sub)Domain
 
-Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
+Ensure you have a vhost for your Akeneo domain.
 
-## Create a Managed_vhost for a (Sub)Domain
-
-If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
+If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
 
 ```bash
 hypernode-manage-vhosts akeneo.example.hypernode.io --type akeneo4 --https --force-https

docs/ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md

@@ -14,13 +14,11 @@ redirect_from:
 
 Akeneo 5 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.4 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 5.x may take up to 15 minutes.
 
-## Managed Vhosts
+## Create a Vhost for a (Sub)Domain
 
-Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
+Ensure you have a vhost for your Akeneo domain.
 
-## Create a Managed_vhost for a (Sub)Domain
-
-If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
+If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
 
 ```bash
 hypernode-manage-vhosts akeneo.example.hypernode.io --type akeneo4 --https --force-https

docs/ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md

@@ -14,13 +14,11 @@ redirect_from:
 
 Akeneo 6 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.0 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 6.x may take up to 15 minutes.
 
-## Managed Vhosts
+## Create a Vhost for a (Sub)Domain
 
-Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
+Ensure you have a vhost for your Akeneo domain.
 
-## Create a Managed_vhost for a (Sub)Domain
-
-If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
+If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
 
 ```bash
 hypernode-manage-vhosts akeneo.example.hypernode.io --type generic-php --https --force-https --webroot /data/web/akeneo/public

docs/ecommerce-applications/akeneo/how-to-install-akeneo-7-on-hypernode.md

@@ -15,13 +15,11 @@ redirect_from:
 Akeneo 7 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.1 and OpenSearch 2.x**, so it won’t affect your shop negatively. Installing Akeneo version 7.x may take up to 15 minutes.\
 **Important note: Akeneo 7.x requires MySQL 8.0.30, which is only available on Debian Bookworm.**
 
-## Managed Vhosts
+## Create a Vhost for a (Sub)Domain
 
-Hypernode uses [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md). Ensure you have a vhost for your Akeneo domain.
+Ensure you have a vhost for your Akeneo domain.
 
-## Create a Managed_vhost for a (Sub)Domain
-
-If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a managed_vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
+If your Magento or Shopware installation already points to `example.hypernode.io`, you can create a vhost for your Akeneo installation on a subdomain, for example `akeneo.example.hypernode.io`. The command below will also install Let’s Encrypt and force your domain to use HTTPS.
 
 ```bash
 hypernode-manage-vhosts akeneo.example.hypernode.io --type generic-php --https --force-https --webroot /data/web/akeneo/public

docs/ecommerce-applications/akeneo/how-to-use-a-basic-staging-environment-with-akeneo-3.md

@@ -14,9 +14,9 @@ redirect_from:
 
 Hypernode offers a staging environment so it can be used as a sandbox for your Akeneo PIM project. Please keep in mind that your staging environment for Akeneo shares resources (disk, CPU, memory) with your production environment. It’s also possible to order a [development plan](../../hypernode-platform/tools/how-to-use-hypernode-development-plans.md) instead, so your production environment will not be affected. Once again a big thank you to our partner [Experius](https://www.experius.nl/) for contributing to this article!
 
-## Update managed_vhosts
+## Update Vhosts
 
-Update the current managed_vhost with staging port.
+Update the current vhost with staging port.
 
 ```bash
 hypernode-manage-vhosts  akeneo.example.hypernode.io --port-http-staging 8888 --port-https-staging 8443 --force-https --https

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

@@ -41,7 +41,7 @@ $ hypernode-systemctl settings varnish_enabled True
 
 ## Configure Varnish on the Vhost
 
-Since the introduction of [hypernode-manage-vhosts](https://changelog.hypernode.com/changelog/release-7166-hypernode-manage-vhosts-enabled-by-default/) Hypernode may work somewhat different than you might be used to. With HMV enabled, it requires one more step to configure Varnish for your shop/vhost. Remember, for each domain, there should be a vhost created. You can list an overview of all configured vhosts with `hypernode-manage-vhosts --list`. While you do that, note that there is a column, "varnish". By default this is set to "False". Which means that Varnish isn't configured for this vhost. You can configure Varnish for the vhost by running the following command:
+The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) command requires one additional step to configure Varnish for your shop/vhost. Remember, for each domain, there should be a vhost created. You can list an overview of all configured vhosts with `hypernode-manage-vhosts --list`. While you do that, note that there is a column, "varnish". By default this is set to "False". Which means that Varnish isn't configured for this vhost. You can configure Varnish for the vhost by running the following command:
 
 ```console
 $ hypernode-manage-vhosts EXAMPLE.COM --varnish

docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md

@@ -25,7 +25,7 @@ Varnish can be enabled with a simple command using the [hypernode-systemctl CLI]
 
 ## Step Two: Enable Varnish for NGINX Vhost
 
-The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts) (HMV) config allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts:
+The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) command allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts:
 
 - example.com
 - [www.example.com](http://www.example.com)

docs/ecommerce-applications/shopware-5/how-to-host-shopware-on-hypernode.md

@@ -28,7 +28,7 @@ Shopware is an e-commerce system roughly the same as Magento and both have the s
 
 ## Configuring Hypernode for Shopware
 
-All you need to do is create a [vhost](../../hypernode-platform/nginx/hypernode-managed-vhosts.md#managing-vhosts) (or change an existing vhost) with type `shopware5` or `shopware6`.
+All you need to do is create a vhost (or change an existing vhost) with type `shopware5` or `shopware6`.
 This will make sure the specific vhost has the right nginx configuration to host your Shopware environment.
 So for example, your domain is `www.example.com` and you'd like a vhost with Shopware 6 configuration.
 You can create this vhost with the following command: `hypernode-manage-vhosts www.example.com --type shopware6 --https --force-https`.

docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md

@@ -25,7 +25,7 @@ You can enable varnish on the hypernode using the [systemctl-tool](../../hyperno
 
 ## Step Two: How to Setup Varnish for the Vhost
 
-The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) (HMV) config allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts:
+The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) command allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts:
 
 - example.com
 - [www.example.com](http://www.example.com)

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

@@ -69,9 +69,9 @@ In our support documentation you will find detailed information about installing
 - [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)
 
-### Step 4 – Set up Hypernode Managed Vhosts
+### Step 4 – Set up Your 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.
+You need 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.
 

docs/hypernode-platform/cluster.md

@@ -91,7 +91,7 @@ To add custom NGINX rules for handling specific things on the loadbalancer (like
 used in `/data/web/nginx` and `/data/web/nginx/<vhost>`. This can be very crucial for your performance, accelerating asset delivery
 and lowering pressure on varnish.
 
-When running `hypernode-manage-vhosts` ([docs](nginx/hypernode-managed-vhosts.md)) on a loadbalancer server for a specific vhost, a
+When running [hypernode-manage-vhosts](nginx/hypernode-managed-vhosts.md) on a loadbalancer server for a specific vhost, a
 preconfigured loadbalancer configuration file will be created for you (for example `/data/web/nginx/example.com/loadbalancer.magento2.conf`).
 These preconfigured files act as a good starting point for your loadbalancer setup, but can be customized to your needs.
 

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

@@ -133,4 +133,3 @@ 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.
-- 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.

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

@@ -26,7 +26,7 @@ There are multiple ways to set up your Magento multistore. You can choose betwee
 - Using subdirectories (e.g. example.com/en/ and example.com/fr/ etc.)
 - Using a combination of different domains and subdirectories (e.g. example.com and example.net/en/ and example.net/fr/)
 
-Below we have provided the instructions on how to set up each of the scenarios within Nginx on your Hypernode. Please do note that in order to follow the instructions your Hypernode must have [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) enabled. Furthermore, we cannot guarantee that the instructions will work with all plugins and custom configurations since this has only been tested with the default Luma theme and without any customizations.
+Below we have provided the instructions on how to set up each of the scenarios within Nginx on your Hypernode. Furthermore, we cannot guarantee that the instructions will work with all plugins and custom configurations since this has only been tested with the default Luma theme and without any customizations.
 
 ### Using Different Domains
 
@@ -144,7 +144,7 @@ Magento Stores - Base URLs
 +----+---------+------------------------------------+--------------------+
 ```
 
-First add the following vhosts using the information from the [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) documentation.
+First add the following vhosts using the information from the [vhost configuration](hypernode-managed-vhosts.md) documentation.
 
 - [www.example.com](http://www.example.com)
 - [www.example.nl](http://www.example.nl)

docs/hypernode-platform/nginx/how-to-redirect-from-or-to-www.md

@@ -18,14 +18,12 @@ Many constructions are possible when it gets to the base URL. Some shop owners p
 
 There are some restrictions when choosing your base URL.
 
-If you use the wwwizer servers, which are sometimes used when your domain is not hosted at Hypernode and thus the DNS can’t be automagically changed in case of up or downgrades, your domain will always redirect to [www](http://www).
+If you use the wwwizer servers, which are sometimes used when your domain is not hosted at Hypernode and thus the DNS can’t be automagically changed in case of up or downgrades, your domain will always redirect to www.
 
 More info can be found [on our page about setting your DNS](../dns/how-to-manage-your-dns-settings-for-hypernode.md).
 
 ## Redirect From Apex to WWW
 
-**When Hypernode Managed Vhosts is enabled**
-
 To redirect all traffic to www you have to create both a vhost for the Apex and for the `www`. For the non-www vhost you can create the vhost as type wwwizer. This will redirect all traffic to the `www`. version of that vhost. This can be achieved by running: `hypernode-manage-vhosts example.com --type wwwizer`.
 
 ```text

docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md

@@ -121,7 +121,7 @@ Besides the above-known plugins that will hit the blacklisted keyword, `http.rat
 
 To prevent a single IP from using all the FPM workers available simultaneously, leaving no workers available for other visitors, we implemented a per IP rate limit mechanism. This mechanism sets a maximum amount of PHP-FPM workers that can be used by one IP to 20. This way, one single IP address cannot deplete all the available FPM workers, leaving other visitors with an error page or a non-responding site.
 
-**Please note:** if [Hypernode Managed Vhosts](hypernode-managed-vhosts.md) is enabled, only add the `http.ratelimit` file in the Nginx root. Don't add it to the specific vhost as well, as this may cause conflicts.
+**Please note:** only add the `http.ratelimit` file in the Nginx root. Don't add it to the specific vhost as well, as this may cause conflicts.
 
 ### How per‑IP limiting works (what you can influence)