dev-sanity

Local dev environment health checks validate repo paths, verify environment files, check running Docker containers, and test HTTP health endpoints using a mode-driven configuration file. This surfaces the first startup failure quickly to guide remediation.

Mode-driven validation loads repo, environment, container, and health endpoint configurations from a private modes/config.sh file. It applies these configurations to check locally running Docker containers and surface any misconfigurations before you start debugging.

Yes, you need Docker and curl installed to validate your local development stack. Docker checks that local containers are running, while curl validates that HTTP health endpoints respond correctly during the environment validation process.

Yes, you can verify that local Docker containers are running, repo paths exist, and environment files are present before starting a local stack. This targeted validation identifies configuration or startup issues early in development.

The best way to surface local dev configuration issues is to run a sanity check against your configured local stack. It validates repos, environment files, containers, and endpoints to pinpoint the first failure and guide remediation.