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

Introduce a configuration parameter for signifying an offline or air-gapped deployment #10035

New Issue
Closed
opened 2025-12-29 21:26:02 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:26:02 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Aug 1, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.0.8

Feature type

New functionality

Proposed functionality

Introduce a new boolean configuration parameter, e.g. OFFLINE_DEPLOYMENT, which is false by default. This should be set to true is NetBox is installed on a system without Internet connectivity, which may be the case in certain high-security environments.

Use case

When this parameter is true, NetBox will omit any built-in external links, such as the footer links to GitHub and Slack. There are likely other instances of external references that may be addressed using this functionality.

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Aug 1, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.0.8 ### Feature type New functionality ### Proposed functionality Introduce a new boolean configuration parameter, e.g. `OFFLINE_DEPLOYMENT`, which is false by default. This should be set to true is NetBox is installed on a system without Internet connectivity, which may be the case in certain high-security environments. ### Use case When this parameter is true, NetBox will omit any built-in external links, such as the footer links to GitHub and Slack. There are likely other instances of external references that may be addressed using this functionality. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 21:26:02 +01:00
adam closed this issue 2025-12-29 21:26:02 +01:00
adam commented 2025-12-29 21:26:03 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Aug 1, 2024):

One thing that would be great to include is that if Netbox is deployed in a way that isn’t connected to the internet, have a configurable setting for Netbox to use to point to the requirements that are already in a local directory. Therefore, instead of trying to download requirements from the internet, it would use that location instead and NOT try to download from the internet.

@mr1716 commented on GitHub (Aug 1, 2024): One thing that would be great to include is that if Netbox is deployed in a way that isn’t connected to the internet, have a configurable setting for Netbox to use to point to the requirements that are already in a local directory. Therefore, instead of trying to download requirements from the internet, it would use that location instead and NOT try to download from the internet.
adam commented 2025-12-29 21:26:03 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Aug 1, 2024):

One thing that would be great to include is that if Netbox is deployed in a way that isn’t connected to the internet, have a configurable setting for Netbox to use to point to the requirements that are already in a local directory. Therefore, instead of trying to download requirements from the internet, it would use that location instead and NOT try to download from the internet.

This, to me, is specific to the way one manages their python venv and has nothing to do with NetBox itself.

@jsenecal commented on GitHub (Aug 1, 2024): > One thing that would be great to include is that if Netbox is deployed in a way that isn’t connected to the internet, have a configurable setting for Netbox to use to point to the requirements that are already in a local directory. Therefore, instead of trying to download requirements from the internet, it would use that location instead and NOT try to download from the internet. This, to me, is specific to the way one manages their python venv and has nothing to do with NetBox itself.
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 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#10035
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?