I built runnem, a CLI for managing local services in projects with multiple components like frontend, backend, and database.
I have a few projects going at once, each with several services. When I come back to one after a few weeks to fix a bug or make a change, I always forget how to spin everything up. Which command runs what? What depends on what?
runnem solves that for me:
- runnem up and runnem down to start or stop everything - Handles service dependencies automatically - Uses screen under the hood (I'm keen on screen) - Manages logs, rotates them, and cleans up ports - Simple YAML config per project (runnem.yaml)
I didn’t research alternatives deeply. I’ve used Tilt before, mainly with Docker, but wanted something lightweight and terminal-native for projects with mixed stacks. Also, did I mention that I like screen? :)
I haven’t tested it much with services that run inside Docker, or local databases (I use neon.tech), or unusual screen setups. There may be edge cases it doesn’t handle yet. It would be great if people find issues I can patch over time.
It's made my dev workflow a bit smoother. I'd love to hear what you think!
Docs: https://runnem.com