From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 84EF61FF13C for ; Thu, 05 Mar 2026 11:17:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CF0E13F60; Thu, 5 Mar 2026 11:18:23 +0100 (CET) From: Dominik Rusovac To: pdm-devel@lists.proxmox.com Subject: [PATCH datacenter-manager v2] ui: adjust testing description Date: Thu, 5 Mar 2026 11:18:13 +0100 Message-ID: <20260305101814.103462-1-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1772705872451 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.506 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NUMERIC_HTTP_ADDR 1.242 Uses a numeric IP address in URL PROLO_LEO1 0.1 Meta Catches all Leo drug variations so far RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.018 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.703 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 1.386 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record WEIRD_PORT 0.001 Uses non-standard port number for HTTP Message-ID-Hash: DKRL6LUICFRVQIFXLKOQIH3OOBPWFS5P X-Message-ID-Hash: DKRL6LUICFRVQIFXLKOQIH3OOBPWFS5P X-MailFrom: d.rusovac@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Describe how to use trunk server for testing. Signed-off-by: Dominik Rusovac --- changes since v1: * adjusted wording * added PDM acronym * added introduction with high-level description ui/README.md | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/ui/README.md b/ui/README.md index f083ea5..ec9b9d4 100644 --- a/ui/README.md +++ b/ui/README.md @@ -1,21 +1,18 @@ -# Experimental Yew GUI for Proxmox Datacenter Manager +# Experimental Yew GUI for Proxmox Datacenter Manager (PDM) # Testing -1.) start datacenter manager +For testing changes in the web UI with rapid development workflow, we recommend to: -sudo ./target/debug/proxmox-datacenter-privileged-api -sudo -u www-data ./target/debug/proxmox-datacenter-api +1. run a PDM daemon, which can be done on a virtual machine or an existing instance; and +2. use [trunk](https://github.com/trunk-rs/trunk), which builds the web UI upon changes and proxies API calls to the PDM daemon, so the frontend can talk to the PDM during development. -2.) either: start local trunk server +Assuming PDM is reachable via 172.16.254.1:8443. - trunk serve --proxy-backend=https://localhost:8443/api2/ --proxy-insecure +To test on http://localhost:8080, use: - then test with url: http://localhost:8080 + trunk serve --proxy-backend=https://172.16.254.1:8443/api2/ --proxy-insecure -2.) or: copy files into pdm js folder: +To test elsewhere with a secure connection, say https://dev:8080/, generate a cert to obtain `api.key` and `api.pem`, and use: - make all - make install - -And test with url https://localhost:8443 + trunk serve --address 0.0.0.0 --serve-base / --proxy-backend https://172.16.254.1:8443/api2/ --public-url https://dev:8080/ --proxy-insecure --tls-key-path api.key --tls-cert-path api.pem -- 2.47.3