Feature Request: Customizable Instance Name / Page Title

Problem

When managing multiple Nginx Proxy Manager instances simultaneously (e.g., production, staging, home lab), all instances share the same browser tab title "Nginx Proxy Manager". This makes it difficult to distinguish between tabs at a glance, increasing the risk of accidentally applying changes to the wrong instance.

Proposed Solution

Add an Instance Name setting in the Admin UI (under Settings), which would:

• Replace or append to the browser <title> tag (e.g., "Nginx Proxy Manager - Production")
• Optionally display the instance name in the navigation bar or header
• Be configurable via both the UI and an environment variable (e.g., INSTANCE_NAME) for Docker-first workflows

Example environment variable usage:

environment:
  INSTANCE_NAME: "Production"

Example resulting title:

Nginx Proxy Manager - Production

Use Case

Users managing 2+ NPM instances open in separate browser tabs have no visual way to tell them apart without hovering over each tab or reading the URL. A simple customizable name solves this immediately.

Alternatives Considered

• Manually patching frontend files inside the container — breaks on every update
• Using a reverse proxy with sub_filter — adds unnecessary infrastructure complexity
• Browser userscripts (Tampermonkey) — requires per-user setup, not a proper solution

Additional Context

This is a commonly requested quality-of-life improvement for homelab and production users running multiple NPM instances. Similar tools like Portainer and Grafana already support custom instance naming.

Start by locating the Admin UI Settings implementation and the existing environment-variable configuration path. Confirm how a setting can be stored and exposed to the frontend, then define the title and optional navigation display behavior. Done means an instance name can be configured through the UI or INSTANCE_NAME and distinguishes browser tabs reliably.