I've been having great success with LLMs generating Mermaid diagrams and flowcharts from a repo. Claude Code and Cursor both do consistently great jobs. For example: `generate a mermaid swimlanes diagram of the XX logic flow`.
This is what I do previously too! The problem that I realize with them is that mermaid diagrams and flowcharts are static and sometimes oversimplified.
I too have been using sops for years, and agree -- dotenvx encryption seems very similar to sops.
I'd prefer an integration between dotevnx and sops where dotevnx handles the UX of public env and injection, while leveraging sops for secret management and retrieval. Additionally, being able to have multiple keys for different actors is important.
Having a single `.env.keys` file feels risky and error prone. dotenvx encourages adding your various env files, such as `.env.production`, to vcs, and you're one simple mistake away from committing your keyfile and having a bad day.
If sops is not to be integrated, dotenvx could take some inspiration where the main key is encrypted in the secrets file itself, and you can define multiple age key recipients, each of which can then decrypt the main key.
> Brig. Gen. Pat Ryder, Pentagon press secretary, told reporters Friday that an F-22 fighter aircraft based at Joint Base Elmendorf-Richardson shot down the object using the same type of missile used to take down the balloon nearly a week ago.[0]
Shameless plug - I've been building the startup Wedge[0]. In addition to helping prevent application fraud, I deeply believe applicants are _people_ and have more to share beyond a resume.
We enable companies to asynchronously collect a short series of video responses from an applicant either at application time or later in the process.
The tutorials provided by VPS providers like Digital Ocean are a pretty good way to learn how to setup a VPN or any other common webservice yourself. They have a pretty well maintained library:
Stand up a few useful services around the home and harden them. Stuff like Plex/Emby, Paperless-ng, *arr's, etc. Self hosting is addicting and one of the best teachers.
It felt like the mRNA took hold in both my arm, _and_ my heart. Which given the proximity and paths between, is not entirely surprising.
It felt like the vaccine entered my bloodstream and was taken up, in part, by the heart. Which then started making spike protein and soliciting an immune response.
I'd really love to learn more about this, but haven't been able to find any good resources. If anyone can point me in the right direction, I'm all ears!
What does this get you over simply attaching to an existing tmux session? You can already SSH into a machine and join any existing tmux session, or better yet, create a new session from an existing session, and get independent viewports and parallel input, or shared, depending on which window you're looking at.
You can quickly provide a shared session connection to an external third party, so they can access computers that are not publicly accessable and that they normally would not have access to without having to do any credential management.
Great link, I have been searching for something like that for a while. Sharing terminals over Google Meet does not work very well. The video compression is particularly lossy with red on black. Pretty annoying with syntax highlighting or colored shell output.
At a quick glance this is not seem to be end to end encrypted, but tmux is running on their server? That's not something I could ever use for work, we are in regulated domain. But you can run your own server, need to check that out.
We've been toying with duckly (née gitduck) - and it provides shared web browsing, shared editing, and shared terminal. There might be some rough edges with the in-browser "window management" - but overall it works pretty well IMHO:
You can self-hosted tmate, but imnho tmate doesn't add that much value over "grant user ssh access and use plain shared tmux/screen".
In that case, you might (for workstation/laptop) have co-worker's on vpn via wireguard /tailscale, bind sshd to the vpn interface, and allow access via ssh keys/certificates.
>the video compression is particularly lossy with red on black.
The irony is that 20 years ago video conferencing was unthinkable, but I used VNC over a dial-up modem. Lossless and much better for terminal sharing than what is generally available today.
Modern computing feels like the dark Middle Ages after the downfall of the Roman empire in some aspects...
reply