Prompt
I'm frustrated with local dev setup being different on every machine
Latest observation
Nov 22, 2026
OpenAI APIWeb search: off
That’s a very common pain point. The usual fix is to make the dev environment reproducible and mostly self-contained, so “works on my machine” becomes much less likely.
Practical ways to standardize local dev
-
Use a dev container / Docker Compose
- Put app dependencies, system packages, and services in containers.
- Everyone runs the same versions of Node/Python/Postgres/Redis/etc.
- Best when your app depends on multiple services.
-
Pin tool versions
- Use version files like:
package.json/ lockfiles for JSpoetry.lock,requirements.txt, oruv.lockfor Python.nvmrc,.tool-versions,.python-version
- This prevents “works on Node 18 but not 20” type issues.
- Use version files like:
-
Automate setup
- Have a single command:
make setupjust setup./scripts/bootstrap.sh
- It should install deps, copy env files, set up databases, and run migrations.
- Have a single command:
-
Document the environment
- A short
READMEwith:- required versions
- how to start services
- how to run tests
- common troubleshooting
- Keep it extremely concrete.
- A short
-
Use
.env.example- Check in a template for environment variables.
- Avoid everyone inventing their own config.
-
Add checks in CI
- Run lint/tests in the same container or same pinned versions.
- CI becomes the “source of truth” for whether the setup is valid.
A good target state
- Clone repo
- Run one command
- Get the app running identically on any machine
If you want, I can help you pick a setup approach based on your stack:
- Node/React
- Python/Django/FastAPI
- Java/Spring
- Go
- Full-stack with Docker Compose
- Monorepo