[GH-ISSUE #3] Requirements for plugins #3

New issue

Open

opened 2026-03-01 15:35:59 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 15:35:59 +03:00

Owner

Originally created by @bogeeee on GitHub (Apr 21, 2025).
Original GitHub issue: https://github.com/bogeeee/pve-manager-electrified/issues/3

Hey there, what do you need for it? Here's my current concept:

Plugins are, at the current stage and for simplicity, client-only. They are packaged as npm packages and published via by npm. You can list other dependencies there, and they will be automatically installed and the web will automatically be rebundled. I'll make this process very simple for the dev...;). Even thinking of offering a one-click VS-Code IDE for it, which runs in a docker container.

I'll expose the complete promox API, using https://github.com/Corsinvest/cv4pve-api-javascript
Plus methods to execute shell commands (if loged on as root). The paradigm is more shifted towards rich clients, execing shell commands and doing the processing on the client side. Assuming the case, that you're mainly using the new features-of interest as root user. But tell me, if there are more use cases, or this doesn't match).
Also, i'll offer a method, to read, write, and even watch any (config-) file on the host (if you're root, of course). Watching happens via websocket notifications.
If the plugin needs additional server side functionality, please list the use case.

Also: Which hooks do you need? Planned are:

Contextmenu hooks für Datacenter, Node, Guest, Disks, Devices,...
Hook to add panels (like these "Overview", "Console", "Hardware",...)

And what UI libraries do you need?
I'll definitely integrate React + Blueprintjs and add an extJs2react bridging component, as i've already done that in another project. So devs should be able to just code their panels, dialogs, etc in React.

Originally created by @bogeeee on GitHub (Apr 21, 2025). Original GitHub issue: https://github.com/bogeeee/pve-manager-electrified/issues/3 Hey there, what do you need for it? Here's my current concept: ---- Plugins are, at the current stage and for simplicity, **client-only**. They are packaged as npm packages and published via by npm. You can list other dependencies there, and they will be automatically installed and the web will automatically be rebundled. I'll make this process very simple for the dev...;). Even thinking of offering a one-click VS-Code IDE for it, which runs in a docker container. - I'll expose the complete promox API, using https://github.com/Corsinvest/cv4pve-api-javascript - Plus methods to execute shell commands (if loged on as root). The paradigm is more shifted towards rich clients, execing shell commands and doing the processing on the client side. Assuming the case, that you're mainly using the new features-of interest **as root user**. But tell me, if there are more use cases, or this doesn't match). - Also, i'll offer a method, to read, write, and even watch any (config-) file on the host (if you're root, of course). Watching happens via websocket notifications. - If the plugin needs additional server side functionality, please list the use case. Also: Which hooks do you need? Planned are: - Contextmenu hooks für Datacenter, Node, Guest, Disks, Devices,... - Hook to add panels (like these "Overview", "Console", "Hardware",...) And what UI libraries do you need? I'll definitely integrate React + Blueprintjs and add an extJs2react bridging component, as i've already done that in another project. So devs should be able to just code their panels, dialogs, etc in React.