It’s always worth to learn something new.

Yes, it is normal.

# fail2ban-client status sshd
Status for the jail: sshd
|- Filter
|  |- Currently failed: 10
|  |- Total failed:     4433
|  `- Journal matches:  _SYSTEMD_UNIT=ssh.service + _COMM=sshd
`- Actions
   |- Currently banned: 27
   |- Total banned:     668
   `- Banned IP list:   2.57.122.194 45.148.10.183 195.178.110.30 2.57.122.208 92.118.39.195 103.74.123.88 92.118.39.23 2.57.122.196 92.118.39.197 45.148.10.151 92.118.39.236 178.20.210.185 68.178.161.186 80.94.92.183 92.118.39.63 2.57.122.197 2.57.122.191 2.57.122.189 80.94.92.171 94.156.152.18 14.225.7.70 45.78.198.199 211.253.9.160 159.224.213.138 1.214.42.172 103.239.165.114 77.239.111.233

You need both. If you want to start as fast as possible, learn Kotlin first.

Everywhere except some Windows only apps.

My choice is OpenWrt and specialized hardware. It is much better suited for home use and has much lower power consumption (i.e. silent). Right now I’m looking for replacement for my home router and going to buy one of Banana Pi boards. However in the US the optimal choice may be different.

So what does the existing CLI do if it is not a runner?

TL;DR

Is it GUI only?

I didn’t try many of them. I use Ansible for my job, but sometimes I hate it. I would try Terraform/OpenTofu or Salt if I were looking for alternative.

deleted by creator

you don’t really need to scale a homelab that much

Maybe. But you never know this beforehand.

if something breaks, you just want to quickly fix it manually because “doing the Ansible” is more of a pain

In most cases you just need to replay a playbook for quick fix. But I agree that the proper fix will likely take a longer time (while downtime is much shorter).

now idempotency and documentation-as-code is out of the window.

Let @BruisedMoose@piefed.social decide.

P. S. I don’t like Ansible, other tools can be easier to use. But I don’t want to recommend something concrete.

It will not if your parser is not overcomplicated and does not populate some huge structures with data. You only need to find tokens and compare them with field names and values you are looking for. Regexes are slower and don’t allow processing escaped characters correctly.

It is hard, if even possible, to keep documentation up-to-date. Better use a configuration management system (salt, ansible etc.) for your servers. Yes, you need to learn how to use it. Yes, it will take a longer time to make changes in your configuration. But as a result you’ll have a self-documented configuration-as-a-code that will allow you to scale your setup as you need. Reproducing something won’t require reading your notes, remembering your actions etc.

Selfhosting for personal projects is cheap. I’d choose Forgejo because it not so resource hungry as GitLab.

For my personal projects (all FOSS) I use Codeberg and mirror them to hosted GtiLab and GitHub.

Sorry, I missed that L, and I’ve never heard about JSONL before (although worked with JSON logs that are effectively JSONL). So, well, you may use grep, however it can be inefficient (depends on regex engine and how good you are in regexes). It is also easy to make a mistake if you are not very proficient in regexes. So I’d prefer using JSON parser (jq or another, maybe lower level if performance matters) over grep anyway.

Bad idea. First, file is read sequentially, and you can’t parallelize this. Second, grep is a bad solution for structured files. Better use jq or something similar.

Ask AI to do this for you.