From 2c6de158a32516c2517922537ceade07e374a17c Mon Sep 17 00:00:00 2001 From: David Luevano Alvarado Date: Fri, 2 Jun 2023 21:48:00 -0600 Subject: add update entry on tutorial entries titles --- db/db_blog.psv | 1 + live/blog/a/al_fin_tengo_fibra_opticona.html | 6 + live/blog/a/learned_go_and_lua_hard_way.html | 153 +++++++++++++++++++++ live/blog/index.html | 1 + live/blog/rss.xml | 22 +++ live/blog/sitemap.xml | 6 + live/blog/tag/@english.html | 1 + live/blog/tag/@rant.html | 1 + live/blog/tag/@short.html | 1 + live/blog/tag/@tools.html | 1 + .../a/updating_creating_entries_titles_to_setup.md | 11 ++ 11 files changed, 204 insertions(+) create mode 100644 live/blog/a/learned_go_and_lua_hard_way.html create mode 100644 src/blog/a/updating_creating_entries_titles_to_setup.md diff --git a/db/db_blog.psv b/db/db_blog.psv index 0388330..5ba840c 100644 --- a/db/db_blog.psv +++ b/db/db_blog.psv @@ -20,3 +20,4 @@ g/gogodot_jam3_devlog_1.md|1654852625.58801|1683219939.7152278|89b18f87b523d721b a/rewrote_pyssg_again.md|1671510665.5266156|1683375981.802067|e7d3dc8a4a2cd2abda2f653c9cbd3049|english,short,tools,update a/updated_pyssg_pymdvar_and_website.md|1683376754.7018104|0.0|442ad5da7342439101abcc076a73cb22|english,short,tools,update 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 diff --git a/live/blog/a/al_fin_tengo_fibra_opticona.html b/live/blog/a/al_fin_tengo_fibra_opticona.html index 5bcbc8b..d62f298 100644 --- a/live/blog/a/al_fin_tengo_fibra_opticona.html +++ b/live/blog/a/al_fin_tengo_fibra_opticona.html @@ -85,6 +85,12 @@

Resulta que ahora sí hay nodos/terminales, de hecho instalaron 3 nuevos y están completamente vacíos, me tocó muy buena suerte y el muy basado del técnico se lo aventó en medio segundo sin ningún pedo, no me pidió nada más que detalles de dónde quería el módem. No tenía efectivo si no le soltaba un varo, se portó muy chingón.

+ + + + Next + + diff --git a/live/blog/a/learned_go_and_lua_hard_way.html b/live/blog/a/learned_go_and_lua_hard_way.html new file mode 100644 index 0000000..aa54a71 --- /dev/null +++ b/live/blog/a/learned_go_and_lua_hard_way.html @@ -0,0 +1,153 @@ + + + + + + +I had to learn Go and Lua the hard way -- Luévano's Blog + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + +
+ +
+
+ +
+

I had to learn Go and Lua the hard way

+ +

TL;DR: I learned Go and Lua the hard way by forking (for fixing):

+ +

In the last couple of days I’ve been setting up a Komga server for manga downloaded using metafates/mangal (upcoming set up entry about it) and everything was fine so far until I tried to download One Piece from MangaDex of which mangal has a built-in scraper. Long story short the issue was that MangaDex’s API only allows requesting manga chapters on chunks of 500 and the way that was being handled was completely wrong, specifics can be found on my commit (and the subsequent minor fix commit).

+

I tried to do a PR, but the project hasn’t been active since Feb 2023 (same reason I didn’t even try to do PRs on the other repos) so I closed it and will start working on my own fork, probaly just merging everything Belphemur‘s fork has to offer, as he’s been working on mangal actively. I could probably just fork from him and/or just submit PR requests to him, but I think I saw some changes I didn’t really like, will have to look more into it.

+

Also, while trying to use some of the custom scrapers I ran into issues with the headless chrome explorer implementation where it didn’t close on each manga chapter download, causig my CPU and Mem usage to get maxed out and losing control of the system, so I had to also fork the metafates/mangal-lua-libs and “fixed” (I say fixed because that wasn’t the issue at the end, it was how the custom scrapers where using it, shitty documentation) the issue by adding the browser.Close() function to the headless Lua API (commit) and merged some commits from the original vadv/gopher-lua-libs just to include any features added to the Lua libs needed.

+

Finally I forked the metafates/mangal-scrapers (which I actually forked NotPhantomX‘s fork as they had included more scrapers from some pull requests) to be able to have updated custom Lua scrapers (in which I also fixed the headless bullshit) and use them on my mangal.

+

So, I went into the rabbit hole of manga scrapping because I wanted to set up my Komga server, and more importantly I had to quickly learn Go and Lua (Lua was easier) and I have to say that Go is super convoluted on the module management, all research I did lead me to totally different responses, but it is just because of different Go versions and the year of the responses.

+ +
+ + + + + Index + + + + + + + Previous + + +
+ + +
+
+

By David Luévano

+

Created: Sat, Jun 03, 2023 @ 03:32 UTC

+
+

Tags: +english, rant, short, tools

+
+ +
+
+ +
+ + + Contact + + + + + Donate + + + + + RSS + + +
+ + + Created with pyssg + + +
+ + Copyright 2023 David Luévano Alvarado + + +
+ + \ No newline at end of file diff --git a/live/blog/index.html b/live/blog/index.html index 81ab48c..551becb 100644 --- a/live/blog/index.html +++ b/live/blog/index.html @@ -88,6 +88,7 @@

Articles

    2023

    +
  • Jun 03 - I had to learn Go and Lua the hard way
  • May 09 - Al fin tengo fibra ópticona
  • May 06 - Updated pyssg to include pymdvar and the website

    • 2022

    diff --git a/live/blog/rss.xml b/live/blog/rss.xml index 0dcff76..975bccd 100644 --- a/live/blog/rss.xml +++ b/live/blog/rss.xml @@ -22,6 +22,28 @@ Luévano's Blog https://blog.luevano.xyz + + I had to learn Go and Lua the hard way + https://blog.luevano.xyz/a/learned_go_and_lua_hard_way.html + https://blog.luevano.xyz/a/learned_go_and_lua_hard_way.html + Sat, 03 Jun 2023 03:32:17 GMT + English + Rant + Short + Tools + Thanks to the issues of a program (mangal) I'm starting to use for my manga media server, I had to learn Go and Lua the hard way so that I can fix it and use it. + TL;DR: I learned Go and Lua the hard way by forking (for fixing):

    + +

    In the last couple of days I’ve been setting up a Komga server for manga downloaded using metafates/mangal (upcoming set up entry about it) and everything was fine so far until I tried to download One Piece from MangaDex of which mangal has a built-in scraper. Long story short the issue was that MangaDex’s API only allows requesting manga chapters on chunks of 500 and the way that was being handled was completely wrong, specifics can be found on my commit (and the subsequent minor fix commit).

    +

    I tried to do a PR, but the project hasn’t been active since Feb 2023 (same reason I didn’t even try to do PRs on the other repos) so I closed it and will start working on my own fork, probaly just merging everything Belphemur‘s fork has to offer, as he’s been working on mangal actively. I could probably just fork from him and/or just submit PR requests to him, but I think I saw some changes I didn’t really like, will have to look more into it.

    +

    Also, while trying to use some of the custom scrapers I ran into issues with the headless chrome explorer implementation where it didn’t close on each manga chapter download, causig my CPU and Mem usage to get maxed out and losing control of the system, so I had to also fork the metafates/mangal-lua-libs and “fixed” (I say fixed because that wasn’t the issue at the end, it was how the custom scrapers where using it, shitty documentation) the issue by adding the browser.Close() function to the headless Lua API (commit) and merged some commits from the original vadv/gopher-lua-libs just to include any features added to the Lua libs needed.

    +

    Finally I forked the metafates/mangal-scrapers (which I actually forked NotPhantomX‘s fork as they had included more scrapers from some pull requests) to be able to have updated custom Lua scrapers (in which I also fixed the headless bullshit) and use them on my mangal.

    +

    So, I went into the rabbit hole of manga scrapping because I wanted to set up my Komga server, and more importantly I had to quickly learn Go and Lua (Lua was easier) and I have to say that Go is super convoluted on the module management, all research I did lead me to totally different responses, but it is just because of different Go versions and the year of the responses.

    ]]>     +     Al fin tengo fibra ópticona https://blog.luevano.xyz/a/al_fin_tengo_fibra_opticona.html diff --git a/live/blog/sitemap.xml b/live/blog/sitemap.xml index 8dc6877..a25e6eb 100644 --- a/live/blog/sitemap.xml +++ b/live/blog/sitemap.xml @@ -45,6 +45,12 @@ 1.0 + + https://blog.luevano.xyz/a/learned_go_and_lua_hard_way.html + 2023-06-03 + weekly + 1.0 + https://blog.luevano.xyz/a/al_fin_tengo_fibra_opticona.html 2023-05-09 diff --git a/live/blog/tag/@english.html b/live/blog/tag/@english.html index effffe1..f405442 100644 --- a/live/blog/tag/@english.html +++ b/live/blog/tag/@english.html @@ -78,6 +78,7 @@

    Articles

      2023

      +
    • Jun 03 - I had to learn Go and Lua the hard way
    • May 06 - Updated pyssg to include pymdvar and the website

      • 2022

    • Dec 20 - Rewrote pyssg again
      • diff --git a/live/blog/tag/@rant.html b/live/blog/tag/@rant.html index 6a81798..f915c7c 100644 --- a/live/blog/tag/@rant.html +++ b/live/blog/tag/@rant.html @@ -78,6 +78,7 @@

      Articles

        2023

        +
      • Jun 03 - I had to learn Go and Lua the hard way
      • May 09 - Al fin tengo fibra ópticona

        • 2022

      • May 15 - Los devs de Android/MIUI me trozaron
        • diff --git a/live/blog/tag/@short.html b/live/blog/tag/@short.html index 1fe0106..1e9d3c3 100644 --- a/live/blog/tag/@short.html +++ b/live/blog/tag/@short.html @@ -78,6 +78,7 @@

        Articles

          2023

          +
        • Jun 03 - I had to learn Go and Lua the hard way
        • May 09 - Al fin tengo fibra ópticona
        • May 06 - Updated pyssg to include pymdvar and the website

          • 2022

          diff --git a/live/blog/tag/@tools.html b/live/blog/tag/@tools.html index 7f177e0..65d22f5 100644 --- a/live/blog/tag/@tools.html +++ b/live/blog/tag/@tools.html @@ -78,6 +78,7 @@

          Articles

            2023

            +
          • Jun 03 - I had to learn Go and Lua the hard way
          • May 06 - Updated pyssg to include pymdvar and the website

            • 2022

          • Dec 20 - Rewrote pyssg again
            • diff --git a/src/blog/a/updating_creating_entries_titles_to_setup.md b/src/blog/a/updating_creating_entries_titles_to_setup.md new file mode 100644 index 0000000..c726804 --- /dev/null +++ b/src/blog/a/updating_creating_entries_titles_to_setup.md @@ -0,0 +1,11 @@ +title: Updated the how-to entries titles +author: David Luévano +lang: en +summary: Just a small update on the title for some old entries. +tags: short + update + english + +One of the main reasons I started "blogging" was basically just to document how I set up stuff up so I can reference them later in the future if I ever needed to replicate the steps or just to show somebody, and these entries had helped to do so multiple times. I'll keep creating these entries but after a while the *Creating a* title started to feel weird, because we're not *creating* anything really, it is just a set up/configuration/how-to/etc. So I think that using *Set up a* for the titles is better and makes more sense; probably using *How to set up a* is better for the SEO bullshit. + +Anyways, so I'll start using *Set up a* instead of *Creating a* and will retroactively change the titles for these entries (by this entry the change should be applied already). This might impact some RSS feeds as they keep up a cache of the feed and might duplicate the entries, heads up if for some reason somebody is using it. -- cgit v1.2.3-70-g09d2