Closed thiagomajesk closed 1 year ago
Crawly automatically starts a cowboy http endpoint to allow remote controlling of the Crawly service.
It is probably a good idea to let this as an opt-in feature, to avoid unexpected scenarios like this.
It would be nice to be able to disable this. We found this to be an issue when running tests while also running a dev environment. It can be solved by setting different port in the test environment from what is used in dev, but it seems more appropriate to simply disable remote control.
Having crawly as a dev dependency on mix gives an error if I try to run
iex -S mix
in my phoenix project:The error
:eaddrinuse
only happens because I'm already running phoenix inlocalhost:3000
. Why is crawly trying to reserve port 3000? Also: could we improve the error message to be more clear?