Every repo has the same onboarding ritual: figure out the stack, install the right tools, start the right services, and hope the README is still accurate.

I built Oneconfig because I got tired of writing READMEs that went stale.

What it does

Oneconfig is a single Go binary with two commands:

oneconfig generate recursively scans your project — including monorepos with packages/ and apps/ workspaces — and infers your entire stack: languages, runtimes, package managers, frameworks, databases, env files, Dockerfiles, Makefiles, Procfiles. It outputs a single oneconfig.yml.