Skip to content

Commit 89f0ffa

Browse files
authored
Merge pull request docker-mailserver#142 from Frankst2/patch-1
Update line numbers in links in README.md
2 parents 922448c + 42f02f0 commit 89f0ffa

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

charts/docker-mailserver/Chart.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ apiVersion: v2
22
appVersion: "14.0.0"
33
description: A fullstack but simple mailserver (smtp, imap, antispam, antivirus, ssl...) using Docker.
44
name: docker-mailserver
5-
version: 4.1.1
5+
version: 4.1.2
66
sources:
77
- https://github.com/docker-mailserver/docker-mailserver-helm
88
maintainers:

charts/docker-mailserver/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,11 +98,11 @@ Configuration files are stored on a Kubernetes [volume](#persistence) mounted at
9898

9999
### ConfigMaps
100100

101-
Its is also possible to use ConfigMaps to mount configuration files in the container. This is done by adding to the `configFiles` key in a custom `values.yaml` file. For more information please see the [documentation](./values.yaml#L425) in values.yaml
101+
Its is also possible to use ConfigMaps to mount configuration files in the container. This is done by adding to the `configFiles` key in a custom `values.yaml` file. For more information please see the [documentation](./values.yaml#L453) in values.yaml
102102

103103
### Secrets
104104

105-
Secrets can also be used to mount configuration files in the container. For example, dkim keys could be stored in a secret as opposed to a file in the `mail-config` volume. Once again, for more information please see the [documentation](./values.yaml#L600) in values.yaml
105+
Secrets can also be used to mount configuration files in the container. For example, dkim keys could be stored in a secret as opposed to a file in the `mail-config` volume. Once again, for more information please see the [documentation](./values.yaml#L610) in values.yaml
106106

107107
## Values YAML
108108

0 commit comments

Comments
 (0)