From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 41CA21FF0A7 for ; Wed, 02 Sep 2026 13:55:04 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id C642121270; Wed, 02 Sep 2026 13:55:03 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 02 Sep 2026 13:54:59 +0200 Message-Id: Subject: Re: [PATCH datacenter-manager 3/3] ui: make the default dashboard page configurable From: "Lukas Wagner" To: "Dominik Csapak" , "Lukas Wagner" , X-Mailer: aerc 0.21.0-0-g5549850facc2-dirty References: <20260820081746.989972-1-d.csapak@proxmox.com> <20260820081746.989972-4-d.csapak@proxmox.com> <78e8a07c-e905-4083-9fe6-d292fbf05865@proxmox.com> In-Reply-To: <78e8a07c-e905-4083-9fe6-d292fbf05865@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1788350096065 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.543 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: VXLXNYN4EFP7I5YINLIX4OKIMROVEYUX X-Message-ID-Hash: VXLXNYN4EFP7I5YINLIX4OKIMROVEYUX X-MailFrom: l.wagner@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: On Wed Sep 2, 2026 at 1:10 PM CEST, Dominik Csapak wrote: >>=20 >> - Have a 'My Settings' dialog in the user menu similar to PVE > > I would probably opt for this, since we already are missing > some settings that would be nice here (e.g. xterm.js/novnc settings > that we already have in PVE) > Seems good to me! >>=20 >> - Abandon the local setting altogether and make it a per-user setting >> that is stored in the backend. Might require bigger changes, since I >> don't think we have any good way to store per-user properties right >> now. Users that routinely use multiple browsers and/or devices might >> prefer this over a local setting. >>=20 > > One of the biggest thing that makes me a bit hesitant to do this > is that we don't usually have per user backend (gui) settings at all > > If we do want those here, I'd also like them on the PVE side > (e.g. tree/view settings) > Yeah, it would definitely a much bigger undertaking. One where it definitely makes sense to think about the cross-product implications. I guess storing these settings in local storage *now* does not really stop us from changing it later to a per-user, backend setting, if we think that this would be a good idea, so no need to overthink this right now. >>=20 >> What do you think? > > see above, currently I'd prefer to implementing a 'my settings' window. > > another option would be to have the global default set in the backend > but this clashes a bit with the permissions per view etc... > >>=20 >> One further thing that I have noticed: If a view that is used as a >> dashboard is deleted, we should probably fall back to the default >> dashboard again. Otherwise user might complain about 'broken' dashboards >> without a clear indication about what is wrong. > > yes that sounds sensible (at least as long as we only save it in > the browser local storage. if we have a setting in the backend > we could prevent deletion if anybody is using that or reset > all users preferences) > Maybe the UI could then also show a small hint in the header, maybe something like "View xyz does not exist, showing default dashboard instead" I guess if there is such a hint, we could also just shown an empty view instead of the default dashboard, since then the user knows what's going on.