jekyll-feed VS coolify

XML feeds are often generated by templating, rather than actual XML serialisation. The official Jekyll Feed plugin has this: https://github.com/jekyll/jekyll-feed/blob/master/lib/jekyll...

JSON is much more easily generated by a valid generator, and less likely to face serialisation issues.

Awesome. I was able to get this going easily enough on my jekyll-created site that uses the jekyll-feeds plugin. You just have to name the template right and it just works.

https://github.com/jekyll/jekyll-feed/#custom-styling

Disable Jekyll-feed plugin from _config.yml

It looks like this [1] plugin [2] is supported in jekyll / GitHub pages [3].

So, it seems like adding RSS / Atom feeds on a jekyll or GitHub pages site is pretty straightforward.

1. https://github.com/jekyll/jekyll-feed

2. https://docs.github.com/en/pages/setting-up-a-github-pages-s...

3. https://pages.github.com/versions/

Nice site! Another fellow note-taker inspired by Gilles Castel I see ;) Would you be willing to add an RSS feed to your site so people can follow it and get updates? It's been a while since I used jekyll but I think you just need to add jekyll-feed to the Gemfile and config.yml. See here

There is again an easy way out with the jekyll-feed plugin. Add the plugin, do a bundle install and the feed should start appearing at /feed.xml.

I was afraid of that. I was starting to think that how my Atom feed is created is not properly formed XML. I'm using this to build the feed, https://github.com/jekyll/jekyll-feed/blob/master/lib/jekyll-feed/feed.xml. See line number 66 for the content I'm talking about ({{ post.content | strip | xml_escape }}). Maybe I just can't do what I'm trying to accomplish using only XSLT. I just wanted to have the option for the user of having the summary or the full on content with HTML markup and all. BTW, the file I referenced is written with Liquid Template Language.

I have tried using the provided theme like Minima but, I just don’t like it after all. That’s why I think it’s better to create my own. I tried to create the simplest design as long as it is easy to be read. I used Coolors, Google Font, Rogue, Jekyll Paginate, Jekyll Feed, and write a bit of Ruby, CSS, and JS for creating the theme itself. I didn’t think creating this simple blog costs me 2 Saturdays, even though it only consists of as many as 3 pages.

This is my first quick try deploying SvelteKit with the open source software Coolify by Andras Bacsai.

With a serverful approach, you can avoid these drawbacks, and the main challenge lies in selecting the platform that aligns with your requirements. Options may include AWS, Render, DigitalOcean, and others. While VPS is also an option, it's generally not recommended due to the significant setup and maintenance overhead involved (logging, monitoring, CI/CD pipelines, etc.). However, you can make your life easier by leveraging tools like Coolify that help managing your VPS.

Heroku and similar providers can simplify the server management issues, but you can use something much better that can combine both cost efficiency and ease of deployment—Coolify:

> VPSs being “easy to manage” is a strong option full of assumptions.

There are definitely many footguns with managing a VPS but I think the threshold to get vaguely competent with a VPS is not really that far off with getting familiar with the average cloud platform - which comes with its own dangers, like the near-total inability to put an upward cap on fees that that person found out with Netlify recently.

Having a $5 VPS and knowing it's never going to cost your more than $5 might balance out a lot of things on the other side for a lot of people.

(And, as a bonus, it comes with the benefit of having a better idea of what is going on on the actual computer which is running your code.)

Platforms like https://coolify.io/ (which I have not tried, but looks interesting) seem to give you some of the abstractions that you get in cloud platforms to save you having to mess with too much low level stuff and become an expert in a billion separate systems.

If you have Debian with automatic updates that does most of the heavy lifting for you. The hardest problem I have is resisting the temptation to just install everything, because the cost to do it is capped at my VPS monthly fee.

So yep, it comes with a lot of assumptions. But so does everything!

https://coolify.io/ might be worth a look

The modern iteration of these tools has taken the developer experience learnings from the Platform as a Service (PaaS) category, and will bring them to your own VM, giving you your own personal PaaS. Example of this include Dokku, Coolify, Caprover, Cloud66 and many more!