Skip to content

Commit d3c15ef

Browse files
martijneichelsheimmartijneichelsheim
committed
mdformat files
1 parent 066dcf3 commit d3c15ef

File tree

3 files changed

+35
-26
lines changed

3 files changed

+35
-26
lines changed

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

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,15 @@
1-
---
1+
______________________________________________________________________
2+
23
myst:
3-
html_meta:
4-
description: Varnish is a complex technique that needs some experience to set
5-
it up. This article explains how you can configure Varnish 4 or 6 for your Hypernode.
6-
title: How to configure Varnish for Magento 2? | Hypernode
4+
html_meta:
5+
description: Varnish is a complex technique that needs some experience to set
6+
it up. This article explains how you can configure Varnish 4 or 6 for your Hypernode.
7+
title: How to configure Varnish for Magento 2? | Hypernode
78
redirect_from:
8-
- /en/ecommerce/magento-2/how-to-configure-varnish-for-magento-2-x/
9-
---
9+
10+
- /en/ecommerce/magento-2/how-to-configure-varnish-for-magento-2-x/
11+
12+
______________________________________________________________________
1013

1114
<!-- source: https://support.hypernode.com/en/ecommerce/magento-2/how-to-configure-varnish-for-magento-2-x/ -->
1215

@@ -116,7 +119,7 @@ Make sure you change this to the aforementioned configuration (without the healt
116119
The `acl purge` block inside your vcl should contain the private ip range of your cluster.
117120
You can find your private ip range using the `hypernode-cluster-info` command on one of your cluster nodes.
118121

119-
As example, our private ip range is `192.168.1.0/24`.
122+
As example, our private ip range is `192.168.1.0/24`.
120123
You can add this to the `acl purge` block. It should like something similar as the example below:
121124

122125
```

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

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,16 @@
1-
---
1+
______________________________________________________________________
2+
23
myst:
3-
html_meta:
4-
description: Shopware 5 applications can greatly benefit from Varnish caching.
5-
Hypernode supports Varnish as a caching layer and configuration is actually
6-
quite simple.
7-
title: How to configure Varnish for Shopware 5? | Hypernode
4+
html_meta:
5+
description: Shopware 5 applications can greatly benefit from Varnish caching.
6+
Hypernode supports Varnish as a caching layer and configuration is actually
7+
quite simple.
8+
title: How to configure Varnish for Shopware 5? | Hypernode
89
redirect_from:
9-
- /en/support/solutions/articles/48001207016-how-to-configure-varnish-for-shopware-5/
10-
---
10+
11+
- /en/support/solutions/articles/48001207016-how-to-configure-varnish-for-shopware-5/
12+
13+
______________________________________________________________________
1114

1215
<!-- source: https://support.hypernode.com/en/support/solutions/articles/48001207016-how-to-configure-varnish-for-shopware-5/ -->
1316

@@ -44,7 +47,7 @@ Copy the VCL configuration from [Shopware's documentation](https://developers.sh
4447
The `acl purgers` block inside your vcl should contain the private ip range of your cluster.
4548
You can find your private ip range using the `hypernode-cluster-info` command on one of your cluster nodes.
4649

47-
As example, our private ip range is `192.168.1.0/24`.
50+
As example, our private ip range is `192.168.1.0/24`.
4851
You can add this to the `acl purgers` block. It should like something similar as the example below:
4952

5053
```vcl

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

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,16 @@
1-
---
1+
______________________________________________________________________
2+
23
myst:
3-
html_meta:
4-
description: Shopware 6 applications can greatly benefit from Varnish caching.
5-
Hypernode supports Varnish as a caching layer and configuration is actually
6-
quite simple.
7-
title: How to configure Varnish for Shopware 6?
4+
html_meta:
5+
description: Shopware 6 applications can greatly benefit from Varnish caching.
6+
Hypernode supports Varnish as a caching layer and configuration is actually
7+
quite simple.
8+
title: How to configure Varnish for Shopware 6?
89
redirect_from:
9-
- /en/support/solutions/articles/48001200525-how-to-configure-varnish-for-shopware-6/
10-
---
10+
11+
- /en/support/solutions/articles/48001200525-how-to-configure-varnish-for-shopware-6/
12+
13+
______________________________________________________________________
1114

1215
<!-- source: https://support.hypernode.com/en/support/solutions/articles/48001200525-how-to-configure-varnish-for-shopware-6/ -->
1316

@@ -96,7 +99,7 @@ To actually use Varnish you need to implement a varnish config file, a .vcl. If
9699
The `acl purgers` block inside your vcl should contain the private ip range of your cluster.
97100
You can find your private ip range using the `hypernode-cluster-info` command on one of your cluster nodes.
98101

99-
As example, our private ip range is `192.168.1.0/24`.
102+
As example, our private ip range is `192.168.1.0/24`.
100103
You can add this to the `acl purgers` block. It should like something similar as the example below:
101104

102105
```vcl

0 commit comments

Comments
 (0)