forgot to update repo

5 files changed, 24 insertions, 23 deletions

diff --git a/blog/dst/a/xmpp_server_with_prosody.html b/blog/dst/a/xmpp_server_with_prosody.html
index d25de3f..a2a09c2 100644
--- a/blog/dst/a/xmpp_server_with_prosody.html
+++ b/blog/dst/a/xmpp_server_with_prosody.html
@@ -416,7 +416,7 @@ Component "vjud.your.domain" "vjud"
 <p>You <mark>HAVE</mark> to read all of the configuration file, because there are a lot of things that you need to change to make it work with your server/domain. Test the configuration file with:</p>
 <pre><code class="language-sh">luac5.2 -p /etc/prosody/prosody.cfg.lua
 </code></pre>
-<p>Notice that by default <code>prosody</code> will look up certificates that look like <code>sub.your.domain</code>, but if you get the certificates as myself, you&rsquo;ll have a single certificate for all subdomains, and by default it is in <code>/etc/letsencrypt/live</code>, which has some strict permissions. So, to import them you can run:</p>
+<p>Notice that by default <code>prosody</code> will look up certificates that look like <code>sub.your.domain</code>, but if you get the certificates like I do, you&rsquo;ll have a single certificate for all subdomains, and by default it is in <code>/etc/letsencrypt/live</code>, which has some strict permissions. So, to import it you can run:</p>
 <pre><code class="language-sh">prosodyctl --root cert import /etc/letsencrypt/live
 </code></pre>
 <p>Ignore the complaining about not finding the subdomain certificates and note that you will have to run that command on each certificate renewal, to automate this, add the <code>--deploy-hook</code> flag to your automated Certbot renewal system; for me it&rsquo;s a <code>systemd</code> timer with the following <code>certbot.service</code>:</p>
@@ -550,7 +550,7 @@ systemctl restart nginx.service
 <pre><code class="language-sh">pacman -S coturn
 </code></pre>
 <p>You can modify the configuration file (located at <code>/etc/turnserver/turnserver.conf</code>) as desired, but at least you need to make the following changes (uncomment or edit):</p>
-<pre><code>use-auth-secret
+<pre><code class="language-ini">use-auth-secret
 realm=proxy.your.domain
 static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
 </code></pre>
@@ -562,11 +562,11 @@ systemctl enable turnserver.service
 <p>You can test if your TURN server works at <a href="https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/">Trickle ICE</a>. You may need to add a user in the <code>turnserver.conf</code> to test this.</p>
 <h2 id="wrapping-up">Wrapping up</h2>
 <p>At this point you should have a working XMPP server, start/enable the <code>prosody</code> service now:</p>
-<pre><code>systemctl start prosody.service
+<pre><code class="language-sh">systemctl start prosody.service
 systemctl enable prosody.service
 </code></pre>
 <p>And you can add your first user with the <code>prosodyctl</code> command (it will prompt you to add a password):</p>
-<pre><code>prosodyctl adduser user@your.domain
+<pre><code class="language-sh">prosodyctl adduser user@your.domain
 </code></pre>
 <p>You may want to add a <code>compliance</code> user, so you can check if your server is set up correctly. To do so, go to <a href="https://compliance.conversations.im/add/">XMPP Compliance Tester</a> and enter the <code>compliance</code> user credentials. It should have similar compliance score to mine:</p>
 <p><a href='https://compliance.conversations.im/server/luevano.xyz'><img src='https://compliance.conversations.im/badge/luevano.xyz'></a></p>
@@ -597,6 +597,7 @@ systemctl enable prosody.service
   <div class="article-info">
     <p>By David Luévano</p>
     <p>Created: Wed, Jun 09, 2021 @ 05:24 UTC</p>
+      <p>Modified: Thu, Jun 10, 2021 @ 04:42 UTC</p>
     <div class="article-tags">
   <p>Tags:
 <a href="https://blog.luevano.xyz/tag/@english.html">english</a>, <a href="https://blog.luevano.xyz/tag/@server.html">server</a>, <a href="https://blog.luevano.xyz/tag/@tools.html">tools</a>, <a href="https://blog.luevano.xyz/tag/@tutorial.html">tutorial</a>  </p>
diff --git a/blog/dst/rss.xml b/blog/dst/rss.xml
index dd2556d..f796c37 100644
--- a/blog/dst/rss.xml
+++ b/blog/dst/rss.xml
@@ -13,8 +13,8 @@
     <copyright>Copyright 2021 David Luévano Alvarado</copyright>
     <managingEditor>david@luevano.xyz (David Luévano Alvarado)</managingEditor>
     <webMaster>david@luevano.xyz (David Luévano Alvarado)</webMaster>
-    <pubDate>Wed, 09 Jun 2021 05:24:56 GMT</pubDate>
-    <lastBuildDate>Wed, 09 Jun 2021 05:24:56 GMT</lastBuildDate>
+    <pubDate>Thu, 10 Jun 2021 04:42:19 GMT</pubDate>
+    <lastBuildDate>Thu, 10 Jun 2021 04:42:19 GMT</lastBuildDate>
     <generator>pyssg v0.5.9</generator>
     <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
     <ttl>30</ttl>
@@ -371,7 +371,7 @@ Component &quot;vjud.your.domain&quot; &quot;vjud&quot;
 <p>You <mark>HAVE</mark> to read all of the configuration file, because there are a lot of things that you need to change to make it work with your server/domain. Test the configuration file with:</p>
 <pre><code class="language-sh">luac5.2 -p /etc/prosody/prosody.cfg.lua
 </code></pre>
-<p>Notice that by default <code>prosody</code> will look up certificates that look like <code>sub.your.domain</code>, but if you get the certificates as myself, you&rsquo;ll have a single certificate for all subdomains, and by default it is in <code>/etc/letsencrypt/live</code>, which has some strict permissions. So, to import them you can run:</p>
+<p>Notice that by default <code>prosody</code> will look up certificates that look like <code>sub.your.domain</code>, but if you get the certificates like I do, you&rsquo;ll have a single certificate for all subdomains, and by default it is in <code>/etc/letsencrypt/live</code>, which has some strict permissions. So, to import it you can run:</p>
 <pre><code class="language-sh">prosodyctl --root cert import /etc/letsencrypt/live
 </code></pre>
 <p>Ignore the complaining about not finding the subdomain certificates and note that you will have to run that command on each certificate renewal, to automate this, add the <code>--deploy-hook</code> flag to your automated Certbot renewal system; for me it&rsquo;s a <code>systemd</code> timer with the following <code>certbot.service</code>:</p>
@@ -505,7 +505,7 @@ systemctl restart nginx.service
 <pre><code class="language-sh">pacman -S coturn
 </code></pre>
 <p>You can modify the configuration file (located at <code>/etc/turnserver/turnserver.conf</code>) as desired, but at least you need to make the following changes (uncomment or edit):</p>
-<pre><code>use-auth-secret
+<pre><code class="language-ini">use-auth-secret
 realm=proxy.your.domain
 static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
 </code></pre>
@@ -517,11 +517,11 @@ systemctl enable turnserver.service
 <p>You can test if your TURN server works at <a href="https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/">Trickle ICE</a>. You may need to add a user in the <code>turnserver.conf</code> to test this.</p>
 <h2 id="wrapping-up">Wrapping up</h2>
 <p>At this point you should have a working XMPP server, start/enable the <code>prosody</code> service now:</p>
-<pre><code>systemctl start prosody.service
+<pre><code class="language-sh">systemctl start prosody.service
 systemctl enable prosody.service
 </code></pre>
 <p>And you can add your first user with the <code>prosodyctl</code> command (it will prompt you to add a password):</p>
-<pre><code>prosodyctl adduser user@your.domain
+<pre><code class="language-sh">prosodyctl adduser user@your.domain
 </code></pre>
 <p>You may want to add a <code>compliance</code> user, so you can check if your server is set up correctly. To do so, go to <a href="https://compliance.conversations.im/add/">XMPP Compliance Tester</a> and enter the <code>compliance</code> user credentials. It should have similar compliance score to mine:</p>
 <p><a href='https://compliance.conversations.im/server/luevano.xyz'><img src='https://compliance.conversations.im/badge/luevano.xyz'></a></p>
diff --git a/blog/dst/sitemap.xml b/blog/dst/sitemap.xml
index 13213e7..4707c03 100644
--- a/blog/dst/sitemap.xml
+++ b/blog/dst/sitemap.xml
@@ -4,7 +4,7 @@
    xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
     <url>
       <loc>https://blog.luevano.xyz/a/xmpp_server_with_prosody.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>weekly</changefreq>
       <priority>1.0</priority>
     </url>
@@ -59,43 +59,43 @@
 
     <url>
       <loc>https://blog.luevano.xyz/tag/@english.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
     <url>
       <loc>https://blog.luevano.xyz/tag/@server.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
     <url>
       <loc>https://blog.luevano.xyz/tag/@short.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
     <url>
       <loc>https://blog.luevano.xyz/tag/@spanish.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
     <url>
       <loc>https://blog.luevano.xyz/tag/@tools.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
     <url>
       <loc>https://blog.luevano.xyz/tag/@tutorial.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
     <url>
       <loc>https://blog.luevano.xyz/tag/@update.html</loc>
-      <lastmod>2021-06-09</lastmod>
+      <lastmod>2021-06-10</lastmod>
       <changefreq>daily</changefreq>
       <priority>0.5</priority>
     </url>
diff --git a/blog/src/.files b/blog/src/.files
index 979a2f6..7d88a59 100644
--- a/blog/src/.files
+++ b/blog/src/.files
@@ -9,4 +9,4 @@ a/mail_server_with_postfix.md 1616299559.6570284 1623137344.8639452 english,serv
 a/new_blogging_system.md 1622172099.117893 1622173322.4337702 english,short,tools,update
 a/asi_nomas_esta_quedando.md 1622795043.0874712 0.0 short,spanish,update
 a/acomodada_la_pagina_de_arte.md 1623006369.6071973 1623006525.2665823 short,spanish,update
-a/xmpp_server_with_prosody.md 1623216270.0372887 0.0 english,server,tools,tutorial
+a/xmpp_server_with_prosody.md 1623216270.0372887 1623300135.5528305 english,server,tools,tutorial
diff --git a/blog/src/a/xmpp_server_with_prosody.md b/blog/src/a/xmpp_server_with_prosody.md
index be3d610..e5d9607 100644
--- a/blog/src/a/xmpp_server_with_prosody.md
+++ b/blog/src/a/xmpp_server_with_prosody.md
@@ -364,7 +364,7 @@ You ???HAVE??? to read all of the configuration file, because there are a lot of
 luac5.2 -p /etc/prosody/prosody.cfg.lua
 ```
 
-Notice that by default `prosody` will look up certificates that look like `sub.your.domain`, but if you get the certificates as myself, you'll have a single certificate for all subdomains, and by default it is in `/etc/letsencrypt/live`, which has some strict permissions. So, to import them you can run:
+Notice that by default `prosody` will look up certificates that look like `sub.your.domain`, but if you get the certificates like I do, you'll have a single certificate for all subdomains, and by default it is in `/etc/letsencrypt/live`, which has some strict permissions. So, to import it you can run:
 
 ```sh
 prosodyctl --root cert import /etc/letsencrypt/live
@@ -534,7 +534,7 @@ pacman -S coturn
 
 You can modify the configuration file (located at `/etc/turnserver/turnserver.conf`) as desired, but at least you need to make the following changes (uncomment or edit):
 
-```
+```ini
 use-auth-secret
 realm=proxy.your.domain
 static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
@@ -555,14 +555,14 @@ You can test if your TURN server works at [Trickle ICE](https://webrtc.github.io
 
 At this point you should have a working XMPP server, start/enable the `prosody` service now:
 
-```
+```sh
 systemctl start prosody.service
 systemctl enable prosody.service
 ```
 
 And you can add your first user with the `prosodyctl` command (it will prompt you to add a password):
 
-```
+```sh
 prosodyctl adduser user@your.domain
 ```