From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-yew-comp 1/1] xtermjs: add remote support
Date: Thu, 06 Nov 2025 13:51:56 +0100 [thread overview]
Message-ID: <1762433447.l1m8bfh2tf.astroid@yuna.none> (raw)
In-Reply-To: <a5ae09a7-adf9-4285-bed1-f46a83dd756c@proxmox.com>
On November 6, 2025 1:33 pm, Dominik Csapak wrote:
> some comments inline
>
> On 11/5/25 3:14 PM, Fabian Grünbichler wrote:
>> by defining a new ConsoleType and adding a remote_name property/parameter.
>>
>> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> ---
>> src/apt_package_manager.rs | 9 ++++++---
>> src/xtermjs.rs | 38 +++++++++++++++++++++++++++++++++-----
>> 2 files changed, 39 insertions(+), 8 deletions(-)
>>
>> diff --git a/src/apt_package_manager.rs b/src/apt_package_manager.rs
>> index 2e2d01a..0b392be 100644
>> --- a/src/apt_package_manager.rs
>> +++ b/src/apt_package_manager.rs
>> @@ -202,9 +202,12 @@ impl LoadableComponent for ProxmoxAptPackageManager {
>> let on_upgrade = props.on_upgrade.clone();
>> let on_upgrade = move |_| match &on_upgrade {
>> Some(on_upgrade) => on_upgrade.emit(()),
>> - None => {
>> - XTermJs::open_xterm_js_viewer(crate::ConsoleType::UpgradeShell, "localhost", false)
>> - }
>> + None => XTermJs::open_xterm_js_viewer(
>> + crate::ConsoleType::UpgradeShell,
>> + None,
>> + "localhost",
>> + false,
>> + ),
>> };
>>
>> let toolbar = Toolbar::new()
>> diff --git a/src/xtermjs.rs b/src/xtermjs.rs
>> index 4eb464d..36b5379 100644
>> --- a/src/xtermjs.rs
>> +++ b/src/xtermjs.rs
>> @@ -17,6 +17,11 @@ pub struct XTermJs {
>> #[prop_or_default]
>> pub key: Option<Key>,
>>
>> + #[prop_or_default]
>> + /// The remote name, if this is a remote node shell
>> + #[builder(IntoPropValue, into_prop_value)]
>> + pub remote_name: Option<AttrValue>,
>> +
>> #[prop_or("localhost".into())]
>> #[builder(IntoPropValue, into_prop_value)]
>> /// The node name.
>> @@ -46,8 +51,13 @@ impl XTermJs {
>>
>> // FIXME: separate noVNC and xterm.js, this is not a nice interface!
>> /// Open a new terminal window.
>> - pub fn open_xterm_js_viewer(console_type: ConsoleType, node_name: &str, vnc: bool) {
>> - let url = xtermjs_url(console_type, node_name, vnc);
>> + pub fn open_xterm_js_viewer(
>> + console_type: ConsoleType,
>> + remote_name: Option<&str>,
>> + node_name: &str,
>> + vnc: bool,
>> + ) {
>> + let url = xtermjs_url(console_type, remote_name, node_name, vnc);
>> let target = "_blank";
>> let features =
>> "toolbar=no,location=no,status=no,menubar=no,resizable=yes,width=800,height=420";
>> @@ -72,14 +82,20 @@ pub enum ConsoleType {
>> LXC(u64),
>> UpgradeShell,
>> LoginShell,
>> + RemotePveLoginShell,
>
> would it be possible to have the remote name as property here like this:
>
> RemotePveLoginShell(AttrValue) / RemotePveLoginShell(String)
>
> ? (similar to how we add the vmid to the kvm/lxc variants)
I had that initially..
> we'd lose the `Copy` trait, but then we could... [continued below]
but didn't do it cause of this - if it's okay to drop Copy here, then
yes, it's probably easier to do it that way, also makes it less of a
breaking change!
>
>> }
>>
>> -fn xtermjs_url(console_type: ConsoleType, node_name: &str, vnc: bool) -> String {
>> +fn xtermjs_url(
>> + console_type: ConsoleType,
>> + remote_name: Option<&str>,
>> + node_name: &str,
>> + vnc: bool,
>> +) -> String {
>> let console = match console_type {
>> ConsoleType::KVM(_vmid) => "kvm",
>> ConsoleType::LXC(_vmid) => "lxc",
>> ConsoleType::UpgradeShell => "upgrade",
>> - ConsoleType::LoginShell => "shell",
>> + ConsoleType::LoginShell | ConsoleType::RemotePveLoginShell => "shell",
>> };
>>
>> let mut param = json!({
>> @@ -105,6 +121,13 @@ fn xtermjs_url(console_type: ConsoleType, node_name: &str, vnc: bool) -> String
>> ConsoleType::LoginShell => {
>> param["cmd"] = "login".into();
>> }
>> + ConsoleType::RemotePveLoginShell => {
>> + param["cmd"] = "login".into();
>> + param["remote-type"] = "pve".into();
>> + param["remote"] = remote_name
>> + .expect("RemotePveLoginShell requires remote name")
>> + .into();
>> + }
>
> omit the 'expect' here. In general having unwrap/expect in the gui code
> is not a good idea, since it crashes the whole ui...
>
> even if it's not possible with this patch to trigger it,
> the interface can be wrongly used too easily imho
>
>
> it would also save a parameter in most functions here
>
>
>
>> }
>>
>> format!("?{}", json_object_to_query(param).unwrap())
>> @@ -122,7 +145,12 @@ impl Component for ProxmoxXTermJs {
>>
>> fn view(&self, ctx: &Context<Self>) -> Html {
>> let props = ctx.props();
>> - let url = xtermjs_url(props.console_type, &props.node_name, props.vnc);
>> + let url = xtermjs_url(
>> + props.console_type,
>> + props.remote_name.as_deref(),
>> + &props.node_name,
>> + props.vnc,
>> + );
>> html! {<iframe class="pwt-flex-fit" src={format!("/{url}")}/>}
>> }
>> }
>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-06 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 14:13 [pve-devel] [RFC access-control/manager/proxmox{, -yew-comp, -datacenter-manager}/xtermjs 00/11] add remote node shell Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH pve-xtermjs 1/1] xtermjs: add support for remote node shells via PDM Fabian Grünbichler
2025-11-06 12:39 ` Dominik Csapak
2025-11-05 14:13 ` [pve-devel] [PATCH access-control 1/1] api: ticket: allow token-owned VNC ticket verification Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH manager 1/2] api: termproxy/vncwebsocket: allow tokens Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH manager 2/2] api: termproxy: add description to return schema Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox 1/2] pve-api-types: add termproxy call and types Fabian Grünbichler
2025-11-06 18:48 ` [pve-devel] applied: " Thomas Lamprecht
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox 2/2] http: websocket: add proxy helper Fabian Grünbichler
2025-11-06 12:21 ` Dominik Csapak
2025-11-06 18:48 ` [pve-devel] applied: " Thomas Lamprecht
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox-yew-comp 1/1] xtermjs: add remote support Fabian Grünbichler
2025-11-06 12:33 ` Dominik Csapak
2025-11-06 12:51 ` Fabian Grünbichler [this message]
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox-datacenter-manager 1/4] connection: add access to "raw" client Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox-datacenter-manager 2/4] api: pve: add termproxy endpoint Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox-datacenter-manager 3/4] api: pve: add vncwebsocket endpoint Fabian Grünbichler
2025-11-05 14:13 ` [pve-devel] [PATCH proxmox-datacenter-manager 4/4] ui: pve: node: add shell tab Fabian Grünbichler
2025-11-06 7:46 ` [pve-devel] [RFC access-control/manager/proxmox{, -yew-comp, -datacenter-manager}/xtermjs 00/11] add remote node shell 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=1762433447.l1m8bfh2tf.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox