Update site from docs source repo

Author: Exploding Labs Bot

superstack/bluegreen/index.html

@@ -463,18 +463,18 @@
 </li>
 
           <li class="md-nav__item">
-  <a href="#set-the-caddy-container-name-explicitly" class="md-nav__link">
+  <a href="#serve-http-only-in-the-stacks" class="md-nav__link">
     <span class="md-ellipsis">
-      Set the Caddy container name explicitly
+      Serve HTTP-only in the stacks
     </span>
   </a>
 
 </li>
 
           <li class="md-nav__item">
-  <a href="#serve-http-only-in-the-stacks" class="md-nav__link">
+  <a href="#set-the-caddy-container-name-explicitly" class="md-nav__link">
     <span class="md-ellipsis">
-      Serve http-only in the stacks
+      Set the Caddy container name explicitly
     </span>
   </a>
 
@@ -622,18 +622,18 @@
 </li>
 
           <li class="md-nav__item">
-  <a href="#set-the-caddy-container-name-explicitly" class="md-nav__link">
+  <a href="#serve-http-only-in-the-stacks" class="md-nav__link">
     <span class="md-ellipsis">
-      Set the Caddy container name explicitly
+      Serve HTTP-only in the stacks
     </span>
   </a>
 
 </li>
 
           <li class="md-nav__item">
-  <a href="#serve-http-only-in-the-stacks" class="md-nav__link">
+  <a href="#set-the-caddy-container-name-explicitly" class="md-nav__link">
     <span class="md-ellipsis">
-      Serve http-only in the stacks
+      Set the Caddy container name explicitly
     </span>
   </a>
 
@@ -737,18 +737,18 @@ <h3 id="remove-exposed-ports">Remove exposed ports</h3>
 <p>Remove the <code>caddy</code> service's <code>ports:</code> section in <code>compose.yaml</code>.</p>
 <p>We'll no longer expose ports in the stacks, instead a simple "front proxy" will
 sit in front of the two stacks, proxying to the active stack.</p>
+<h3 id="serve-http-only-in-the-stacks">Serve HTTP-only in the stacks</h3>
+<p>Set <code>CADDY_SITE_ADDRESS</code> to only <code>:80</code>, removing <code>:443</code> (leaving TLS
+termination to the front proxy):</p>
+<div class="highlight"><span class="filename">compose.yaml</span><pre><span></span><code><span class="nt">caddy</span><span class="p">:</span>
+<span class="w">  </span><span class="nt">environment</span><span class="p">:</span>
+<span class="w">    </span><span class="nt">CADDY_SITE_ADDRESS</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">:80</span>
+</code></pre></div>
 <h3 id="set-the-caddy-container-name-explicitly">Set the Caddy container name explicitly</h3>
 <p>This allows us to switch between the two stacks:</p>
 <div class="highlight"><span class="filename">compose.yaml</span><pre><span></span><code><span class="nt">caddy</span><span class="p">:</span>
 <span class="w">  </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">${STACK_NAME}_caddy</span>
 </code></pre></div>
-<h3 id="serve-http-only-in-the-stacks">Serve http-only in the stacks</h3>
-<p>Set <code>CADDY_SITE_ADDRESS</code> to only <code>:80</code> (leaving TLS termination to the front
-proxy):</p>
-<div class="highlight"><span class="filename">compose.yaml</span><pre><span></span><code><span class="nt">caddy</span><span class="p">:</span>
-<span class="w">  </span><span class="nt">environment</span><span class="p">:</span>
-<span class="w">    </span><span class="nt">CADDY_SITE_ADDRESS</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">:80</span>
-</code></pre></div>
 <h3 id="move-postgres-to-its-own-unique-container">Move Postgres to its own unique container</h3>
 <p>Running two separate PostgreSQL instances and having them both simultaneously
 access the same data directory within that shared volume is not recommended and