podinfo VS jq

I would recommend setting up a simple Kubernetes cluster (maybe using KinD, minikube, or something similar) and getting to know how it works (you could try deploying something like Kuard or Podinfo or deploy one of your own containerized apps to Kubernetes).

Podinfo does something very similar while coming with alot of additional features.

A more mature example: https://github.com/stefanprodan/podinfo, k8s specific.

Try this podinfo implementation.

I have chosen the well known podinfo application as an example, and I have developed the base and some components associated to it.

Check out https://github.com/stefanprodan/podinfo it’s my go to for creating new microservices

It focuses on an "uninteresting" workload and uses podinfo as the sample app. This is because it's easy to deploy and customize with a sample Helm chart.

That should recursively list directories, counting only the files within each, and output² jsonl that can be further mangled within the shell². You could just as easily populate an associative array for further work, or $whatever. Unlike bash, zsh has reasonable behaviour around quoting and whitespace too.

¹ https://zsh.sourceforge.io/Doc/Release/User-Contributions.ht...

² https://github.com/jpmens/jo

³ https://github.com/stedolan/jq

What I miss from jq and what is implemented but unreleased is platform independent line delimiters.

jq on Windows produces \r\n terminated lines which can be annoying when used with Cygwin / MSYS2 / WSL. The '--binary' option to not convert line delimiters is one of those pending improvements.

https://github.com/stedolan/jq/commit/0dab2b18d73e561f511801...

If you have jq installed you can use it to make the output look nicer.

It requires jq for JSON processing and GNU parallel for concurrent searches in the notebooks.

jq is your friend.

The jq command (https://stedolan.github.io/jq/) is useful pulling that information out.