diff --git a/layouts/_default/list.html b/layouts/_default/list.html index d379e12456b..2995a0e45c4 100644 --- a/layouts/_default/list.html +++ b/layouts/_default/list.html @@ -3,28 +3,6 @@ {{ end }} {{ define "hero" }} -
-
- {{ range $product := $.Site.Sections }} - {{ range $version := .Sections }} - {{ range $language := .Sections }} - {{if $.CurrentSection}} - {{ if .IsAncestor $.CurrentSection }} - {{ .Params.shortTitle }} - {{end}} - {{end}} - {{end}} - {{end}} - {{end}} -
- {{ with .Params.Title }} -

{{ . }}

- {{end}} - - {{ with .Params.Author }} - {{ . }} - {{end}} -
{{ end }} {{ define "main" }} @@ -36,9 +14,14 @@ {{ partial "docs-side-nav.html" . }} -
+
-
+ {{ with .Params.Title }} +

{{ . }}

+
+ {{end}} + +
{{ .Content }} diff --git a/layouts/shortcodes/persistentdata.html b/layouts/shortcodes/persistentdata.html index 38fa799cea4..26110d682b4 100644 --- a/layouts/shortcodes/persistentdata.html +++ b/layouts/shortcodes/persistentdata.html @@ -1,7 +1,7 @@

Rancher uses etcd as datastore. When using the Single Node Install, the embedded etcd is being used. The persistent data is at the following path in the container: /var/lib/rancher. You can bind mount a host volume to this location to preserve data on the host it is running on.

-

Command

+
Command:
 docker run -d --restart=unless-stopped \
diff --git a/layouts/shortcodes/ssl_faq_ha.html b/layouts/shortcodes/ssl_faq_ha.html
index a8142f34d4a..84c0c8f7738 100644
--- a/layouts/shortcodes/ssl_faq_ha.html
+++ b/layouts/shortcodes/ssl_faq_ha.html
@@ -52,7 +52,7 @@ certutil -encode FILENAME FILENAME.base64
 
 

You can validate the certificate chain by using the openssl binary. If the output of the command (see the command example below) ends with Verify return code: 0 (ok), your certificate chain is valid. The ca.pem file must be the same as you added to the rancher/rancher container. When using a certificate signed by a recognized Certificate Authority, you can omit the -CAfile parameter.

-

Command

+
Command:
 openssl s_client -CAfile ca.pem -connect rancher.yourdomain.com:443
 ...
diff --git a/layouts/shortcodes/ssl_faq_single.html b/layouts/shortcodes/ssl_faq_single.html
index 999810a4dd4..aa3d2acefae 100644
--- a/layouts/shortcodes/ssl_faq_single.html
+++ b/layouts/shortcodes/ssl_faq_single.html
@@ -34,7 +34,7 @@ VWQqljhfacYPgp8KJUJENQ9h5hZ2nSCrI+W00Jcw4QcEdCI8HL5wmg==
 
 

You can validate the certificate chain by using the openssl binary. If the output of the command (see the command example below) ends with Verify return code: 0 (ok), your certificate chain is valid. The ca.pem file must be the same as you added to the rancher/rancher container. When using a certificate signed by a recognized Certificate Authority, you can omit the -CAfile parameter.

-

Command

+
Command:
 openssl s_client -CAfile ca.pem -connect rancher.yourdomain.com:443
 ...