From: Dex via pve-devel <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Dex <dex@fur.lol>
Subject: [pve-devel] PVE Plugin System
Date: Mon, 22 Dec 2025 17:42:12 +0000 [thread overview]
Message-ID: <mailman.163.1766485018.353.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4751 bytes --]
From: Dex <dex@fur.lol>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: PVE Plugin System
Date: Mon, 22 Dec 2025 17:42:12 +0000
Message-ID: <OZjFLZr9Sa_d3-OvTbmjo_GlmwLoIUrONn_56VORPqWeAaaQeehPHNRPpnTtUd4Sg1ySXc73AvBAjynmXl1A4MTLHhhwiN3CimKf5PjjoY8=@fur.lol>
Hello,
I'm planning to implement a plugin system for PVE to enable runtime loading of third-party code into pve-manager. It would allow loading of Perl code for things like creating custom REST endpoints, and modifying existing endpoint logic. It would also allow loading of Javascript code into the web UI to allow for new UI elements/pages to be created. The goal is to provide an way to run/load third party code as part of pve-manager instead of needing to modify files in a deployment to provide this support.
I'm looking to implement this system for one of my projects, and was curious if you guys would be interested in collaborating on implementation details as I work through development, and if there would be interest in having a patch submitted to the upstream for this.
Let me know what you think -
Dex
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-12-23 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 17:42 Dex via pve-devel [this message]
2025-12-23 12:05 ` Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.163.1766485018.353.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=dex@fur.lol \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.