starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add a "hostname" <meta> tag to the page header #10708

New Issue
Closed
opened 2025-12-29 21:35:03 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:35:03 +01:00
Owner
Copy Link

Originally created by @bctiemann on GitHub (Jan 28, 2025).

Originally assigned to: @bctiemann on GitHub.

NetBox version

v4.2.2

Feature type

Change to existing functionality

Proposed functionality

To aid in monitoring and troubleshooting, add a <meta> tag to the <head> of the base HTML page reflecting the value of settings.HOSTNAME, which was removed in NetBox v4.0.

<meta name="hostname" content="{{ settings.HOSTNAME }}" />

Use case

Internal monitoring of NetBox instances in the cloud use the hostname to verify ingress routing. It is not necessary to show the hostname visibly on the login page or other pages, but a <meta> tag that can be machine-read is a good solution.

Database changes

N/A

External dependencies

N/A

Originally created by @bctiemann on GitHub (Jan 28, 2025). Originally assigned to: @bctiemann on GitHub. ### NetBox version v4.2.2 ### Feature type Change to existing functionality ### Proposed functionality To aid in monitoring and troubleshooting, add a `<meta>` tag to the `<head>` of the base HTML page reflecting the value of `settings.HOSTNAME`, which was removed in NetBox v4.0. ` <meta name="hostname" content="{{ settings.HOSTNAME }}" />` ### Use case Internal monitoring of NetBox instances in the cloud use the hostname to verify ingress routing. It is not necessary to show the hostname visibly on the login page or other pages, but a `<meta>` tag that can be machine-read is a good solution. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:35:03 +01:00
adam closed this issue 2025-12-29 21:35:03 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: low status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10708
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?