all repos — site @ fc29b8d93aca0ff139d8ef3a4061bdc888680c0d

source for my site, found at icyphox.sh

Formatting of codeblocks

Signed-off-by: Anirudh Oppiliappan <x@icyphox.sh>
Anirudh Oppiliappan x@icyphox.sh
Fri, 16 Aug 2019 00:15:57 +0530
commit

fc29b8d93aca0ff139d8ef3a4061bdc888680c0d

parent

3699f53b7ef138bcf0efac8b2b87f8f57bb9aa28

4 files changed, 20 insertions(+), 7 deletions(-)

jump to
M build/blog/feed.xmlbuild/blog/feed.xml

@@ -74,7 +74,7 @@ <p>But it eventually worked after a couple of attempts.</p>

<p>The next thing I struggled with &#8212; DNS. Specifically, the with the step where the DKIM keys are generated<sup class="footnote-ref" id="fnref-2"><a href="#fn-2">2</a></sup>. The output under <br /> -<code>config/opendkim/keys/domain.tld/mail.txt</code> +<code>config/opendkim/keys/domain.tld/mail.txt</code> <br /> isn&#8217;t exactly CloudFlare friendly; they can&#8217;t be directly copy-pasted into a <code>TXT</code> record. </p>
M build/blog/mailserver/index.htmlbuild/blog/mailserver/index.html

@@ -130,8 +130,12 @@

<p>Yet another hurdle &#8212; SSL/TLS certificates. This isn&#8217;t very properly documented, unless you read through the <a href="https://github.com/tomav/docker-mailserver/wiki/Installation-Examples">wiki</a> and look at an example. In short, install <code>certbot</code>, have port 80 free, -and run <code>certbot certonly --standalone -d mail.domain.tld</code>. Once that&#8217;s -done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in +and run </p> + +<div class="codehilite"><pre><span></span><code>$ certbot certonly --standalone -d mail.domain.tld +</code></pre></div> + +<p>Once that&#8217;s done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in the container, something like so:</p> <div class="codehilite"><pre><span></span><code><span class="nn">...</span>
M pages/blog/feed.xmlpages/blog/feed.xml

@@ -102,8 +102,12 @@

<p>Yet another hurdle &#8212; SSL/TLS certificates. This isn&#8217;t very properly documented, unless you read through the <a href="https://github.com/tomav/docker-mailserver/wiki/Installation-Examples">wiki</a> and look at an example. In short, install <code>certbot</code>, have port 80 free, -and run <code>certbot certonly --standalone -d mail.domain.tld</code>. Once that&#8217;s -done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in +and run </p> + +<div class="codehilite"><pre><span></span><code>$ certbot certonly --standalone -d mail.domain.tld +</code></pre></div> + +<p>Once that&#8217;s done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in the container, something like so:</p> <div class="codehilite"><pre><span></span><code><span class="nn">...</span>
M pages/blog/mailserver.mdpages/blog/mailserver.md

@@ -90,8 +90,13 @@

Yet another hurdle --- SSL/TLS certificates. This isn't very properly documented, unless you read through the [wiki](https://github.com/tomav/docker-mailserver/wiki/Installation-Examples) and look at an example. In short, install `certbot`, have port 80 free, -and run `certbot certonly --standalone -d mail.domain.tld`. Once that's -done, edit the `docker-compose.yml` file to mount `/etc/letsencrypt` in +and run + +``` shell +$ certbot certonly --standalone -d mail.domain.tld +``` + +Once that's done, edit the `docker-compose.yml` file to mount `/etc/letsencrypt` in the container, something like so: ```yaml ...