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

Move user-managed assets to own subdirectory tree #5161

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

Originally created by @candlerb on GitHub (Aug 9, 2021).

NetBox version

v2.11.10 and v3.0-beta1

Feature type

Change to existing functionality

Proposed functionality

(Moved from #6916)

Currently the /opt/netbox/netbox directory contains a mix of user data/state (media, reports, scripts) and actual Netbox source code (e.g. circuits, dcim, virtualization etc)

I propose that that user files are moved under their own directory tree, perhaps /opt/netbox/data or /var/lib/netbox. In the latter case this would give:

  • /var/lib/netbox/media
  • /var/lib/netbox/reports
  • /var/lib/netbox/scripts

There are already configuration settings MEDIA_ROOT, REPORTS_ROOT, SCRIPTS_ROOT so this could just be a case of changing how the defaults are calculated.

Use case

To make it more straightforward to backup/restore all external (non-database) state, transfer to another Netbox instance, share between frontends via NFS etc.

To allow Netbox to add further state directories in future, without having to change the backup/restore process.

Database changes

None

External dependencies

None

Originally created by @candlerb on GitHub (Aug 9, 2021). ### NetBox version v2.11.10 and v3.0-beta1 ### Feature type Change to existing functionality ### Proposed functionality (Moved from #6916) Currently the `/opt/netbox/netbox` directory contains a mix of user data/state (`media`, `reports`, `scripts`) and actual Netbox source code (e.g. `circuits`, `dcim`, `virtualization` etc) I propose that that user files are moved under their own directory tree, perhaps `/opt/netbox/data` or `/var/lib/netbox`. In the latter case this would give: * `/var/lib/netbox/media` * `/var/lib/netbox/reports` * `/var/lib/netbox/scripts` There are already configuration settings `MEDIA_ROOT`, `REPORTS_ROOT`, `SCRIPTS_ROOT` so this could just be a case of changing how the defaults are calculated. ### Use case To make it more straightforward to backup/restore all external (non-database) state, transfer to another Netbox instance, share between frontends via NFS etc. To allow Netbox to add further state directories in future, without having to change the backup/restore process. ### Database changes None ### External dependencies None
adam added the type: featurepending closure labels 2025-12-29 19:24:56 +01:00
adam closed this issue 2025-12-29 19:24:56 +01:00
adam commented 2025-12-29 19:24:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 9, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 9, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:24:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 8, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Nov 8, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#5161
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?