homelab/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc: improve examples.

Browse source
This commit is contained in:
Ludovic Fernandez 2019-07-22 09:58:04 +02:00 • committed by Traefiker Bot
parent 8b4ba3cb67
commit 75c99a0491
69 changed files with 1256 additions and 552 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/content/https/acme.md
View file

@ -109,7 +109,7 @@ when using the `TLS-ALPN-01` challenge, Traefik must be reachable by Let's Encry
```bash tab="CLI"
# ...
--certificatesResolvers.sample.acme.tlsChallenge
--certificatesResolvers.sample.acme.tlsChallenge=true
```
### `httpChallenge`

7
docs/content/https/ref-acme.txt
View file

@ -1,5 +1,4 @@
# Enable ACME (Let's Encrypt): automatic SSL.
--certificatesResolvers.sample.acme
# Email address used for registration.
#
@ -35,13 +34,13 @@
#
# Optional (but recommended)
#
--certificatesResolvers.sample.acme.tlsChallenge
--certificatesResolvers.sample.acme.tlsChallenge=true
# Use a HTTP-01 ACME challenge.
#
# Optional
#
--certificatesResolvers.sample.acme.httpChallenge
--certificatesResolvers.sample.acme.httpChallenge=true
# EntryPoint to use for the HTTP-01 challenges.
#
@ -54,7 +53,7 @@
#
# Optional
#
--certificatesResolvers.sample.acme.dnsChallenge
--certificatesResolvers.sample.acme.dnsChallenge=true
# DNS provider used.
#

10
docs/content/https/tls.md
View file

@ -35,7 +35,7 @@ tls:
!!! important "File Provider Only"
In the above example, we've used the [file provider](../providers/file.md) to handle these definitions.
In its current alpha version, it is the only available method to configure the certificates (as well as the options and the stores).
In its current beta version, it is the only available method to configure the certificates (as well as the options and the stores).
## Certificates Stores
@ -52,9 +52,9 @@ tls:
default: {}
```
!!! important "Alpha restriction"
!!! important "Beta restriction"
During the alpha version, any store definition other than the default one (named `default`) will be ignored,
During the beta version, any store definition other than the default one (named `default`) will be ignored,
and there is thefore only one globally available TLS store.
In the `tls.certificates` section, a list of stores can then be specified to indicate where the certificates should be stored:
@ -85,9 +85,9 @@ tls:
keyFile: /path/to/other-domain.key
```
!!! important "Alpha restriction"
!!! important "Beta restriction"
During the alpha version, the `stores` list will actually be ignored and automatically set to `["default"]`.
During the beta version, the `stores` list will actually be ignored and automatically set to `["default"]`.
### Default Certificate