urbackup-client-docker VS HedgeDoc

For backups I use UrBackup, and with the UrBackup Client container, I can back up each application's persistent volumes. I run it in Docker for now, and store backups on a BTRFS Zvol in my ZFS array. Though technically it's not totally safe to backup databases this way, I have not run into many issues going this. Restoring or migrating is as simple as spinning up my helm chart on the new server (with only the client and its Persistent Volume Claims active), hitting restore, and then upgrading the deployment with the actual databases and services.

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.