+ +

Al fin ya me acomodé la página pa' los dibujos

Así es, ya quedó acomodado el sub-dominio art.luevano.xyz pos pal arte veda. Entonces pues ando feliz por eso.

Este pedo fue gracias a que me reescribí la forma en la que pyssg maneja los templates, ahora uso el sistema de jinja en vez del cochinero que hacía antes.

Y pues nada más eso, aquí está el primer post y por supuesto acá está el link del RSS https://art.luevano.xyz/rss.xml.

@@ -107,7 +110,7 @@

By David Luévano

Created: Sun, Jun 06, 2021 @ 19:06 UTC

Modified: Sun, Jun 06, 2021 @ 19:08 UTC

Modified: Thu, May 04, 2023 @ 18:19 UTC

Tags: short, spanish, update

diff --git a/live/blog/a/asi_nomas_esta_quedando.html b/live/blog/a/asi_nomas_esta_quedando.html index c1f9f3f..b275a2c 100644 --- a/live/blog/a/asi_nomas_esta_quedando.html +++ b/live/blog/a/asi_nomas_esta_quedando.html @@ -16,13 +16,11 @@ + + - - - - + + @@ -73,13 +71,19 @@

+ +

Así nomás está quedando el página

Estuve acomodando un poco más el sItIo, al fin agregué la “sección” de contact y de donate por si hay algún loco que quiere tirar varo.

También me puse a acomodar un servidor de XMPP el cual, en pocas palabras, es un protocolo de mensajería instantánea (y más) descentralizado, por lo cual cada quien puede hacer una cuenta en el servidor que quiera y conectarse con cuentas creadas en otro servidor… exacto, como con los correos electrónicos. Y esto está perro porque si tú tienes tu propio server, así como con uno de correo electrónico, puedes controlar qué características tiene, quiénes pueden hacer cuenta, si hay end-to-end encryption (o mínimo end-to-server), entre un montón de otras cosas.

Ahorita este server es SUMISO (compliant en español, jeje) para jalar con la app conversations y con la red social movim, pero realmente funcionaría con casi cualquier cliente de XMPP, amenos que ese cliente implemente algo que no tiene mi server. Y también acomodé un server de Matrix que es muy similar pero es bajo otro protocolo y se siente más como un discord/slack (al menos en el element), muy chingón también.

Si bien aún quedan cosas por hacer sobre estos dos servers que me acomodé (además de hacerles unas entradas para documentar cómo lo hice), quiero moverme a otra cosa que sería acomodar una sección de dibujos, lo cual en teoría es bien sencillo, pero como quiero poder automatizar la publicación de estos, quiero modificar un poco el pyssg para que jale chido para este pex.

Ya por último también quiero moverle un poco al CSS, porque lo dejé en un estado muy culerón y quiero meterle/ajustar unas cosas para que quede más limpio y medianamente bonito… dentro de lo que cabe porque evidentemente me vale verga si se ve como una página del 2000.

Actualización: Ya tumbé el servidor de XMPP porque consumía bastantes recursos y no lo usaba tanto, si en un futuro consigo un mejor servidor podría volver a hostearlo.

@@ -109,6 +113,7 @@

By David Luévano

Created: Fri, Jun 04, 2021 @ 08:24 UTC

Modified: Thu, May 04, 2023 @ 18:18 UTC

Tags: short, spanish, update

diff --git a/live/blog/a/devs_android_me_trozaron.html b/live/blog/a/devs_android_me_trozaron.html index 69239fb..860bd63 100644 --- a/live/blog/a/devs_android_me_trozaron.html +++ b/live/blog/a/devs_android_me_trozaron.html @@ -16,13 +16,11 @@ + + - - - - + + @@ -73,6 +71,11 @@

+ +

Los devs de Android/MIUI me trozaron

Llevo dos semanas posponiendo esta entrada porque andaba bien enojado (todavía, pero ya se anda pasando) y me daba zzz. Pero bueno, antes que nada este pex ocupa un poco de contexto sobre dos cositas:

diff --git a/live/blog/a/el_blog_ya_tiene_timestamps.html b/live/blog/a/el_blog_ya_tiene_timestamps.html index 29c080e..cf9d36d 100644 --- a/live/blog/a/el_blog_ya_tiene_timestamps.html +++ b/live/blog/a/el_blog_ya_tiene_timestamps.html @@ -16,13 +16,12 @@ + + - - - - + + + @@ -73,12 +72,19 @@

+ +

Así es raza, el blog ya tiene timestamps

Pues eso, esta entrada es sólo para tirar update sobre mi primer post. Ya modifiqué el ssg lo suficiente como para que maneje los timestamps, y ya estoy más familiarizado con este script entonces ya lo podré extender más, pero por ahora las entradas ya tienen su fecha de creación (y modificación en dado caso) al final y en el índice ya están organizados por fecha, que por ahora está algo simple pero está sencillo de extender.

Ya lo único que queda es cambiar un poco el formato del blog (y de la página en general), porque en un momento de desesperación puse todo el texto en justificado y pues no se ve chido siempre, entonces queda corregir eso. Y aunque me tomó más tiempo del que quisiera, así nomás quedó, diría un cierto personaje.

El ssg modificado está en mis dotfiles (o directamente aquí).

Por último, también quité las extensiones .html de las URLs, porque se veía bien pitero, pero igual los links con .html al final redirigen a su link sin .html, así que no hay rollo alguno.

~~El ssg modificado está en mis dotfiles (o directamente aquí).~~ +Como al final ya no usé el ssg modificado, este pex ya no existe.

Por último, también quité las extensiones .html de las URLs, porque se ve bien pitero, pero igual los links con .html al final redirigen a su link sin .html, así que no hay rollo alguno.

Actualización: Ahora estoy usando mi propia solución en vez de ssg, que la llamé pyssg, de la cual empiezo a hablar acá.

@@ -108,7 +114,7 @@

By David Luévano

Created: Tue, Mar 16, 2021 @ 02:46 UTC

Modified: Mon, May 17, 2021 @ 20:53 UTC

Modified: Thu, May 04, 2023 @ 18:15 UTC

Tags: short, spanish, tools, update

diff --git a/live/blog/a/first_blog_post.html b/live/blog/a/first_blog_post.html index 6da8afd..d5eb3fd 100644 --- a/live/blog/a/first_blog_post.html +++ b/live/blog/a/first_blog_post.html @@ -16,13 +16,12 @@ + + - - - - + + + @@ -73,11 +72,17 @@

+ +

This is the first blog post, just for testing purposes

I’m making this post just to figure out how ssg5 and lowdown are supposed to work (and eventually also rssg).

At the moment, I’m not satisfied because there’s no automatic date insertion into the 1) html file, 2) the blog post itself and 3) the listing system in the blog homepage (and there’s also the problem with the ordering of the entries…). And all of this just because I didn’t want to use Luke’s solution (don’t really like that much how he handles the scripts… but they just work).

I’m making this post just to figure out how ssg5 and lowdown are supposed to work, and eventually rssg.

At the moment I’m not satisfied because there’s no automatic date insertion into the 1) html file, 2) the blog post itself and 3) the listing system in the blog homepage which also has a problem with the ordering of the entries. And all of this just because I didn’t want to use Luke’s lb solution as I don’t really like that much how he handles the scripts (but they just work).

Hopefully, for tomorrow all of this will be sorted out and I’ll have a working blog system.

Update: I’m now using my own solution which I called pyssg, of which I talk about here.

@@ -101,7 +106,7 @@

By David Luévano

Created: Sat, Feb 27, 2021 @ 13:08 UTC

Modified: Mon, May 17, 2021 @ 20:53 UTC

Modified: Thu, May 04, 2023 @ 18:14 UTC

Tags: english, short, tools, update

diff --git a/live/blog/a/git_server_with_cgit.html b/live/blog/a/git_server_with_cgit.html index defcf3e..3c0bcae 100644 --- a/live/blog/a/git_server_with_cgit.html +++ b/live/blog/a/git_server_with_cgit.html @@ -16,14 +16,21 @@ + + - + + + + + + @@ -73,17 +80,34 @@

+ +

Create a git server and setup cgit web app (on Nginx)

My git server is all I need to setup to actually kill my other server (I’ve been moving from servers on these last 2-3 blog entries), that’s why I’m already doing this entry. I’m basically following git’s guide on setting up a server plus some specific stuff for (btw i use) Arch Linux (Arch Linux Wiki: Git server and Step by step guide on setting up git server in arch linux (pushable)).

Note that this is mostly for personal use, so there’s no user/authentication control other than that of SSH. Also, most if not all commands here are run as root.

Prerequisites¶

My git server is all I need to setup to actually kill my other server (I’ve been moving from servers on these last 2-3 blog entries), that’s why I’m already doing this entry. I’m basically following git’s guide on setting up a server plus some specific stuff for btw i use Arch Linux (Arch Linux Wiki: Git server and Step by step guide on setting up git server in arch linux (pushable)).

Note that this is mostly for personal use, so there’s no user/authentication control other than that of normal ssh. And as with the other entries, most if not all commands here are run as root unless stated otherwise.

Table of contents¶

Table of contents
Prerequisites
Git
Cgit
- Cgit’s file rendering
+

Prerequisites¶

I might get tired of saying this (it’s just copy paste, basically)… but you will need the same prerequisites as before (check my website and mail entries), with the extras:

(Optional, if you want a “front-end”) A CNAME for “git” and (optionally) “www.git”, or some other name for your sub-domains.
An SSL certificate, if you’re following the other entries, add a git.conf and run certbot --nginx to extend the certificate.

Git¶

Git is a version control system.

If not installed already, install the git package:

pacman -S git
@@ -117,11 +141,11 @@ systemctl enable git-daemon.socket

You’re basically done. Now you should be able to push/pull repositories to your server… except, you haven’t created any repository in your server, that’s right, they’re not created automatically when trying to push. To do so, you have to run (while inside /home/git):

git init --bare {repo_name}.git
-chown -R git:git repo_name.git
+chown -R git:git {repo_name}.git

Those two lines above will need to be run each time you want to add a new repository to your server (yeah, kinda lame… although there are options to “automate” this, I like it this way).

Those two lines above will need to be run each time you want to add a new repository to your server. There are options to “automate” this but I like it this way.

After that you can already push/pull to your repository. I have my repositories (locally) set up so I can push to more than one remote at the same time (my server, GitHub, GitLab, etc.); to do so, check this gist.

Cgit¶

Cgit is a fast web interface for git.

This is optionally since it’s only for the web application.

Install the cgit and fcgiwrap packages:

@@ -162,10 +186,9 @@ repo.url={url} repo.path={dir_path} repo.owner={owner} repo.desc={short_description} - ... -

Where you can uncomment the robots line to let web crawlers (like Google’s) to index your git web app. And at the end keep all your repositories (the ones you want to make public), for example for my dotfiles I have:

Where you can uncomment the robots line to not let web crawlers (like Google’s) to index your git web app. And at the end keep all your repositories (the ones you want to make public), for example for my dotfiles I have:

...
 repo.url=.dots
 repo.path=/home/git/.dots.git
@@ -174,6 +197,7 @@ repo.desc=These are my personal dotfiles.
 ...

Otherwise you could let cgit to automatically detect your repositories (you have to be careful if you want to keep “private” repos) using the option scan-path and setup .git/description for each repository. For more, you can check cgitrc(5).

Cgit’s file rendering¶

By default you can’t see the files on the site, you need a highlighter to render the files, I use highlight. Install the highlight package:

pacman -S highlight

@@ -222,10 +246,10 @@ exec highlight --force --inline-css -f -I -O xhtml -S "$EXTENSION" 2&g

By David Luévano

Created: Sun, Mar 21, 2021 @ 19:00 UTC

Modified: Tue, Jun 08, 2021 @ 07:27 UTC

Modified: Fri, May 05, 2023 @ 08:35 UTC

Tags: -english, server, tools, tutorial

+code, english, server, tools, tutorial

diff --git a/live/blog/a/hoy_toco_desarrollo_personaje.html b/live/blog/a/hoy_toco_desarrollo_personaje.html index e67976a..e57dd46 100644 --- a/live/blog/a/hoy_toco_desarrollo_personaje.html +++ b/live/blog/a/hoy_toco_desarrollo_personaje.html @@ -16,13 +16,9 @@ + + - - - - @@ -73,6 +69,11 @@

+ +

Hoy me tocó desarrollo de personaje

Sabía que hoy no iba a ser un día tan bueno, pero no sabía que iba a estar tan horrible; me tocó desarrollo de personaje y saqué el bad ending.

diff --git a/live/blog/a/mail_server_with_postfix.html b/live/blog/a/mail_server_with_postfix.html index c8acc43..95003e5 100644 --- a/live/blog/a/mail_server_with_postfix.html +++ b/live/blog/a/mail_server_with_postfix.html @@ -16,14 +16,21 @@ + + - + + + + + + @@ -73,18 +80,38 @@

+ +

Create a mail server with Postfix, Dovecot, SpamAssassin and OpenDKIM

The entry is going to be long because it’s a tedious process. This is also based on Luke Smith’s script, but adapted to Arch Linux (his script works on debian-based distributions). This entry is mostly so I can record all the notes required while I’m in the process of installing/configuring the mail server on a new VPS of mine; also I’m going to be writing a script that does everything in one go (for Arch Linux), that will be hosted here.

This configuration works for local users (users that appear in /etc/passwd), and does not use any type of SQL Database. And note that most if not all commands executed here are run with root privileges.

Prerequisites¶

The entry is going to be long because it’s a tedious process. This is also based on Luke Smith’s script, but adapted to Arch Linux (his script works on debian-based distributions). This entry is mostly so I can record all the notes required while I’m in the process of installing/configuring the mail server on a new VPS of mine; ~~also I’m going to be writing a script that does everything in one go (for Arch Linux), that will be hosted here.~~ I haven’t had time to do the script so nevermind this, if I ever do it I’ll make a new entry regarding it.

This configuration works for local users (users that appear in /etc/passwd), and does not use any type of SQL database. And note that most if not all commands executed here are run with root privileges, unless stated otherwise.

Prerequisites¶

Basically the same as with the website with Nginx and Certbot, with the extras:

You will need a CNAME for “mail” and (optionally) “www.mail”, or whatever you want to call the sub-domains (although the RFC 2181 states that it NEEDS to be an A record, fuck the police).
An SSL certificate. You can use the SSL certificate obtained following my last post using certbot (just create a mail.conf and run certbot --nginx again).
Ports 25, 587 (SMTP), 465 (SMTPS), 143 (IMAP) and 993 (IMAPS) open on the firewall.
Ports 25, 587 (SMTP), 465 (SMTPS), 143 (IMAP) and 993 (IMAPS) open on the firewall (I use ufw).

Postfix¶

Postfix is a “mail transfer agent” which is the component of the mail server that receives and sends emails via SMTP.

Install the postfix package:

pacman -S postfix
@@ -121,7 +148,7 @@ smtpd_sasl_path = private/auth
 smtpd_sasl_security_options = noanonymous, noplaintext
 smtpd_sasl_tls_security_options = noanonymous

Specify the mailbox home (this is going to be a directory inside your user’s home containing the actual mail files):

Specify the mailbox home, this is going to be a directory inside your user’s home containing the actual mail files, for example it will end up being/home/david/Mail/Inbox:

home_mailbox = Mail/Inbox/

Pre-configuration to work seamlessly with dovecot and opendkim:

@@ -135,8 +162,7 @@ smtpd_milters = inet:127.0.0.1:8891 non_smtpd_milters = inet:127.0.0.1:8891 mailbox_command = /usr/lib/dovecot/deliver -

Where {yourdomainname} is luevano.xyz in my case, or if you have localhost configured to your domain, then use localhost for myhostname (myhostname = localhost).

Lastly, if you don’t want the sender’s IP and user agent (application used to send the mail), add the following line:

Where {yourdomainname} is luevano.xyz in my case. Lastly, if you don’t want the sender’s IP and user agent (application used to send the mail), add the following line:

smtp_header_checks = regexp:/etc/postfix/smtp_header_checks

And create the /etc/postfix/smtp_header_checks file with the following content:

@@ -173,7 +199,7 @@ newaliases

systemctl start postfix.service
 systemctl enable postfix.service

Dovecot¶

Dovecot is an IMAP and POP3 server, which is what lets an email application retrieve the mail.

Install the dovecot and pigeonhole (sieve for dovecot) packages:

pacman -S dovecot pigeonhole
@@ -288,8 +314,8 @@ account required pam_unix.so
 systemctl start dovecot.service
 systemctl enable dovecot.service
 
-OpenDKIM¶
-OpenDKIM is needed so services like G**gle (we don’t mention that name here [[[this is a meme]]]) don’t throw the mail to the trash. DKIM stands for “DomainKeys Identified Mail”.
+OpenDKIM¶
+OpenDKIM is needed so services like G**gle don’t throw the mail to the trash. DKIM stands for “DomainKeys Identified Mail”.
 Install the opendkim package:
 pacman -S opendkim
 
@@ -338,7 +364,8 @@ chmod g+r /etc/postfix/dkim/*
 systemctl start opendkim.service
 systemctl enable opendkim.service
 
-And don’t forget to add the following TXT records on your domain registrar (these examples are for Epik):
+OpenDKIM DNS TXT records¶
+Add the following TXT records on your domain registrar (these examples are for Epik):
 
 DKIM entry: look up your {yoursubdomain}.txt file, it should look something like:
 
@@ -346,7 +373,7 @@ systemctl enable opendkim.service
     "p=..."
     "..." )  ; ----- DKIM key mail for {yourdomain}

In the TXT record you will place {yoursubdomain}._domainkey as the “Host” and "v=DKIM1; k=rsa; s=email; " "p=..." "..." in the “TXT Value” (replace the dots with the actual value you see in your file).

In the TXT record you will place {yoursubdomain}._domainkey as the “Host” and "v=DKIM1; k=rsa; s=email; " "p=..." "..." in the “TXT Value” (replace the dots with the actual value you see in your file).

DMARC entry: just _dmarc.{yourdomain} as the “Host” and "v=DMARC1; p=reject; rua=mailto:dmarc@{yourdomain}; fo=1" as the “TXT Value”.
@@ -356,7 +383,7 @@ systemctl enable opendkim.service

And at this point you could test your mail for spoofing and more.

SpamAssassin¶

SpamAssassin is just a mail filter to identify spam.

Install the spamassassin package (which will install a bunch of ugly perl packages…):

pacman -S spamassassin
@@ -409,10 +436,10 @@ ExecStart=/usr/bin/vendor_perl/spamd -x -u spamd -g spamd --listen=/run/spamd/sp
 systemctl start spamassassin.service
 systemctl enable spamassassin.service
 
-Wrapping up¶
-We should have a working mail server by now. Before continuing check your journal logs (journalctl -xe --unit={unit}, where {unit} could be spamassassin.service for example) to see if there was any error whatsoever and try to debug it, it should be a typo somewhere (the logs are generally really descriptive) because all the settings and steps detailed here just (literally just finished doing everything on a new server as of the writing of this text) worked (((it just werks on my machine))).
+Wrapping up¶
+We should have a working mail server by now. Before continuing check your journal logs (journalctl -xe --unit={unit}, where {unit} could be spamassassin.service for example) to see if there was any error whatsoever and try to debug it, it should be a typo somewhere because all the settings and steps detailed here just worked; I literally just finished doing everything on a new server as of the writing of this text, it just werks on my machine.
 Now, to actually use the mail service: first of all, you need a normal account (don’t use root) that belongs to the mail group (gpasswd -a user group to add a user user to group group) and that has a password.
-Next, to actually login into a mail app/program/whateveryouwanttocallit, you will use the following settings, at least for thunderdbird(I tested in windows default mail app and you don’t need a lot of settings):
+Next, to actually login into a mail app/program, you will use the following settings, at least for thunderdbird(I tested in windows default mail app and you don’t need a lot of settings):
 
 * server: subdomain.domain (mail.luevano.xyz in my case)
 SMTP port: 587
@@ -426,10 +453,9 @@ systemctl enable spamassassin.service
 
 All that’s left to do is test your mail server for spoofing, and to see if everything is setup correctly. Go to DKIM Test and follow the instructions (basically click next, and send an email with whatever content to the email that they provide). After you send the email, you should see something like:
 
-
+
 DKIM Test successful
 
-Finally, that’s actually it for this entry, if you have any problem whatsoever you can contact me.
 
   
     
@@ -459,10 +485,10 @@ systemctl enable spamassassin.service
   
     By David Luévano
     Created: Sun, Mar 21, 2021 @ 04:05 UTC
-      Modified: Tue, Jun 08, 2021 @ 07:29 UTC
+      Modified: Fri, May 05, 2023 @ 08:35 UTC
     
   Tags:
-english, server, tools, tutorial  
+code, english, server, tools, tutorial  
 
 
   
diff --git a/live/blog/a/new_blogging_system.html b/live/blog/a/new_blogging_system.html
index 066f288..9a06766 100644
--- a/live/blog/a/new_blogging_system.html
+++ b/live/blog/a/new_blogging_system.html
@@ -16,13 +16,12 @@
     
     
     
+    
+    
     
-
-
-
-
+
+
+
 
     
   
@@ -73,14 +72,20 @@
     
 
     
+      
+        
+      
   I'm using a new blogging system
 
   So, I was tired of working with ssg (and then sbg which was a modified version of ssg that I “wrote”), for one general reason: not being able to extend it as I would like; and not just dumb little stuff, I wanted to be able to have more control, to add tags (which another tool that I found does: blogit), and even more in a future.
 The solution? Write a new program “from scratch” in pYtHoN. Yes it is bloated, yes it is in its early stages, but it works just as I want it to work, and I’m pretty happy so far with the results and have with even more ideas in mind to “optimize” and generally clean my wOrKfLoW to post new blog entries. I even thought of using it for posting into a “feed” like gallery for drawings or pictures in general.
 I called it pyssg, because it sounds nice and it wasn’t taken in the PyPi. It is just a terminal program that reads either a configuration file or the options passed as flags when calling the program.
 It still uses Markdown files because I find them very easy to work with. And instead of just having a “header” and a “footer” applied to each parsed entry, you will have templates (generated with the program) for each piece that I thought made sense (idea taken from blogit): the common header and footer, the common header and footer for each entry and, header, footer and list elements for articles and tags. When parsing the Markdown file these templates are applied and stitched together to make a single HTML file. Also generates an RSS feed and the sitemap.xml file, which is nice.
-It might sound convoluted, but it works pretty well, with of course room to improve; I’m open to suggestions, issue reporting or direct contributions here. BTW, it only works on Linux for now (and don’t think on making it work on windows, but feel free to do PR for the compatibility).
+It might sound convoluted, but it works pretty well, with of course room to improve; I’m open to suggestions, issue reporting or direct contributions here. For now, it is only tested on Linux (and don’t think on making it work on windows, but feel free to do PR for the compatibility).
 That’s it for now, the new RSS feed is available here: https://blog.luevano.xyz/rss.xml.
+Update: Since writing this entry, pyssg has evolved quite a bit, so not everything described here is still true. For the latest updates check the newest entries or the git repository itself.
 
   
     
@@ -110,7 +115,7 @@
   
     By David Luévano
     Created: Fri, May 28, 2021 @ 03:21 UTC
-      Modified: Fri, May 28, 2021 @ 03:42 UTC
+      Modified: Thu, May 04, 2023 @ 18:18 UTC
     
   Tags:
 english, short, tools, update  
diff --git a/live/blog/a/password_manager_authenticator_setup.html b/live/blog/a/password_manager_authenticator_setup.html
index afd0e45..fbc57d1 100644
--- a/live/blog/a/password_manager_authenticator_setup.html
+++ b/live/blog/a/password_manager_authenticator_setup.html
@@ -16,13 +16,11 @@
     
     
     
+    
+    
     
-
-
-
-
+
+
 
     
   
@@ -73,10 +71,15 @@
     
 
     
+      
+        
+      
   My setup for a password manager and MFA authenticator
 
   Disclaimer: I won’t go into many technical details here of how to install/configure/use the software, this is just supposed to be a short description on my setup.
-It’s been a while since I started using a password manager at all, and I’m happy that I started with KeePassXC (open source, multiplatform password manager that it’s completely offline) as a direct recommendation from lm; before this I was using the same password for everything (like a lot of people), which is a well know privacy issue as noted in detail by Leo (I don’t personally recommed LastPass as Leo does). Note that you will still need a master password to lock/unlock your password database (you can additionally use a hardware key and a key file).
+It’s been a while since I started using a password manager at all, and I’m happy that I started with KeePassXC (open source, multiplatform password manager that it’s completely offline) as a direct recommendation from EL ELE EME; before this I was using the same password for everything (like a lot of people), which is a well know privacy issue as noted in detail by Leo (I don’t personally recommed LastPass as Leo does). Note that you will still need a master password to lock/unlock your password database (you can additionally use a hardware key and a key file).
 Anyways, setting up keepass is pretty simple, as there is a client for almost any device; note that keepass is basically just the format and the base for all of the clients, as its common with pretty much any open source software. In my case I’m using KeePassXC in my computer and KeePassDX in my phone (Android). The only concern is keeping everything in sync because keepass doesn’t have any automatic method of synchronizing between devices because of security reasons (as far as I know), meaning that you have to manage that yourself.
 Usually you can use something like G**gl* drive, dropbox, mega, nextcloud, or any other cloud solution that you like to sync your keepass database between devices; I personally prefer to use Syncthing as it’s open source, it’s really easy to setup and has worked wonders for me since I started using it, also it keeps versions of your files that can serve as backups in any scenario where the database gets corrupted or something.
 Finally, when I went through the issue with the micro SD and the adoptable storage bullshit (you can find the rant here, in spanish) I had to also migrate from G**gl* authenticator (gauth) to something else for the simple reason that gauth doesn’t even let you do backups, nor it’s synched with your account… nothing, it is just standalone and if you ever lose your phone you’re fucked; so I decided to go with Aegis authenticator, as it is open source, you have control over all your secret keys, you can do backups directly to the filesystem, you can secure your database with an extra password, etc., etc.. In general aegis is the superior MFA authenticator (at least compared with gauth) and everything that’s compatible with gauth is compatible with aegis as the format is a standard (as a matter of fact, keepass also has this MFA feature which is called TOPT and is also compatible, but I prefer to have things separate). I also use syncthing to keep a backup of my aegis database.
@@ -116,7 +119,7 @@
   
     By David Luévano
     Created: Sun, May 15, 2022 @ 22:40 UTC
-      Modified: Sun, May 22, 2022 @ 00:24 UTC
+      Modified: Thu, May 04, 2023 @ 03:49 UTC
     
   Tags:
 english, short, tools  
diff --git a/live/blog/a/rewrote_pyssg_again.html b/live/blog/a/rewrote_pyssg_again.html
index 481cb45..a1443d9 100644
--- a/live/blog/a/rewrote_pyssg_again.html
+++ b/live/blog/a/rewrote_pyssg_again.html
@@ -16,13 +16,12 @@
     
     
     
+    
+    
     
-
-
-
-
+
+
+
 
     
   
@@ -73,9 +72,14 @@
     
 
     
+      
+        
+      
   Rewrote pyssg again
 
-  I’ve been wanting to change the way pyssg reads config files and generates HTML files so that it is more flexible and I don’t need to have 2 separate build commands and configs (for blog and art), and also to handle other types of “sites”; because pyssg was built with blogging in mind, so it was a bit limited to how it could be used. So I had to kind of rewrite pyssg, and with the latest version I can now generate the whole site and use the same templates for everything, quite neat for my use case.
+  I’ve been wanting to change the way pyssg reads config files and generates HTML files so that it is more flexible and I don’t need to have 2 separate build commands and configs (for blog and art), and also to handle other types of “sites”; because pyssg was built with blogging in mind, so it was a bit limited to how it could be used. So I had to kind of rewrite pyssg, and with the latest version I can now generate the whole site and use the same templates for everything, quite neat for my use case.
 Anyways, so I bought a new domain for all pyssg related stuff, mostly because I wanted somewhere to test live builds while developing, it is of course pyssg.xyz; as of now it is the same template, CSS and scripts that I use here, probably will change in the future. I’ll be testing new features and anything pyssg related stuff.
 I should start pointing all links to pyssg to the actual site instead of the github repository (or my git repository), but I haven’t decided how to handle everything.
 
@@ -101,6 +105,7 @@
   
     By David Luévano
     Created: Tue, Dec 20, 2022 @ 04:31 UTC
+      Modified: Thu, May 04, 2023 @ 03:57 UTC
     
   Tags:
 english, short, tools, update  
diff --git a/live/blog/a/tenia_esto_descuidado.html b/live/blog/a/tenia_esto_descuidado.html
index 76fa1ed..b30a3b7 100644
--- a/live/blog/a/tenia_esto_descuidado.html
+++ b/live/blog/a/tenia_esto_descuidado.html
@@ -6,7 +6,7 @@
     
     
     
-Tenia este pex algo descuidado -- Luevano's Blog
+Tenía este pex algo descuidado -- Luevano's Blog
   
 
     
@@ -16,16 +16,14 @@
     
     
     
+    
+    
     
-
-
-
-
+
+
 
     
-  
+  
   
   
   
@@ -73,13 +71,18 @@
     
 
     
-  Tenia este pex algo descuidado
+      
+        
+      
+  Tenía este pex algo descuidado
 
   Así es, tenía un poco descuidado este pex, siendo la razón principal que andaba ocupado con cosas de la vida profesional, ayay. Pero ya que ando un poco más despejado y menos estresado voy a seguir usando el blog y a ver qué más hago.
-Tengo unas entradas pendientes que quiero hacer del estilo de “tutorial” o “how-to”, pero me lo he estado debatiendo, porque Luke ya empezó a hacerlo más de verdad en landchad.net, lo cual recomiendo bastante pues igual yo empecé a hacer esto por él (y por lm); aunque la verdad pues es muy específico a como él hace las cosas y quizá sí puede haber diferencias, pero ya veré en estos días. La próxima que quiero hacer es sobre el VPN, porque no lo he setupeado desde que reinicié El Página Web y La Servidor, entonces acomodaré el VPN de nuevo y de pasada tiro entrada de eso.
-También dejé un dibujo pendiente, que la neta lo dejé por 2 cosas: está bien cabrón (porque también lo quiero colorear) y porque estaba ocupado; de lo cuál ya sólo queda el está bien cabrón pero no he tenido el valor de retomarlo. Lo triste es que ya pasó el tiempo del hype y ya no tengo mucha motivación para terminarlo más que el hecho de que cuando lo termine empezaré a usar Clip Studio Paint en vez de Krita, porque compré una licencia ahora que estuvo en 50% de descuento (sí, me mamé).
+Tengo unas entradas pendientes que quiero hacer del estilo de “tutorial” o “how-to”, pero me lo he estado debatiendo, porque Luke ya empezó a hacerlo más de verdad en landchad.net, lo cual recomiendo bastante pues igual yo empecé a hacer esto por él (y por EL ELE EME); aunque la verdad pues es muy específico a como él hace las cosas y quizá sí puede haber diferencias, pero ya veré en estos días. La próxima que quiero hacer es sobre el VPN, porque no lo he setupeado desde que reinicié El Página Web y La Servidor, entonces acomodaré el VPN de nuevo y de pasada tiro entrada de eso.
+También dejé un dibujo pendiente, que la neta lo dejé por 2 cosas: está bien cabrón (porque también lo quiero colorear) y porque estaba ocupado; de lo cuál ya sólo queda el está bien cabrón pero no he tenido el valor de retomarlo. Lo triste es que ya pasó el tiempo del hype y ya no tengo mucha motivación para terminarlo más que el hecho de que cuando lo termine empezaré a usar Clip Studio Paint en vez de Krita, porque compré una licencia ahora que estuvo en 50% de descuento.
 Algo bueno es que me he estado sintiendo muy bien conmigo mismo últimamente, aunque casi no hable de eso. Sí hay una razón en específico, pero es una razón algo tonta. Espero así siga.
-Ah, y también quería acomodarme una sección de comentarios, pero como siempre, todas las opciones están bien bloated, entonces pues me voy a hacer una en corto seguramente en Python para el back, MySQL para la base de datos y Javascript para la conexión acá en el front, algo tranqui.
+Ah, y también quería acomodarme una sección de comentarios, pero como siempre, todas las opciones están bien bloated, entonces pues me voy a hacer una en corto seguramente en Python para el back, MySQL para la base de datos y Javascript para la conexión acá en el front, algo tranqui. Nel, siempre no ocupo esto, pa’ qué.
 Sobres pues.
 
   
@@ -110,6 +113,7 @@
   
     By David Luévano
     Created: Sun, Jul 18, 2021 @ 07:51 UTC
+      Modified: Thu, May 04, 2023 @ 18:20 UTC
     
   Tags:
 short, spanish, update  
diff --git a/live/blog/a/volviendo_a_usar_la_pagina.html b/live/blog/a/volviendo_a_usar_la_pagina.html
index 8380991..59a898d 100644
--- a/live/blog/a/volviendo_a_usar_la_pagina.html
+++ b/live/blog/a/volviendo_a_usar_la_pagina.html
@@ -16,13 +16,11 @@
     
     
     
+    
+    
     
-
-
-
-
+
+
 
     
   
@@ -73,12 +71,17 @@
     
 
     
+      
+        
+      
   Volviendo a usar la página
 
   Después de mucho tiempo de estar luchando con querer volver a usar este pex (maldita d word y demás), ya me volví a acomodar el setup para agregar nuevas entradas.
-Entre las cosas que tuve que hacer fue actualizar el pyssg porque no lo podía usar de una como estaba; y de pasado le agregue una que otra feature nueva. Luego quiero agregarle más funcionalidad para poder buildear la página completa; por ahora se hace en segmentos: todo lo de luevano.xyz está hecho manual, mientras que blog y art usan pyssg.
+Entre las cosas que tuve que hacer fue actualizar el pyssg porque no lo podía usar de una como estaba; y de pasado le agregue una que otra feature nueva. Luego quiero agregarle más funcionalidad para poder buildear la página completa; por ahora se hace en segmentos: todo lo de luevano.xyz está hecho manual, mientras que blog y art usan pyssg.
 Otra cosa es que quizá me devuelva a editar alguans entradas nada más para homogeneizar las entradas específicas a Create a… (tiene más sentido que sean Setup x… o algo similar).
-En otras noticias, estoy muy agusto en el jale que tengo actualmente aunque lleve alrededor de 3 semanas de un infierno por problemas debidos a varias razones (del jale). Debo pensar en si debo omitir cosas personales o del trabajo aquí, ya que quién sabe quién se pueda llegar a topar con esto *thinking emoji*.
+En otras noticias, estoy muy agusto en el jale que tengo actualmente aunque lleve alrededor de 3 semanas de un infierno en el jale. Debo pensar en si debo omitir cosas personales o del trabajo aquí, ya que quién sabe quién se pueda llegar a topar con esto *thinking emoji*.
 
   
     
@@ -108,7 +111,7 @@
   
     By David Luévano
     Created: Thu, Apr 28, 2022 @ 03:21 UTC
-      Modified: Thu, Apr 28, 2022 @ 03:28 UTC
+      Modified: Thu, May 04, 2023 @ 18:23 UTC
     
   Tags:
 short, spanish, update  
diff --git a/live/blog/a/vpn_server_with_openvpn.html b/live/blog/a/vpn_server_with_openvpn.html
index de80c45..6109f37 100644
--- a/live/blog/a/vpn_server_with_openvpn.html
+++ b/live/blog/a/vpn_server_with_openvpn.html
@@ -16,14 +16,21 @@
     
     
     
+    
+    
     
-
+    
 
 
 
 
+
+
+
+
+
     
   
   
@@ -73,18 +80,36 @@
     
 
     
+      
+        
+      
   Create a VPN server with OpenVPN (IPv4)
 
   I’ve been wanting to do this entry, but had no time to do it since I also have to set up the VPN service as well to make sure what I’m writing makes sense, today is the day.
 Like with any other of my entries I based my setup on the Arch Wiki, this install script and this profile generator script.
-This will be installed and working alongside the other stuff I’ve wrote about on other posts (see the server tag). All commands here are executes as root unless specified otherwise. Also, this is intended only for IPv4 (it’s not that hard to include IPv6, but meh).
-Prerequisites¶
+This will be installed and working alongside the other stuff I’ve wrote about on other posts (see the server tag). All commands here are executes as root unless specified otherwise. Also, this is intended only for IPv4 (it’s not that hard to include IPv6, but meh). As always, all commands are executed as root unless stated otherwise.
+Table of contents¶
+
+
+Table of contents
+Prerequisites
+Create PKI from scratch
+OpenVPN
+Enable forwarding
+Create client configurations
+
+
+
+
+Prerequisites¶
 Pretty simple:
 
-Working server with root access, and with Ufw as the firewall.
-Depending on what port you want to run the VPN on, the default 1194, or as a fallback on 443 (click here for more). I will do mine on port 1194 but it’s just a matter of changing 2 lines of configuration and one Ufw rule.
+Working server with root access, and with ufw as the firewall.
+Depending on what port you want to run the VPN on, the default 1194, or as a fallback on 443 (click here for more). I will do mine on port 1194 but it’s just a matter of changing 2 lines of configuration and one ufw rule.
 
-Create PKI from scratch¶
+Create PKI from scratch¶
 PKI stands for Public Key Infrastructure and basically it’s required for certificates, private keys and more. This is supposed to work between two servers and one client: a server in charge of creating, signing and verifying the certificates, a server with the OpenVPN service running and the client making the request.
 This is supposed to work something like: 1) a client wants to use the VPN service, so it creates a requests and sends it to the signing server, 2) this server checks the requests and signs the request, returning the certificates to both the VPN service and the client and 3) the client can now connect to the VPN service using the signed certificate which the OpenVPN server knows about. In a nutshell, I’m no expert.
 … but, to be honest, all of this is a hassle and (in my case) I want something simple to use and manage. So I’m gonna do all on one server and then just give away the configuration file for the clients, effectively generating files that anyone can run and will work, meaning that you need to be careful who you give this files (it also comes with a revoking mechanism, so no worries).
@@ -128,8 +153,8 @@ openssl dhparam -out dh.pem 2048
 openvpn --genkey secret ta.key


 That’s it for the PKI stuff and general certificate configuration.
-OpenVPN¶
-OpenVPN is a robust and highly flexible VPN daemon, that’s pretty complete feature wise.
+OpenVPN¶
+OpenVPN is a robust and highly flexible VPN daemon, that’s pretty complete feature-wise.
 Install the openvpn package:
 pacman -S openvpn
 
@@ -231,6 +256,7 @@ verb 3
 explicit-exit-notify 1

# and ; are comments. Read each and every line, you might want to change some stuff (like the logging), specially the first line which is your server public IP.

Enable forwarding¶

Now, we need to enable packet forwarding (so we can access the web while connected to the VPN), which can be enabled on the interface level or globally (you can check the different options with sysctl -a | grep forward). I’ll do it globally, run:

sysctl net.ipv4.ip_forward=1

@@ -276,7 +302,7 @@ ufw reload systemctl enable openvpn-server@server.service

Where the server after @ is the name of your configuration, server.conf without the .conf in my case.

Create client configurations¶

You might notice that I didn’t specify how to actually connect to our server. For that we need to do a few more steps. We actually need a configuration file similar to the server.conf file that we created.

The real way of doing this would be to run similar steps as the ones with easy-rsa locally, send them to the server, sign them, and retrieve them. Nah, we’ll just create all configuration files on the server as I was mentioning earlier.

Also, the client configuration file has to match the server one (to some degree), to make this easier you can create a client-common file in /etc/openvpn/server with the following content:

@@ -349,7 +375,7 @@ chown nobody:nobody pki/crl.pem chmod o+r pki/crl.pem cd $CPWD -

And the way to use is to run vpn_script new/rev client_name as sudo (when revoking, it doesn’t actually deletes the .ovpn file in ~/ovpn). Again, this is a little script that I put together, so you should check it out, it may need tweaks (depending on your directory structure for easy-rsa) and it could have errors.

And the way to use is to run vpn_script new/rev client_name as sudo (when revoking, it doesn’t actually delete the .ovpn file in ~/ovpn). Again, this is a little script that I put together, so you should check it out, it may need tweaks (depending on your directory structure for easy-rsa).

Now, just get the .ovpn file generated, import it to OpenVPN in your client of preference and you should have a working VPN service.

@@ -380,10 +406,10 @@ cd $CPWD

By David Luévano

Created: Sun, Aug 01, 2021 @ 09:27 UTC

Modified: Sun, Aug 01, 2021 @ 10:13 UTC

Modified: Fri, May 05, 2023 @ 08:36 UTC

Tags: -english, server, tools, tutorial

+code, english, server, tools, tutorial

diff --git a/live/blog/a/website_with_nginx.html b/live/blog/a/website_with_nginx.html index 386b95d..6070c82 100644 --- a/live/blog/a/website_with_nginx.html +++ b/live/blog/a/website_with_nginx.html @@ -16,14 +16,21 @@ + + - + + + + + + @@ -73,25 +80,39 @@

+ +

Create a website with Nginx and Certbot

These are general notes on how to setup a Nginx web server plus Certbot for SSL certificates, initially learned from Luke’s video and after some use and research I added more stuff to the mix. And, actually at the time of writing this entry, I’m configuring the web server again on a new VPS instance, so this is going to be fresh.

As a side note, (((i use arch btw))) so everything here es aimed at an Arch Linux distro, and I’m doing everything on a VPS. Also note that most if not all commands here are executed with root privileges.

Prerequisites¶

As a side note, i use arch btw so everything here es aimed at an Arch Linux distro, and I’m doing everything on a VPS. Also note that most if not all commands here are executed with root privileges.

Table of contents¶

Table of contents
Prerequisites
Nginx
Certbot

Prerequisites¶

You will need two things:

A domain name (duh!). I got mine on Epik (affiliate link, btw).
- With the corresponding A and AAA records pointing to the VPS’ IPs (“A” record points to the ipv4 address and “AAA” to the ipv6, basically). I have three records for each type: empty one, “www” and “*” for a wildcard, that way “domain.name”, “www.domain.name”, “anythingelse.domain.name” point to the same VPS (meaning that you can have several VPS for different sub-domains).
- With the corresponding A and AAA records pointing to the VPS’ IPs. I have three records for each type: empty string, “www” and “*” for a wildcard, that way “domain.name”, “www.domain.name”, “anythingelse.domain.name” point to the same VPS (meaning that you can have several VPS for different sub-domains). These depend on the VPS provider.

A VPS or somewhere else to host it. I’m using Vultr (also an affiliate link).

A VPS or somewhere else to host it. I’m using Vultr (also an affiliate link, btw).
- With ssh already configured both on the local machine and on the remote machine.
- Firewall already configured to allow ports 80 (HTTP) and 443 (HTTPS). I use ufw so it’s just a matter of doing ufw allow 80,443/tcp as root and you’re golden.
- cron installed if you follow along (you could use systemd timers, or some other method you prefer to automate running commands every X time).
- Firewall already configured to allow ports 80 (HTTP) and 443 (HTTPS). I use ufw so it’s just a matter of doing ufw allow 80,443/tcp (for example) as root and you’re golden.
- cron installed if you follow along (you could use systemd timers, or some other method you prefer to automate running commands every certain time).

Nginx¶

Nginx is a web (HTTP) server and reverse proxy server.

You have two options: nginx and nginx-mainline. I prefer nginx-mainline because it’s the “up to date” package even though nginx is labeled to be the “stable” version. Install the package and enable/start the service:

pacman -S nginx-mainline
@@ -100,7 +121,7 @@ systemctl start nginx.service

And that’s it, at this point you can already look at the default initial page of Nginx if you enter the IP of your server in a web browser. You should see something like this:

As stated in the welcome page, configuration is needed, head to the directory of Nginx:

@@ -167,7 +188,7 @@ systemctl restart nginx

If everything goes correctly, you can now go to your website by typing domain.name on a web browser. But you will see a “404 Not Found” page like the following (maybe with different Nginx version):

That’s no problem, because it means that the web server it’s actually working. Just add an index.html file with something simple to see it in action (in the /var/www/some_folder that you decided upon). If you keep seeing the 404 page make sure your root line is correct and that the directory/index file exists.

@@ -180,7 +201,7 @@ systemctl restart nginx try_files $uri/index.html $uri.html $uri/ $uri =404; ... -

Certbot¶

Certbot is what provides the SSL certificates via Let’s Encrypt.

The only “bad” (bloated) thing about Certbot, is that it uses python, but for me it doesn’t matter too much. You may want to look up another alternative if you prefer. Install the packages certbot and certbot-nginx:

pacman -S certbot certbot-nginx
@@ -192,7 +213,7 @@ systemctl restart nginx
 Now, the certificate given by certbot expires every 3 months or something like that, so you want to renew this certificate every once in a while. Using cron, you can do this by running:
 crontab -e
 
-And a file will be opened where you need to add a new rule for Certbot, just append the line: 1 1 1 * * certbot renew (renew on the first day of every month) and you’re good. Alternatively use systemd timers as stated in the Arch Linux Wiki.
+And a file will be opened where you need to add a new rule for Certbot, just append the line: 1 1 1 * * certbot renew --quiet --agree-tos --deploy-hook "systemctl reload nginx.service" (renew on the first day of every month) and you’re good. Alternatively use systemd timers as stated in the Arch Linux Wiki.
 That’s it, you now have a website with SSL certificate.
 
   
@@ -223,10 +244,10 @@ systemctl restart nginx
   
     By David Luévano
     Created: Fri, Mar 19, 2021 @ 02:58 UTC
-      Modified: Tue, Jun 08, 2021 @ 07:27 UTC
+      Modified: Fri, May 05, 2023 @ 08:34 UTC
     
   Tags:
-english, server, tools, tutorial  
+code, english, server, tools, tutorial  
 
 
   
diff --git a/live/blog/a/xmpp_server_with_prosody.html b/live/blog/a/xmpp_server_with_prosody.html
index 20418ca..9a83ac4 100644
--- a/live/blog/a/xmpp_server_with_prosody.html
+++ b/live/blog/a/xmpp_server_with_prosody.html
@@ -16,14 +16,21 @@
     
     
     
+    
+    
     
-
+    
 
 
 
 
+
+
+
+
+
     
   
   
@@ -73,12 +80,29 @@
     
 
     
+      
+        
+      
   Create an XMPP server with Prosody compatible with Conversations and Movim
 
-  Recently I set up an XMPP server (and a Matrix one, too) for my personal use and for friends if they want one; made one for EL ELE EME for example. So, here are the notes on how I set up the server that is compatible with the Conversations app and the Movim social network. You can see my addresses in contact and the XMPP compliance/score of the server.
-One of the best resources I found that helped me a lot was Installing and Configuring Prosody XMPP Server on Debian 9, and of course the Arch Wiki and the oficial documentation.
-As with my other entries, this is under a server running Arch Linux, with the Nginx web server and Certbot certificates. And all commands here are executed as root (unless specified otherwise)
-Prerequisites¶
+  Update: I no longer host this XMPP server as it consumed a lot of resources and I wasn’t using it that much. I’ll probably re-create it in the future, though.
+Recently I set up an XMPP server (and a Matrix one, too) for my personal use and for friends if they want one; made one for EL ELE EME for example. So, here are the notes on how I set up the server that is compatible with the Conversations app and the Movim social network. You can see my addresses at contact and the XMPP compliance/score of the server.
+One of the best resources I found that helped me a lot was Installing and Configuring Prosody XMPP Server on Debian 9, the Arch Wiki and the oficial documentation.
+As with my other entries, this is under a server running Arch Linux, with the Nginx web server and Certbot certificates. And all commands here are executed as root, unless specified otherwise.
+Table of contents¶
+
+
+Table of contents
+Prerequisites
+Prosody
+Nginx configuration file
+Coturn
+Wrapping up
+
+
+Prerequisites¶
 Same as with my other entries (website, mail and git) plus:
 
 A and (optionally) AAA DNS records for:
@@ -90,16 +114,16 @@
 
 
 (Optionally, but recommended) the following SRV DNS records; make sure it is pointing to an A or AAA record (matching the records from the last point, for example):
-_xmpp-client._tcp.**your.domain**. for port 5222 pointing to xmpp.**your.domain**.
-_xmpp-server._tcp.**your.domain**. for port 5269 pointing to xmpp.**your.domain**.
-_xmpp-server._tcp.muc.**your.domain**. for port 5269 pointing to xmpp.**your.domain**.
+_xmpp-client._tcp.{your.domain}. for port 5222 pointing to xmpp.{your.domain}.
+_xmpp-server._tcp.{your.domain}. for port 5269 pointing to xmpp.{your.domain}.
+_xmpp-server._tcp.muc.{your.domain}. for port 5269 pointing to xmpp.{your.domain}.
 
 
 SSL certificates for the previous subdomains; similar that with my other entries just create the appropriate prosody.conf (where server_name will be all the subdomains defined above) file and run certbot --nginx. You can find the example configuration file almost at the end of this entry.
 Email addresses for admin, abuse, contact, security, etc. Or use your own email for all of them, doesn’t really matter much as long as you define them in the configuration and are valid, I have aliases so those emails are forwarded to me.
 Allow ports 5000, 5222, 5269, 5280 and 5281 for Prosody and, 3478 and 5349 for Turnserver which are the defaults for coturn.
 
-Prosody¶
+Prosody¶
 Prosody is an implementation of the XMPP protocol that is flexible and extensible.
 Install the prosody package (with optional dependencies) and the mercurial package:
 pacman -S prosody, mercurial, lua52-sec, lua52-dbi, lua52-zlib
@@ -111,11 +135,11 @@ mkdir modules-enabled
 
 You can see that I follow a similar approach that I used with Nginx and the server configuration, where I have all the modules available in a directory, and make a symlink to another to keep track of what is being used. You can update the repository by running hg pull --update while inside the modules-available directory (similar to Git).
 Make symbolic links to the following modules:
-ln -s /var/lib/prosody/modules-available/MODULE_NAME /var/lib/prosody/modules-enabled/
+ln -s /var/lib/prosody/modules-available/{module_name} /var/lib/prosody/modules-enabled/
 ...
 
 
-Modules:
+Modules ({module_name}):
 mod_bookmarks
 mod_cache_c2s_caps
 mod_checkcerts
@@ -443,8 +467,8 @@ ln -s your.domain.key SUBDOMAIN.your.domain.key
 ...
 
 That’s basically all the configuration that needs Prosody itself, but we still have to configure Nginx and Coturn before starting/enabling the prosody service.
-Nginx configuration file¶
-Since this is not an ordinary configuration file I’m going to describe this too. Your prosody.conf file should have the following location blocks under the main server block (the one that listens to HTTPS):
+Nginx configuration file¶
+Since this is not an ordinary configuration file I’m going to describe this, too. Your prosody.conf file should have the following location blocks under the main server block (the one that listens to HTTPS):
 # HTTPS server block
 server {
     root /var/www/prosody/;
@@ -537,11 +561,11 @@ server {
     ]
 }
 
-Remember to have your prosody.conf file symlinked (or discoverable by Nginx) to the sites-enabled directory. You can now restart your nginx service (and test the configuration, optionally):
+Remember to have your prosody.conf file symlinked (or discoverable by Nginx) to the sites-enabled directory. You can now test and restart your nginx service (and test the configuration, optionally):
 nginx -t
 systemctl restart nginx.service
 
-Coturn¶
+Coturn¶
 Coturn is the implementation of TURN and STUN server, which in general is for (at least in the XMPP world) voice support and external service discovery.
 Install the coturn package:
 pacman -S coturn
@@ -557,7 +581,7 @@ static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
 systemctl enable turnserver.service
 
 You can test if your TURN server works at Trickle ICE. You may need to add a user in the turnserver.conf to test this.
-Wrapping up¶
+Wrapping up¶
 At this point you should have a working XMPP server, start/enable the prosody service now:
 systemctl start prosody.service
 systemctl enable prosody.service
@@ -570,7 +594,7 @@ systemctl enable prosody.service
 Additionally, you can test the security of your server in IM Observatory, here you only need to specify your domain.name (not xmpp.domain.name, if you set up the SRV DNS records correctly). Again, it should have a similar score to mine:
 
 You can now log in into your XMPP client of choice, if it asks for the server it should be xmpp.your.domain (or your.domain for some clients) and your login credentials you@your.domain and the password you chose (which you can change in most clients).
-That’s it, send me a message david@luevano.xyz if you were able to set up the server successfully.
+That’s it, send me a message at david@luevano.xyz if you were able to set up the server successfully.
 
   
     
@@ -600,10 +624,10 @@ systemctl enable prosody.service
   
     By David Luévano
     Created: Wed, Jun 09, 2021 @ 05:24 UTC
-      Modified: Tue, Dec 20, 2022 @ 04:33 UTC
+      Modified: Fri, May 05, 2023 @ 08:36 UTC
     
   Tags:
-english, server, tools, tutorial  
+code, english, server, tools, tutorial  
 
 
   
-- 
cgit v1.2.3-54-g00ecf