chore: update shared app related doc #154
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| * **Centralized management**: Only administrators can install the core service of a shared application. Administrators are responsible for installing, configuring, and hosting the app's service, resources, and runtime environment within the cluster. | ||
| * **Easy identification**: In Olares Market, shared applications are typically marked with a "Shared" label for easy identification. | ||
| * **Flexible access**: The method for accessing a shared application depends on the app's form: | ||
| * **Headless backend service**: For shared applications that do not have a direct user interface (e.g., Ollama), users typically need to install an **authorized application** to serve as the service access point. For example, users within the cluster can access the Ollama service via Open WebUI or LobeChat. |
There was a problem hiding this comment.
Perhaps use another example. Now there’s a visible entrance for Ollama.
There was a problem hiding this comment.
Or, don't mention it at all?
|
|
||
| Authorized applications are applications that have been granted access to specific shared applications within Olares. They typically provide a user-friendly interface, allowing users to easily access the APIs or services exposed by the shared applications. | ||
|
|
||
| For example, Open WebUI, LobeChat, and n8n are authorized applications for Ollama. Dify Shared is the authorized application of itself. |
There was a problem hiding this comment.
Originally, an authorized application refers to the cluster-side interface for a cluster application (e.g., ComfyUI for Cluster & ComfyUI). The reason we introduced the “Shared” version was to simplify the explanation and avoid the need to clarify why two applications must be installed to run a single service.
In this sense, Open WebUI, LobeChat, and n8n are not authorized applications for Ollama. This is because Ollama can operate independently, and users can access online models without needing to install Ollama. Perhaps you meant “reference applications” here? As they might serve as separate applications to access the service?
There was a problem hiding this comment.
So perhaps we don't need to introduce what an authorized application is? Or we keep all of these concepts, because users can see “ComfyUI Shared”, “ComfyUI” and “ComfyUI Shared” at the same time.
There was a problem hiding this comment.
@TShentu Comments?
There was a problem hiding this comment.
I believe this is referring to "reference applications." Both the Shared app and the Reference app should be explained here. Typically, each application runs in its own sandbox (namespace) and cannot access other applications’ sandboxes. However, in this case, the Reference app is pre-authorized by the Shared app, allowing it to access the Shared app’s sandbox data.
The key message is that reference applications represent a special exception in which an app chooses to share its sandbox data with another app, allowing the receiving app to access that otherwise private information.
There was a problem hiding this comment.
I don't think being an authorized application of a shared app rules out the option of the app to access other online resources. It just means the app is authorized to access the service/resource of the shared app. Also as I understand it, we replaced reference app with authorized app... so these two (reference app and authorized app) are the same in this context...
This PR replaced the original cluster-scoped concept with "shared application". Following docs are impacted: