moved resusable content to shortcodes

This commit is contained in:
Mark Bishop
2018-05-09 13:53:20 -07:00
committed by Mark Bishop
parent 3e93983e8d
commit 134b2c29fc
10 changed files with 51 additions and 496 deletions
+11
View File
@@ -0,0 +1,11 @@
<div>
<p>Rancher uses etcd as datastore. When using the Single Node Install, the embedded etcd will be used. The persistent data will be stored in <code>/var/lib/rancher</code> inside the container. You can bind mount a host volume to this location to preserve data on the host it is running on.</p>
<p><b>Command</b></p>
<pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4">
docker run -d -p 80:80 -p 443:443 \
-v /host/rancher:/var/lib/rancher \
rancher/rancher
</pre>
</div>
+38
View File
@@ -0,0 +1,38 @@
<h3>How do I know if my certificates are in PEM format?</h3>
<p>You can recognize the PEM format by:</p>
<p><strong>Starting with:</strong> <code>-----BEGIN CERTIFICATE-----</code></p>
<p><strong>Ending with:</strong> <code>-----END CERTIFICATE-----</code></p>
<p><strong>Example of a PEM certificate</strong></p>
<pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4">
----BEGIN CERTIFICATE-----
MIIGVDCCBDygAwIBAgIJAMiIrEm29kRLMA0GCSqGSIb3DQEBCwUAMHkxCzAJBgNV
... more lines
VWQqljhfacYPgp8KJUJENQ9h5hZ2nSCrI+W00Jcw4QcEdCI8HL5wmg==
-----END CERTIFICATE-----
</pre>
<h3>What is the order of certificates in case I want to add my intermediate(s)?</h3>
<p>The order of adding certificates is as follows:</p>
<pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4">
-----BEGIN CERTIFICATE-----
(Your certificate)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Your intermediate certificate)
-----END CERTIFICATE-----
</pre>
<h3>How do I validate my certificate chain?</h3>
<p>You can validate the certificate chain by using the <code>openssl</code> binary. If the output of the command (see the command example below) ends with <code>Verify return code: 0 (ok)</code>, your certificate chain is valid. The <code>ca.pem</code> file should be the same as you supplied to the <code>rancher/rancher</code> container. When using a certificate signed by a well known Certificate Authority, you can omit the <code>-CAfile</code> parameter.</p>
<p><strong>Command</strong></p>
<pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4">
openssl s_client -CAfile ca.pem -connect rancher.yourdomain.com:443
...
Verify return code: 0 (ok)
</pre>