I'm not sure what you're asking. Sometimes development happens on developer computers, staged for review to instances/databases spun up for that purpose. Someti

I'm not sure what you're asking. Sometimes development happens on developer computers, staged for review to instances/databases spun up for that purpose. Sometimes the developers have a parallel but scaled-down copy of the production environment. The web applications I work on, with one or two exceptions in the past, don't have complex dev requirements. Often deployment amounts to "git pull." If you work with complex dev environments and CI/CD pipelines that cost enough to care about, maybe look at how to simplify that. How development and deployment happens varies tremendously, so I don't have any general advice beyond "simplify" and examine the processes and resources your developers use and say they need. Every process and resource should have cost, benefit, and risk assigned. Left to themselves programmers too often add complexity and process for its own sake, or out of unexamined adherence to "best practices."