jekyll-feed VS k3s

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.

Opinionated meaning it picks, install, patches your CNI/Ingress/Load Balancer/DNS Server/Metrics Server/Monitoring Setup.

k3s is probably most well known as it ships with bunch of preinstall software: https://github.com/k3s-io/k3s so you can just start throwing yaml files at cluster and handling workloads. It's what I use for my homelab.

Paid things I've heard of include OpenStack and SideroLabs. Haven't used personally by SRE coworkers say good things about them.

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable.

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319

For other distributions, nix-snapshotter works with official containerd releases so it’s just a matter of toml configuration and a systemd unit for nix-snapshotter.

We run Kubernetes outside of NixOS, but yes the NixOS modules provided by the nix-snapshotter certainly make it simple.

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Kubernetes - k3s distribution

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later.

You should be familiar with Kubernetes and have set up a Kubernetes cluster. I recommend k3s.