Working on turning individual disparate services into a unified zero-trust overlay network (what we're calling a Synthetic Environment™) where mocks and real services can be integrated or work seamlessly together, accessible through traditional networking or exposed public tunnels.
This is a developers tool, that can be used during development to seamlessly integrate mocks and changes into existing systems. Or easily expose internal work through a public tunnel. Or if been in an position where its hard to push to staging, pre-prod or other environments because of many competing constraints, then this product may help.
This project has made me think about more about the difference between TUI's and "command-line" (CLI) apps as categories. Traditionally CLIs were kind of run-and-exit tools, and "real" TUIs were long-running, stateful apps, but what we're creating seems to sit somewhere in between the to.
With richer terminals and libraries like this, the distinction feels more about interaction style than environment. Curious how others think about that boundary when designing tools that work in terminals.
I've had a similar thoughts! I just put together a document with four sections (original, sanitized, output, unsantized) and built a little command-line tool to automatically filter and copy content between them. For now, my tool uses simple regex and specific keywords, but I really like the approach you're taking!! This is definitely an interesting problem that needs a good solution. I'm excited to see your WASM implementation!
This is a developers tool, that can be used during development to seamlessly integrate mocks and changes into existing systems. Or easily expose internal work through a public tunnel. Or if been in an position where its hard to push to staging, pre-prod or other environments because of many competing constraints, then this product may help.