Web preview is launched on new port

[krestyanikov]

Hello Takeshi Hagikura

I noticed strange behavior in ComposeFlow when running Web Preview.
I ran the preview for the first time and it was launched on http://localhost:8080/

Then I made some changes and ran the preview again. This was exposed on http://localhost:8081/. I checked the old preview and it continued to work

Then I closed ComposeFlow thinking that both previews would be stopped, but they continued to work on their ports

I launched ComposeFlow again and ran the preview. This was now running on http://localhost:8082/

Previews on ports 8080 and 8081 also continued to work.

I think this is not entirely expected behavior. It is better if the preview always opens on the same port (8080?) and does not create new processes in the system (that is, the previous process must be stopped), and also when finishing work with ComposeFlow, all running previews must be stopped. What do you think about this?

Thank you.

[thagikura]

It looks like an unintended behavior indeed. When I try it locally, it keeps running in the same port as expected, but it looks like under certain condition the web preview runs in a new port.

Let me mark it as a bug and look into it.