Problem Statement
I've just had a go with the new Spotlight local debugger - it's absolutely fab! In order to use it though, I had to make a little hack; we run our local dev environment in a docker container which doesn't have Node installed, and we have a separate container we use for Node operations. I got it working by editing my vendor files to overload the http://localhost:8969 with the hostname of my Node container, which all worked nicely - it would be amazing if there could be a config option for this.
Solution Brainstorm
Perhaps a 'spotlight_url' config parameter to pass into Sentry::init() would be simplest, that could then override the hardcoded value in sentry-Transport/HttpTransport::sendRequestToSpotlight()?
Problem Statement
I've just had a go with the new Spotlight local debugger - it's absolutely fab! In order to use it though, I had to make a little hack; we run our local dev environment in a docker container which doesn't have Node installed, and we have a separate container we use for Node operations. I got it working by editing my vendor files to overload the http://localhost:8969 with the hostname of my Node container, which all worked nicely - it would be amazing if there could be a config option for this.
Solution Brainstorm
Perhaps a 'spotlight_url' config parameter to pass into Sentry::init() would be simplest, that could then override the hardcoded value in sentry-Transport/HttpTransport::sendRequestToSpotlight()?