From: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
Subject: [PATCH cluster/manager 0/2] Configurable window titles for nodes
Date: Thu, 16 Jul 2026 10:48:05 +0200 [thread overview]
Message-ID: <20260716084807.77400-1-t.ellmenreich@proxmox.com> (raw)
Thank you @Dominik Csapak for your comments.
Configurable window titles for nodes
====================================
Currently the window title is fixed to the following string:
$nodename - Proxmox Virtual Environment
This has become problematic for users with multiple clusters, each containing
the same node name. To help distinguish between tabs, it has been requested [1]
that the window title be made configurable with the fqdn as an option.
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=5475
Implementation
--------------
After considering the different options, I have deemed a server side
implementation, through the datacenter.cfg, to be the better option.
Specifically because of its durability across sessions and because it
automatically configures the title for all users and all nodes across the
cluster.
The config file stores an enum string that will then be converted to a window
title and inserted in the index.html.tpl file on every request.
The current enum options are:
- default - Displays the default '$nodename - Proxmox Virtual Environment' string
if the config enum is not present
- 'node-and-cluster' - Displays the nodename and then the clustername in the
following style: '$nodename - $clustername - Proxmox Virtual Environment'
- 'fqdn' - Displays the current fqdn as returned by `PVE::Tools::get_fqdn()`
like so: '$fqdn - Proxmox Virtual Environment'
Possible future extensions
--------------------------
- If proper cross-node user settings are implemented in the future, they could
be used to allow users to define their own window title settings and have
these settings be persisted across sessions
- One of the selection options for window titles could be a user defined
template string which would allow users of PVE to define their own
window titles.
Changes since RFC
-----------------
- change of the `datacenter.cfg` setting title from "windowtitle" to
"window-title"
- renamed `nodeandcluster` to `node-and-cluster`
- added the " - Proxmox Virtual Environment" trailer to all titles
- removed the questions from this text and added the "Possible future
extensions" section
pve-manager:
Thomas Ellmenreich (1):
fix #5475: configurable window title
PVE/Service/pveproxy.pm | 21 +++++++++++++++++++++
www/index.html.tpl | 2 +-
www/manager6/Utils.js | 11 +++++++++++
www/manager6/dc/OptionView.js | 6 ++++++
4 files changed, 39 insertions(+), 1 deletion(-)
pve-cluster:
Thomas Ellmenreich (1):
fix #5475: configurable window title
src/PVE/DataCenterConfig.pm | 7 +++++++
1 file changed, 7 insertions(+)
Summary over all repositories:
5 files changed, 46 insertions(+), 1 deletions(-)
--
Generated by murpp 0.12.0
next reply other threads:[~2026-07-16 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 8:48 Thomas Ellmenreich [this message]
2026-07-16 8:48 ` [PATCH manager 1/2] fix #5475: configurable window title Thomas Ellmenreich
2026-07-16 8:48 ` [PATCH cluster 2/2] " Thomas Ellmenreich
2026-07-16 12:50 ` Thomas Lamprecht
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=20260716084807.77400-1-t.ellmenreich@proxmox.com \
--to=t.ellmenreich@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