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

Netbox installation #6205

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

Originally created by @tazboyz16 on GitHub (Mar 13, 2022).

Change Type

Addition

Area

Installation instructions

Proposed Changes

With the package installations, git should be listed to ensure the upgrade script completes with no issues.
This is due to not all deploys include a "standard" packaging list like the proxmox ubuntu lxc containers

Originally created by @tazboyz16 on GitHub (Mar 13, 2022). ### Change Type Addition ### Area Installation instructions ### Proposed Changes With the package installations, git should be listed to ensure the upgrade script completes with no issues. This is due to not all deploys include a "standard" packaging list like the proxmox ubuntu lxc containers
adam added the type: documentation label 2025-12-29 19:38:01 +01:00
adam closed this issue 2025-12-29 19:38:01 +01:00
adam commented 2025-12-29 19:38:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 14, 2022):

Users are instructed to install git here, only if using it for the installation.

@jeremystretch commented on GitHub (Mar 14, 2022): Users are instructed to install git [here](https://netbox.readthedocs.io/en/stable/installation/3-netbox/#option-b-clone-the-git-repository), only if using it for the installation.
adam commented 2025-12-29 19:38:02 +01:00
Author
Owner
Copy Link

@tazboyz16 commented on GitHub (Mar 16, 2022):

I didnt do the git clone option, I went with the release installation. Redirecting this to option B is misplaced if option A results on requiring this package due your upgrade script process required to pull a git repo for a module or update.

Would it not be proactive to include the git package in the installation packages prior to the option A\B choice?

@tazboyz16 commented on GitHub (Mar 16, 2022): I didnt do the git clone option, I went with the release installation. Redirecting this to option B is misplaced if option A results on requiring this package due your upgrade script process required to pull a git repo for a module or update. Would it not be proactive to include the git package in the installation packages prior to the option A\B choice?
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 type: documentation
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#6205
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?