Dashboard starts without Port and ui

Hello everyone
I don't like always accessing the dashboard via url:port/ui.
I want to open the dashboard directly when I access my Raspbian's URL. However, I want to retain the port for changes to the flows (1880). (The port will probably be protected once I've achieved this here.)
If I change the path for ui in settings.js, the port defined there remains, as far as I understand.
Is there an easy way to change this?

The dashboard (both v1 and v2) use the same HTTP server as the Node-RED editor, there is no way to run them on separate ports on their own.

With Dashboard v1 (which I can tell you are using because of the /ui) you can choose to remap the route from /ui to / and move the editor to something else (like /editor) and then use something link nginx as a revese proxy to remap the / path to port 80 (or 443 for HTTPS) and leave the editor on 1880 /editor.

While you could move Node-RED's port to port 80 (though only if running it as a privileged app), that would not let you have the Editor on a port and the Dashboard not on a port.

So, as hardillb has suggested, your only choice would be to use a reverse proxy such as an appropriately configured NGINX server or HA Proxy to front-end Node-RED. You will find some NGINX configuration shared previously on the forum.