rebuild manga entry

4 files changed, 15 insertions, 11 deletions

diff --git a/db/db_blog.psv b/db/db_blog.psv
index 9c40636..301abfa 100644
--- a/db/db_blog.psv
+++ b/db/db_blog.psv
@@ -22,5 +22,5 @@ a/updated_pyssg_pymdvar_and_website.md|1683376754.7018104|0.0|442ad5da7342439101
 a/al_fin_tengo_fibra_opticona.md|1683622740.1853704|0.0|949b8fd2aca929d74d8217474c990515|rant,short,spanish,update

 a/learned_go_and_lua_hard_way.md|1685763137.7581403|0.0|493f86ce317f7b182b62c3438e5f7a8a|english,rant,short,tools

 a/updating_creating_entries_titles_to_setup.md|1685764004.1478639|0.0|2bcf247ed5c2aa9fd5f4b542043123fe|english,short,update

-a/manga_server_with_komga.md|1686425767.8936074|1686653315.6535006|7c33a7604565de1300710ce0add53944|code,english,server,tools,tutorial

+a/manga_server_with_komga.md|1686425767.8936074|1687297399.155358|fe34586cace9c117f29445b83f6944c5|code,english,server,tools,tutorial

 a/arch_logs_flooding_disk.md|1686824540.5338242|1686824666.933781|261eeee98ecbb22399f1253697b12353|code,english,server,short,tools,tutorial

diff --git a/live/blog/a/manga_server_with_komga.html b/live/blog/a/manga_server_with_komga.html
index 21c5305..1659d61 100644
--- a/live/blog/a/manga_server_with_komga.html
+++ b/live/blog/a/manga_server_with_komga.html
@@ -113,9 +113,11 @@
 </ul>
 </li>
 <li><a href="#komga">Komga</a><ul>
-<li><a href="#reverse-proxy">Reverse proxy</a></li>
+<li><a href="#reverse-proxy">Reverse proxy</a><ul>
 <li><a href="#ssl-certificate">SSL certificate</a></li>
-<li><a href="#starting-using-komga">Starting using Komga</a></li>
+</ul>
+</li>
+<li><a href="#start-using-komga">Start using Komga</a></li>
 <li><a href="#library-creation">Library creation</a><ul>
 <li><a href="#set-default-directory-permissions">Set default directory permissions</a></li>
 <li><a href="#populate-manga-library">Populate manga library</a></li>
@@ -406,14 +408,14 @@ KOMGA_DATABASE_BACKUP_SCHEDULE=&quot;0 0 */8 * * ?&quot;
 }
 </code></pre>
 <p>If it&rsquo;s going to be used as a subdir on another domain then just change the <code>location</code> with <code>/subdir</code> instead of <code>/</code>; be careful with the <code>proxy_pass</code> directive, it has to match what you configured at <code>/etc/komga.conf</code> for the <code>SERVER_SERVLET_CONTEXT_PATH</code> regardless of the <code>/subdir</code> you selected at <code>location</code>.</p>
-<h3 id="ssl-certificate">SSL certificate<a class="headerlink" href="#ssl-certificate" title="Permanent link">&para;</a></h3>
+<h4 id="ssl-certificate">SSL certificate<a class="headerlink" href="#ssl-certificate" title="Permanent link">&para;</a></h4>
 <p>If using a subdir then the same certificate for the subdomain/domain should work fine and no extra stuff is needed, else if following along me then we can create/extend the certificate by running:</p>
 <pre><code class="language-sh">certbot --nginx
 </code></pre>
 <p>That will automatically detect the new subdomain config and create/extend your existing certificate(s). In my case I manage each certificate&rsquo;s subdomain:</p>
 <pre><code class="language-sh">certbot --nginx -d domainname.com -d subdomain.domainname.com -d komga.domainname.com
 </code></pre>
-<h3 id="starting-using-komga">Starting using Komga<a class="headerlink" href="#starting-using-komga" title="Permanent link">&para;</a></h3>
+<h3 id="start-using-komga">Start using Komga<a class="headerlink" href="#start-using-komga" title="Permanent link">&para;</a></h3>
 <p>We can now <code>start</code>/<code>enable</code> the <code>komga.service</code>:</p>
 <pre><code class="language-sh">systemctl enable komga.service
 systemctl start komga.service
@@ -495,7 +497,7 @@ default:other::r-x
   <div class="article-info">
     <p>By David Luévano</p>
     <p>Created: Sat, Jun 10, 2023 @ 19:36 UTC</p>
-      <p>Modified: Tue, Jun 13, 2023 @ 10:48 UTC</p>
+      <p>Modified: Tue, Jun 20, 2023 @ 21:43 UTC</p>
     <div class="article-tags">
   <p>Tags:
 <a href="https://blog.luevano.xyz/tag/@code.html">code</a>, <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/live/blog/rss.xml b/live/blog/rss.xml
index 79e1c87..12a2e7c 100644
--- a/live/blog/rss.xml
+++ b/live/blog/rss.xml
@@ -103,9 +103,11 @@ LogNamespace=email
 </ul>
 </li>
 <li><a href="#komga">Komga</a><ul>
-<li><a href="#reverse-proxy">Reverse proxy</a></li>
+<li><a href="#reverse-proxy">Reverse proxy</a><ul>
 <li><a href="#ssl-certificate">SSL certificate</a></li>
-<li><a href="#starting-using-komga">Starting using Komga</a></li>
+</ul>
+</li>
+<li><a href="#start-using-komga">Start using Komga</a></li>
 <li><a href="#library-creation">Library creation</a><ul>
 <li><a href="#set-default-directory-permissions">Set default directory permissions</a></li>
 <li><a href="#populate-manga-library">Populate manga library</a></li>
@@ -396,14 +398,14 @@ KOMGA_DATABASE_BACKUP_SCHEDULE=&quot;0 0 */8 * * ?&quot;
 }
 </code></pre>
 <p>If it&rsquo;s going to be used as a subdir on another domain then just change the <code>location</code> with <code>/subdir</code> instead of <code>/</code>; be careful with the <code>proxy_pass</code> directive, it has to match what you configured at <code>/etc/komga.conf</code> for the <code>SERVER_SERVLET_CONTEXT_PATH</code> regardless of the <code>/subdir</code> you selected at <code>location</code>.</p>
-<h3 id="ssl-certificate">SSL certificate<a class="headerlink" href="#ssl-certificate" title="Permanent link">&para;</a></h3>
+<h4 id="ssl-certificate">SSL certificate<a class="headerlink" href="#ssl-certificate" title="Permanent link">&para;</a></h4>
 <p>If using a subdir then the same certificate for the subdomain/domain should work fine and no extra stuff is needed, else if following along me then we can create/extend the certificate by running:</p>
 <pre><code class="language-sh">certbot --nginx
 </code></pre>
 <p>That will automatically detect the new subdomain config and create/extend your existing certificate(s). In my case I manage each certificate&rsquo;s subdomain:</p>
 <pre><code class="language-sh">certbot --nginx -d domainname.com -d subdomain.domainname.com -d komga.domainname.com
 </code></pre>
-<h3 id="starting-using-komga">Starting using Komga<a class="headerlink" href="#starting-using-komga" title="Permanent link">&para;</a></h3>
+<h3 id="start-using-komga">Start using Komga<a class="headerlink" href="#start-using-komga" title="Permanent link">&para;</a></h3>
 <p>We can now <code>start</code>/<code>enable</code> the <code>komga.service</code>:</p>
 <pre><code class="language-sh">systemctl enable komga.service
 systemctl start komga.service
diff --git a/live/blog/sitemap.xml b/live/blog/sitemap.xml
index 1695776..e72cbb7 100644
--- a/live/blog/sitemap.xml
+++ b/live/blog/sitemap.xml
@@ -53,7 +53,7 @@
     </url>
     <url>
       <loc>https://blog.luevano.xyz/a/manga_server_with_komga.html</loc>
-      <lastmod>2023-06-13</lastmod>
+      <lastmod>2023-06-20</lastmod>
       <changefreq>weekly</changefreq>
       <priority>1.0</priority>
     </url>