Open AtkinsSJ opened 6 months ago
A few things come to mind:
A workaround might be to scan for available ports (like the Puter dev server does) instead of hard-coding them. That doesn't fix this issue, but would make it less of a problem, and would generally be good to do as we don't know what ports someone's system might be using already.
I'm running on Linux, and this happens a bit inconsistently for me.
Steps:
dev-runner ./run-phoenix-http.json5
stop
to shut it downnode
processes related to it have exiteddev-runner ./run-phoenix-http.json5
againAfter doing the same again, I only had the
:8080
server fail to start. Then a third time, they both succeeded. But it definitely varies.