Problem
ix view opens up the visualiser on port 8080, where I already have an application running. I see no failure, but it is not accessible as it cannot bind the port. I cannot change this port.
Even after shutting down my existing service on the port, I cannot find the visualiser after running the command again, I have no service running on that port.
Proposed solution
Add a -p option to ix view to allow the user to specify another port.
Why it matters
This would bring more usability for developers, as most of us have services already running on certain ports. There might be some way to configure this already that I'm not aware of, but I feel a command line option to the command is most intuitive.
Problem
ix viewopens up the visualiser on port 8080, where I already have an application running. I see no failure, but it is not accessible as it cannot bind the port. I cannot change this port.Even after shutting down my existing service on the port, I cannot find the visualiser after running the command again, I have no service running on that port.
Proposed solution
Add a
-poption toix viewto allow the user to specify another port.Why it matters
This would bring more usability for developers, as most of us have services already running on certain ports. There might be some way to configure this already that I'm not aware of, but I feel a command line option to the command is most intuitive.