my website at https://anirudh.fi
4
fork

Configure Feed

Select the types of activity you want to include in your feed.

Formatting of codeblocks

Signed-off-by: Anirudh Oppiliappan <x@icyphox.sh>

+20 -7
+1 -1
build/blog/feed.xml
··· 74 74 75 75 <p>The next thing I struggled with &#8212; DNS. Specifically, the with the step where 76 76 the DKIM keys are generated<sup class="footnote-ref" id="fnref-2"><a href="#fn-2">2</a></sup>. The output under <br /> 77 - <code>config/opendkim/keys/domain.tld/mail.txt</code> 77 + <code>config/opendkim/keys/domain.tld/mail.txt</code> <br /> 78 78 isn&#8217;t exactly CloudFlare friendly; they can&#8217;t be directly copy-pasted into 79 79 a <code>TXT</code> record. </p> 80 80
+6 -2
build/blog/mailserver/index.html
··· 130 130 <p>Yet another hurdle &#8212; SSL/TLS certificates. This isn&#8217;t very properly 131 131 documented, unless you read through the <a href="https://github.com/tomav/docker-mailserver/wiki/Installation-Examples">wiki</a> 132 132 and look at an example. In short, install <code>certbot</code>, have port 80 free, 133 - and run <code>certbot certonly --standalone -d mail.domain.tld</code>. Once that&#8217;s 134 - done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in 133 + and run </p> 134 + 135 + <div class="codehilite"><pre><span></span><code>$ certbot certonly --standalone -d mail.domain.tld 136 + </code></pre></div> 137 + 138 + <p>Once that&#8217;s done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in 135 139 the container, something like so:</p> 136 140 137 141 <div class="codehilite"><pre><span></span><code><span class="nn">...</span>
+6 -2
pages/blog/feed.xml
··· 102 102 <p>Yet another hurdle &#8212; SSL/TLS certificates. This isn&#8217;t very properly 103 103 documented, unless you read through the <a href="https://github.com/tomav/docker-mailserver/wiki/Installation-Examples">wiki</a> 104 104 and look at an example. In short, install <code>certbot</code>, have port 80 free, 105 - and run <code>certbot certonly --standalone -d mail.domain.tld</code>. Once that&#8217;s 106 - done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in 105 + and run </p> 106 + 107 + <div class="codehilite"><pre><span></span><code>$ certbot certonly --standalone -d mail.domain.tld 108 + </code></pre></div> 109 + 110 + <p>Once that&#8217;s done, edit the <code>docker-compose.yml</code> file to mount <code>/etc/letsencrypt</code> in 107 111 the container, something like so:</p> 108 112 109 113 <div class="codehilite"><pre><span></span><code><span class="nn">...</span>
+7 -2
pages/blog/mailserver.md
··· 90 90 Yet another hurdle --- SSL/TLS certificates. This isn't very properly 91 91 documented, unless you read through the [wiki](https://github.com/tomav/docker-mailserver/wiki/Installation-Examples) 92 92 and look at an example. In short, install `certbot`, have port 80 free, 93 - and run `certbot certonly --standalone -d mail.domain.tld`. Once that's 94 - done, edit the `docker-compose.yml` file to mount `/etc/letsencrypt` in 93 + and run 94 + 95 + ``` shell 96 + $ certbot certonly --standalone -d mail.domain.tld 97 + ``` 98 + 99 + Once that's done, edit the `docker-compose.yml` file to mount `/etc/letsencrypt` in 95 100 the container, something like so: 96 101 ```yaml 97 102 ...