This may be familiarity bias, but I often find `kubectl` and related tools like `k9s` more ergonomic than `systemctl`/`journalctl`, even for managing simple single-replica processes that are bound to the host network.
In some sense, Kubernetes is just a portable platform for running Linux services, even on a single node using something like K3s. I almost see it as being an extension of the Linux OS layer.
It seems like this adds much tighter integration between the caller and callee processes used named pipes and RPC communication, such as being able to share input/output streams within the same terminal session, which is a significant value add compared to runas.exe.
As someone who develops for both Windows and Linux I find WSL to be very useful. Much better than my previous method of dual booting Linux and Windows. I've yet to run into a problem that I needed to boot into native Linux for.
I've always been interested in the technical distinction between an API "key" and an API "token". And the terminology of "key" used to confuse me, because I associated that with cryptography, and I thought an API key would be used to sign or encrypt something. But it seems that in many cases it's basically just a long, random password.
I've had a lot of fun combining Obsidian with Claude Code. It's very much like having a personal coach. It's a low-friction way to have it remember things about me without having to re-provide a bunch of context on new chats.
Obviously you have to be careful what you share, and make your own decisions about the utility/privacy trade-off.
I also agree with keeping it very simple. I went down a rabbit hole where I installed a bunch of plugins and basically treated it as a dynamic web application. Now I keep it simple and have basically no plugins, no enforced structure. I don't try to do Zettelkasten or anything like that. Usually I just write in my daily note and link to other notes as makes sense, but I don't force it.
What do you anticipate to be the hardest part of supporting a self-hosted solution? I've worked a fair bit on converting SAAS -> self-hosted and always interested to hear others' pain points.
I imagine a lot of the organizations that would find this most valuable, and would be willing to pay a lot, would be the same ones that would require something like this.
This sounds interesting on paper but I wonder how likely it is they actually pull it off. Even putting aside the logistics of installing new oses across a bunch of workstations, migrating from legacy Active Directory domains is something even small enterprises struggle with.