kvile

Really neat! Also as a Linux user, I deeply appreciate the linux support :-) A few questions and comments: | Kvile | - Awesome, really happy to see a reasonable take on this (open source, offline-first, no telemetry, no acount, etc). Do you think at some point you'll try to monetize it in some way? - Looks like build assets didn't get attached for the latest release (v0.2.1) in Github: https://github.com/tskulbru/kvile/releases/tag/kvile-v0.2.1 | Mockingjay | - Awesome, definitely a valuable project. I'll be sharing this with some friends who could really use this. | Stao | - The website says it's open source, but I couldn't find a link to the source repo. I looked at your github repos and didn't see it in there either. - Great idea! I'm so bad about forgetting to stand so something like this could be super useful.

Hi everyone, I'm Torstein! I've been building Kvile, an HTTP debugging app built with Tauri 2 (Rust + React). Some backstory: I've spent too much time fighting with OpenAPI specs that drift out of sync with reality. Generated clients break, docs lie, and you end up curling the endpoint anyway to see what it actually returns. I wanted something simpler - HTTP requests that live right next to the service I'm working on. Edit a file, send a request, commit it with my code. No spec generation, no sync issues, no "the docs say X but the API does Y." That's why Kvile is built around .http files as the source of truth. Why .http files? - Version control: Plain text that diffs cleanly in git - No lock-in: Standard format supported by JetBrains, VS Code, and others - Docs as code: Requests live in your repo alongside the code they test - S