From 81d0d609e47d5cdfab3d5db2eff6ec91b5d2773b Mon Sep 17 00:00:00 2001 From: David Luevano Alvarado Date: Mon, 19 Dec 2022 22:48:27 -0600 Subject: add new entry, fix ??? to == syntax for 'mark' --- live/blog/a/rewrote_pyssg_again.html | 142 ++++++++++++++++++++++++++++++ live/blog/a/xmpp_server_with_prosody.html | 6 +- live/blog/g/gogodot_jam3_devlog_1.html | 6 ++ live/blog/index.html | 4 +- live/blog/rss.xml | 18 +++- live/blog/sitemap.xml | 8 +- live/blog/tag/@english.html | 4 +- live/blog/tag/@short.html | 4 +- live/blog/tag/@tools.html | 4 +- live/blog/tag/@update.html | 4 +- 10 files changed, 189 insertions(+), 11 deletions(-) create mode 100644 live/blog/a/rewrote_pyssg_again.html (limited to 'live/blog') diff --git a/live/blog/a/rewrote_pyssg_again.html b/live/blog/a/rewrote_pyssg_again.html new file mode 100644 index 0000000..faff8bb --- /dev/null +++ b/live/blog/a/rewrote_pyssg_again.html @@ -0,0 +1,142 @@ + + + + + + + +Rewrote pyssg again -- Luevano's Blog + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + +
+ +
+

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.

+

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.

+ + + + +
+ +
+ + + + \ No newline at end of file diff --git a/live/blog/a/xmpp_server_with_prosody.html b/live/blog/a/xmpp_server_with_prosody.html index 261531f..7f7b168 100644 --- a/live/blog/a/xmpp_server_with_prosody.html +++ b/live/blog/a/xmpp_server_with_prosody.html @@ -76,7 +76,7 @@

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.

+

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

@@ -411,7 +411,7 @@ Component "vjud.your.domain" "vjud" name = "User Directory" vjud_mode = "opt-in" -

You ???HAVE??? 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:

+

You HAVE 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:

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 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:

@@ -601,7 +601,7 @@ systemctl enable prosody.service