Jacmoe's Cyber Soapbox

Projects

Sun, 10 Sep 2023 23:38:00 +0200

Projects

About

Sun, 10 Sep 2023 01:34:00 +0200

On the other hand, we denounce with righteous indignation and dislike men who are so beguiled and demoralized by the charms of pleasure of the moment, so blinded by desire, that they cannot foresee the pain and trouble that are bound to ensue; and equal blame belongs to those who fail in their duty through weakness of will, which is the same as saying through shrinking from toil and pain.

First Entry in my new Gemini Log

Fri, 17 Mar 2023 00:00:00 +0000

The first entry of my Gemini Log (Gemlog) is up: 2023-03-17 - Hello, Universe!

I am thinking that my Gemini Capsule should be a place for me to share my writing, my writer’s journal, and my musings about writing.

Much simpler to put something up on Gemini: simply write a simple text, and put it on the server.

Here’s to many more entries in the Gemlog! 🚀

Local Gemini Server - Quick and Dirty

Tue, 14 Mar 2023 14:22:00 +0100

If you, like me, are excited about Project Gemini and want to create your own capsule (Gemini site), you will probably wonder how you would test your capsule on your local machine before putting it out there.

This small (and dirty!) guide aims to remove that doubt.

So, without further dillydally, here goes:

Install GmCapsule by running the following command, assuming that Python is installed:

pip install gmcapsule

Now, create a .gmcapsulerc file in your home directory, with the following content:

[static]
root = /<user_home>/gemini/capsule/

<user_home> should obviously be replaced with your home directory. root should point to where the Gemini files are to be served from.

Notice that the server name is appended to the path above, which means that the real path to the index.gmi file for the root of the site is located in /<user_home>/gemini/capsule/localhost.

Now we need to create a server certificate and the corresponding key.

Create a directory called .certs in your home directory, cd into it, and run the following command:

openssl req -new -x509 -days 365 -nodes -out cert.pem -keyout key.pem -subj "/CN=localhost" -newkey rsa:4096 -addext "subjectAltName = DNS:localhost"

The .certs directory should now contain two files, cert.pem and key.pem. The GmCapsule server loads the certificate upon startup.

Now, start the server by running:

gmcapsuled

Use a Gemini client, like amfora to browse your local Gemini capsule:

amfora gemini://localhost/

Now, enjoy creating content for Gemini!

I am excited about the whole idea of the small internet, and the syntax for the .gmi files are so simple, much simpler than even Markdown. I like not having to mess around with HTML, CSS, JavaScript, fonts … Just plain text.

I will probably be writing more about Gemini in the future 🙂

PS: you might have to open port 1965 if you are running a firewall.

Welcome to my new blog

Tue, 29 Mar 2022 00:00:00 +0000

My old blog at WordPress only has one single post in it.

I wrote it using Org-mode in Emacs, and used an extension to put it on WordPress.

That was good.

I had to perform a lot of tweaking to the HTML, however, and that has obviously put me off just writing blog posts.

That was bad.

So, I wanted something as easy as writing a blog post in my favorite writing environment, committing the changes to git source control, and pushing it to a remote repository to be hosted. I don't want to deal with a website like WordPress, to be honest.

Hugo and Emacs

After hunting around, I stumbled over a good workflow using Hugo and the excellent Emacs extension ox-hugo. All I have to do is write my blog posts in one org-file within Emacs, export to Hugo using the exporter, and let Hugo generate the output. Then I commit the changes to my git repository, push it to GitHub, and my homepage is updated.

I don't have to mess around with anything, like I did in WordPress.

Since it's now going to be much easier to get a blog post up, I am sure I will actually blog a post or two now 🙂

I have several ideas, and the good thing about it is, that I can have those posts in my org-file, as sub-trees, because the Emacs Hugo exporter will only export the trees that are DONE, not the ones marked with TODO.

It should be easy to blog, and I am most comfortable in Emacs. So, there's that 😀