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

split install script to permit automated installation #11873

New Issue
Closed
opened 2025-12-29 21:51:04 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:51:04 +01:00
Owner
Copy Link

Originally created by @erempel on GitHub (Nov 26, 2025).

NetBox version

v4.4.7

Feature type

Change to existing functionality

Proposed functionality

I have opened a discussion but there does not seem to be much interest there ;-)
https://github.com/netbox-community/netbox/discussions/20801

The install script (upgrade.sh) does more than just install the product. I would like that script to be split into two. One that does the install, and the other that does all of the other steps. This will separate the steps needed to be run with administrative privileges and those that only require a runtime user.

Use case

This change would allow me to use the install portion of the script to create a complete installation, without any configuration. At our site we build the install artifact on a host that has internet connectivity and then we deploy that artifact to or production hosts that do not have access to the internet.
After the install, configuration and the second script can be performed by an unprivileged user.

Database changes

none

External dependencies

none

Originally created by @erempel on GitHub (Nov 26, 2025). ### NetBox version v4.4.7 ### Feature type Change to existing functionality ### Proposed functionality I have opened a discussion but there does not seem to be much interest there ;-) https://github.com/netbox-community/netbox/discussions/20801 The install script (upgrade.sh) does more than just install the product. I would like that script to be split into two. One that does the install, and the other that does all of the other steps. This will separate the steps needed to be run with administrative privileges and those that only require a runtime user. ### Use case This change would allow me to use the install portion of the script to create a complete installation, without any configuration. At our site we build the install artifact on a host that has internet connectivity and then we deploy that artifact to or production hosts that do not have access to the internet. After the install, configuration and the second script can be performed by an unprivileged user. ### Database changes none ### External dependencies none
adam added the type: featurenetbox labels 2025-12-29 21:51:04 +01:00
adam closed this issue 2025-12-29 21:51:04 +01:00
adam commented 2025-12-29 21:51:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 4, 2025):

Thanks for the suggestion, but we long ago made the decision to intentionally limit the functionality of the installation tooling we ship with NetBox. This is because we want to focus on building the application itself, and not on supporting the myriad environments in which it might potentially be installed. The installation script included with NetBox is intended to serve as a minimal reference: For anything more complex, you'll need to devise your own tooling.

@jeremystretch commented on GitHub (Dec 4, 2025): Thanks for the suggestion, but we long ago made the decision to intentionally limit the functionality of the installation tooling we ship with NetBox. This is because we want to focus on building the application itself, and not on supporting the myriad environments in which it might potentially be installed. The installation script included with NetBox is intended to serve as a minimal reference: For anything more complex, you'll need to devise your own tooling.
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 netbox 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#11873
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?