Currently if something is running on the port that cli webserver needs, it errors out with an "address in use" message. There's no indication which port it's trying to use.
If user knows the port number, they could debug it with an lsof command then kill the process that's using that port. We should look into whether this can be automated.
E.g. User runs dev -> port conflict error -> cli runs lsof to get the process that's running on that port -> cli provides a friendly error message about that process and how to terminate it.
linear[bot]
commented
3 weeks ago
Currently if something is running on the port that cli webserver needs, it errors out with an "address in use" message. There's no indication which port it's trying to use.
If user knows the port number, they could debug it with an lsof command then kill the process that's using that port. We should look into whether this can be automated.
E.g. User runs dev -> port conflict error -> cli runs lsof to get the process that's running on that port -> cli provides a friendly error message about that process and how to terminate it.