🚀 Feature Request: Running dev-registry in a separate process and make the host:port of the dev-registry configurable when running wrangler dev

[ammubhave]

Describe the solution

Problem: We use docker-compose to bring up our whole stack during development. Since wrangler local mode service bindings use the dev-registry running on localhost, we're forced to put all the workers that have service bindings inside a single container.

Proposed solution:

1. Allow running the dev-registry in a separate process which can run in its own container on a custom port.
2. Allow passing configs to wrangler to make it use this existing dev-registry that may be running in a separate container. This will require adding config for dev-registry host and port

This will let us run all our workers in separate containers but still let them talk to each other.