fix(ExApp): merge AppAPI concepts page into developer manual AppAPI overview page

Signed-off-by: Edward Ly <contact@edward.ly>
This commit is contained in:
Edward Ly
2024-10-23 17:12:05 -07:00
parent d19f2426fc
commit 72d143ede7
3 changed files with 20 additions and 20 deletions

View File

@@ -1,19 +0,0 @@
Concepts
========
API Access Control Mechanism
----------------------------
Each application defines list of API groups it intends to access.
This system easily allows you to increase the level of trust in applications.
Even prior to installation, it's possible to ascertain the API groups to which an application will gain access.
Extensible Deployment
---------------------
The system should support the expansion and integration of new deployment methods, avoiding any tight coupling with a specific deployment type.
Applications should be capable of indicating the deployment methods they can accommodate.
Given the evolving landscape of new technologies and the potential emergence of more intricate or simplified deployment options,
the system is architected to seamlessly embrace the integration of novel deployment modes.

View File

@@ -10,4 +10,3 @@ ExApps management
CreationOfDeployDaemon
TestDeploy
ManagingExternalApplications
Concepts

View File

@@ -33,3 +33,23 @@ AppAPI brings out the following terms frequently used in the code:
* ``ExAppScope`` - granted to ExApp scope group of access to API routes
* ``ExAppApiScope`` - pre-defined scope group of access to list of API routes
* ``FileActionsMenu`` - entry in files actions menu (context menu)
Concepts
--------
API Access Control Mechanism
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Each application defines list of API groups it intends to access.
This system easily allows you to increase the level of trust in applications.
Even prior to installation, it's possible to ascertain the API groups to which an application will gain access.
Extensible Deployment
^^^^^^^^^^^^^^^^^^^^^
The system should support the expansion and integration of new deployment methods, avoiding any tight coupling with a specific deployment type.
Applications should be capable of indicating the deployment methods they can accommodate.
Given the evolving landscape of new technologies and the potential emergence of more intricate or simplified deployment options,
the system is architected to seamlessly embrace the integration of novel deployment modes.