Built a CLI that reads any codebase and launches it with one command. Now I'm trying to figure out if this is actually worth building further
Context: I do a lot of work across different client codebases, and I got tired of the ritual every time I pick one back up: figuring out the env vars, the db, the right node/python version, whatever config drift happened since last time. So I built a CLI that reads the source, auto-detects the stack, and spins the whole thing up (local or remote) with one command and no manual config.
It also generates end-to-end tests straight from the source code and runs then in isolated sanxboxes. This part came out of the same annoyance, wanting avoit long manual tests on every client project.
Where it's at: it works, two other freelancers are using it for real work, but it's not public and I haven't decided if this is a "ship it as a product" thing or stays a personal tool. That's what I'm trying to figure out.
If you handle multiple projects/clients, I'm genuinely curious how you getting things running today, and whether this would actually solve something for you or if it's a "neat but I don't have this problem" kind of thing.
If you want to go deeper, I put together a short 6-minute voice interview (no pitch, just questions about your workflow): [https://buildpad.io/interview/ybucrg6a]. Totally optional, happy to just hear thoughts in the comments too.