HedgeDoc VS k3s

Nice and simple. I feel the only lacking feature for a basic blog is having unlisted blog posts, which is very handy when you want to share it to proof-readers. This can be done on google doc/hedgedoc [0] for sure, but then when porting there are very often typos creeping in.

[0] https://hedgedoc.org/

Maybe Hedgedoc will fit these needs? You can use markdown to format. https://hedgedoc.org/

If self-hosting is an option for you I would recommend that you go with HedgeDoc. Completely open source, you get all the features you asked for including real time collaboration.

You can give HedgeDoc (https://hedgedoc.org/) a try as a replacement for Google Docs.

It is the one that works best for concurrent editing IMO (but it is markdown which can be a problem for some)

I use one singular HedgeDoc document for that purpose. It's not exactly the same intent as Google Keep, but it's an awesome project I use anyway and fills the role perfectly for me personally.

HedgeDoc is a web-based, self-hosted, collaborative markdown editor. This open-source option allows a team to easily share ideas on notes, graphs and presentations in real-time. troubleshootmertr finds it a good option "for knowledgebase."

HedgeDoc [0] allows you to collaborate in markdown, and also create slides.

[0] https://hedgedoc.org/ and https://demo.hedgedoc.org/slide-example?both

For writing Markdown documents I use Hedgedoc.

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.

K3s' go.mod[0] is insane.

[0] https://github.com/k3s-io/k3s/blob/master/go.mod