After data folder change, in addition to the new data folder the previous data folder also remains accessible through the web interface (browser), as well as through the api. Even after closing the app.
Observations:
When I start the Manager app on macOS, several processes start running: the app itself, a number of Manager Helper processes, and a ManagerServer process. The data folder is reachable through the app (obviously), but also on local port 55667. Fine.
When I close Manager, all these processes disappear and port 55667 closes. Fine.
But when I, within Manager, change the data folder and Manager restarts, the running ManagerServer process is not terminated but instead a second one is started. The new data folder has a random port number assigned. The old port 55667 remains functional and continues to lead to the previous data folder.
Even if I then quit Manager, the old ManagerServer remains active and port 55667 remains functional and leading to the old data folder.
Is this intentional? To me it is not only confusing, but very inconvenient. When I want to change data folder in a safe way and also have port 55667 back, this is what I have to do:
- within Manager, change data folder through the menu
- close Manager
- find the running ManagerServer process and kill it by hand
- restart Manager - now I finally have the new data folder, the old one cannot be reached anymore, and I also have port 55667 back, for browser activity or api access.
I do not think this is how the function was intended. Killing the running ManagerServer together with the automatic restart would achieve the same, using only step 1.