[DOCS]: Desktop app acting as a server

[lucianthorr]

Description

I found this point in another thread

The desktop app serves the GUI only within the client, but that discoverability is if you want to use the API for the desktop client. Only the docker version serves the GUI from the server - so that it can be accessed in a browser.

This should be clearer in the documentation AND in the desktop app. To me, it really appears in the app as if you are starting a server that can be accessed from the LAN.

[timothycarambat]

You can, for the backend, not use of the frontend. The app is able to be run with its server attached to 0.0.0.0 so that you can expose the backend on LAN.

Trying to run a multi-user environment off a single desktop client is not and won't ever be supported, but some like to leverage the client for other scripts so that is why we expose it at all.

If you want multi-user with the UI, that is the Docker app - we can make a page about this feature - however I think covers the idea currently

[lucianthorr]

Thanks. Yeah, that Docker vs Desktop comparison does seem sufficient. My mistake was in misunderstanding the Network Discoverability description in the Desktop's Settings. I thought it was saying that it's making its features available on the local network. (I'm one day old on AnythingLLM so I wasn't sure what to expect really).

[timothycarambat]

@lucianthorr That is a totally fair exception imo. The reason we dont host a UI via that backend server is because inevitably we are going to have people trying to host the desktop app as a server and eventually expose their desktop to the internet via a tunnel or something so they can use it on external networks and that is not a behavior we should encourage for people since the desktop app can be extended to have some powerful privileges or access.

The Docker version has the auth and containerization and such to at least mitigate that risk