Split Port

[genuspeople]

What if we could configure separate ports — one for client-to-server connections and another for the web management interface? That way, we could keep the web manager hidden from general internet scanning and browsing.

[bitbound]

Unfortunately, this would require a major re-architecture.

Although the web front-end is Blazor WebAssembly, it still uses server-side rendering for authentication and first render. As such, the front-end and back-end are tightly coupled and served from the same dotnet process. Decoupling them would be a major effort.

After the decoupling the frontend, the APIs and websocket/SignalR endpoints for devices and users would need to be separated into different services. Currently, the backend relies on in-process state for coordinating sessions and streaming between users and devices. Again, this would be major architectural overhaul to separate.

That said, I don't disagree with your intent. But it's just not something I can implement now with the relatively short runway I have.

If ControlR becomes financially self-sustaining, I am interested in dropping Blazor for React, and a larger decoupling effort could be made at that time. But I'd need to get to that point first in the next 18 months.