The plugin system is designed with a focus on security, flexibility, and ease of use. Below is the proposed workflow for plugin integration and execution:
-
Plugin Connection Request: Plugins will initiate a connection request to the main application.
-
Execution Permission Request: Upon connection, plugins will request
execpermissions to execute specific commands. Examples include:docker ps -adocker run -d %@
-
User-Driven Permission Granting: The user will review and grant the necessary permissions to the plugin based on the requested actions.
-
Command Execution: Once permissions are granted, the plugin will proceed to execute the approved commands.
-
Result Handling: The application will handle the results of the plugin's execution, including returning output, errors, and progress updates.
-
Logging: All plugin activities will be logged by the application for auditing and troubleshooting purposes.
For the initial phase, only exec permissions will be made available to ensure a controlled environment.
We are open to suggestions and contributions to refine this plugin system. Your feedback is invaluable in shaping the future of our plugin ecosystem.
For any inquiries or to provide feedback, please reach out to us at:
- Email: [email protected]
- Reply-To: [email protected]
Please ensure you are whitelisted in our system to receive prompt responses.
Join us in building a powerful and secure plugin system that empowers developers and enhances application functionality.
Let's join hands and start a new chapter of the plugin system!
Notes on Plugin Development Language and APP WKWebView Injection Protocol The main programming language for plugin development is JavaScript. For plugins that need to interact with the APP's WKWebView, please follow the injection protocol specified by the APP to ensure seamless integration and proper functionality. We provide necessary technical support and guidance to help developers successfully develop and integrate plugins.