Is your feature request related to a problem? Please describe.
Currently, the login page has hardcoded branding (the inline SVG logo and the "MeshMonitor" title) in src/components/LoginPage.tsx (around lines 119-140). Users who deploy MeshMonitor as a centralized dashboard for specific communities or organizations cannot easily customize this login screen. Right now, the only workaround is to fork the repository, modify the code directly, and rebuild the Docker image locally. This breaks the convenience of using the official pre-built Docker images and makes future updates much harder.
Describe the solution you'd like
It would be incredibly helpful to have native support for custom branding via environment variables in the .env file. For example:
CUSTOM_TITLE="My Organization Base"CUSTOM_LOGO_URL="https://example.com/logo.png"
The LoginPage.tsx could then be updated to conditionally render these custom assets if the variables are present, or gracefully fallback to the default MeshMonitor SVG and title if they are left blank.
Describe alternatives you've considered
Forking and Rebuilding: Cloning the repo, replacing the SVG and <h1> tag manually, and running a local docker build. This is currently what I have to do, but it makes auto-upgrading impossible.
Additional context
I recently discussed this in the Discord channel, and NodeZero confirmed that this branding is currently hardcoded and suggested I open this feature request. Adding this small flexibility would be a massive game-changer for many node operators deploying MeshMonitor for local communities or institutional networks!
Is your feature request related to a problem? Please describe.
Currently, the login page has hardcoded branding (the inline SVG logo and the "MeshMonitor" title) in
src/components/LoginPage.tsx(around lines 119-140). Users who deploy MeshMonitor as a centralized dashboard for specific communities or organizations cannot easily customize this login screen. Right now, the only workaround is to fork the repository, modify the code directly, and rebuild the Docker image locally. This breaks the convenience of using the official pre-built Docker images and makes future updates much harder.Describe the solution you'd like
It would be incredibly helpful to have native support for custom branding via environment variables in the
.envfile. For example:CUSTOM_TITLE="My Organization Base"CUSTOM_LOGO_URL="https://example.com/logo.png"The
LoginPage.tsxcould then be updated to conditionally render these custom assets if the variables are present, or gracefully fallback to the default MeshMonitor SVG and title if they are left blank.Describe alternatives you've considered
Forking and Rebuilding: Cloning the repo, replacing the SVG and
<h1>tag manually, and running a localdocker build. This is currently what I have to do, but it makes auto-upgrading impossible.Additional context
I recently discussed this in the Discord channel, and
NodeZeroconfirmed that this branding is currently hardcoded and suggested I open this feature request. Adding this small flexibility would be a massive game-changer for many node operators deploying MeshMonitor for local communities or institutional networks!