Skip to content

Commit d236006

Browse files
author
Jonathan Visser
committed
Format documents
1 parent 978502b commit d236006

File tree

5 files changed

+4
-8
lines changed

5 files changed

+4
-8
lines changed

docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
22
myst:
33
html_meta:
4-
description: 'We recommend serving your site only over HTTPS traffic. This is safer and is better for search index optimization. Configure your shop with these steps. '
4+
description: 'We recommend serving your site only over HTTPS traffic. This is
5+
safer and is better for search index optimization. Configure your shop with
6+
these steps. '
57
title: How to configure your shop to only use https? | Hypernode
68
redirect_from:
79
- /en/hypernode/nginx/how-to-configure-your-shop-to-only-use-https/

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,6 @@ To redirect all traffic to www you have to create both a vhost for the Apex and
3434
| www.example.com | magento2 | False | False | False | False | intermediate |
3535
```
3636

37-
<!-- Legacy nginx instructions removed: Hypernode platform uses Managed Vhosts across the board. -->
38-
3937
## Redirect From WWW to Apex
4038

4139
To redirect all traffic from www to the apex domain use the following Nginx snippet:

docs/hypernode-platform/nginx/hypernode-managed-vhosts.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,5 +124,3 @@ If you are running into issues (e.g. SSL or other configuration errors) with Hyp
124124
`hypernode-manage-vhosts --all`
125125

126126
This regenerates the HMV configuration based on what is set in `hypernode-manage-vhosts --list` and in our experience resolves most basic issues with Hypernode Managed Vhosts.
127-
128-
##

docs/hypernode-platform/ssl/how-to-upgrade-your-ssl-settings-to-an-a.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ It is possible to switch to the [Modern Compatibility Settings](https://wiki.moz
3535

3636
#### Mozilla Modern Configuration and Hypernode Managed Vhosts
3737

38-
The Hypernode Managed Vhosts (HMV) system is currently enabled by default on all new booted Hypernodes (booted after 01-05-2020). Read more about HMV [here](../nginx/hypernode-managed-vhosts.md).
38+
Hypernode uses Managed Vhosts (HMV) for per-domain configuration. Read more about HMV [here](../nginx/hypernode-managed-vhosts.md).
3939

4040
When you have different vhosts configured, you also need to enable the SSL config **per vhost**. You do this by running this command:
4141

docs/hypernode-platform/ssl/how-to-use-lets-encrypt-on-hypernode.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,6 @@ If you have Let's Encrypt configured for your vhost, but want to add a third par
4545
1. Install the third party certificate.
4646
1. Run `hypernode-manage-vhosts example.com --https --ssl-noclobber` to configure HTTPS for your vhost without overwriting the third party certificate.
4747

48-
<!-- Legacy dehydrated flow removed: Hypernode platform uses Managed Vhosts across the board. -->
49-
5048
## Troubleshooting
5149

5250
- By default, `dehydrated` renews Let's Encrypt certificates 30 days before expiring.

0 commit comments

Comments
 (0)