Local Development Environment With Containers
Standardise dev environments across a team.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design a containerised local development setup. Application stack: [STACK]. Services needed (database, cache, queue): [SERVICES]. Operating systems used by the team: [TEAM_OS]. Onboarding time today: [ONBOARDING_TIME]. Provide a repository layout, a compose file concept with services and volumes (in generic form), commands for common tasks in a Makefile or script, seed data approach with fake data only, and hot reload advice. Include troubleshooting for the five most common problems (ports, volumes, file permissions, performance on some operating systems, stale images). Add a one-page onboarding guide with a target of working in 30 minutes and a checklist to verify. Suggest how to keep the setup close to production without copying production data. Add a section on keeping development setup instructions tested: run the onboarding guide in CI on a clean machine monthly. Provide a short list of what should stay outside containers for performance reasons on some systems, and how to document the exceptions. Include a checklist of environment variables and how to manage them safely without committing secrets.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.