Tag: meta (2)

As I mentioned a few days ago, I have to decide between MeiliSearch and an SQL option. I will most likely go towards an SQL option because I need some sort of way to retrieve all the existing tags and I cannot do that with MeiliSearch unless I retrieve all posts and filter the tags.

I’m gonna be honest: I’m a bit scared of implementing this πŸ˜‚ I haven’t used SQL databases in some time and I feel like something will break at some point. However, I’m trying to avoid CGO at all costs. Maybe I’ll try the newer non-CGO SQLite options for Go, or maybe I’ll just go with Postgres.

In the series of “the new version of my CMS”: trying to decide how to save context (reply, like, repost context) and webmentions. One option, which is the one I’m using right now with Hugo, is to have a sidecar file that contains those informations. In the new non-static system, that will mean every time I need to render a post, I need to read two files at least.

The other option would be to have an “xray” folder organized in a fashion like domain.com/hashoftheurl.json and then still use the sidecar file (or even the post frontmatter) to link all the webmentions and context data. That’d require more I/O operations though.

I think I’m going with the sidecar for now. How are you storing your webmentions?

Why is Bunny Optimizer Engine 10$ per month? That’s a bit too much. I must say that I’m tempted of the capabilities to resize images on demand instead of having to upload the right sizes - and then if I wanna change them, I have to reupload all images with the new sizes again. But 10$ is too much for that! There’s other services with lower princings though.

In the process of building my new blogging system with IndieWeb whistles and bells, I was thinking today about the usage of shortcodes. Hugo provides this functionality called Shortcodes which lets you define some snippets with Go templating and then re-use them in your posts.

I’m using them to quite some extent, mainly with figures. If I do implement something similar, then the rendering process will be 3 pass: first pass the post content with Go templating, then Markdown, then Go templating again. Not sure if the two first steps should be swapped.

I don’t feel very happy about that 3-passing scheme as I think speed matters and I’m already afraid of adding too much! Any suggestions?

I have an exam next week, but I’ve also been working a bit on Eagle v2. I think I underestimated the amount of work I will have. I have many shortcodes in Hugo and I’m also relying on some custom Goldmark extensions that are being used by Hugo.

On the format, I’ve decided to do something very similar to p3k and organize the files by year, month and day. Don’t worry, I will set up all the redirects afterwards. And this time they’re actually redirects and not Hugo-generated-redirect-HTML-files.

I must say that using a statically typed language is not the most seamless for this, but it works! I see why - maybe - so many people on the IndieWeb community have used PHP.

I’m also blocked on how to index: so far I’ve been using MeiliSearch which works perfectly. It would still work perfectly. However, in the future I would like to have my own IndieAuth implementation and that would require to store tokens so it’d be a great time to move to an SQL database. Decisions… decisions… decisions…