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

Rename: netbox/netbox to netbox/config #1212

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

Originally created by @ghost on GitHub (Sep 6, 2017).

Issue type

[X ] Request for Change

Description

Rename the netbox folder to config to avoid doubling in names and confusion when trying to get to the configuration-folder. Since it contains all config-files, this is the appropriate name for it.

so it's:

netbox/config/configuration.docker.py
netbox/config/configuration.example.py

instead of

netbox/netbox/configuration.docker.py
netbox/netbox/configuration.example.py

This may break something within an update but yould be fixed with an ln -s as a shortcut.

using config as the name makes this better for human reading.

Originally created by @ghost on GitHub (Sep 6, 2017). ### Issue type [X ] Request for Change ### Description Rename the netbox folder to config to avoid doubling in names and confusion when trying to get to the configuration-folder. Since it contains all config-files, this is the appropriate name for it. so it's: netbox/config/configuration.docker.py netbox/config/configuration.example.py instead of netbox/netbox/configuration.docker.py netbox/netbox/configuration.example.py This may break something within an update but yould be fixed with an ln -s as a shortcut. using config as the name makes this better for human reading.
adam closed this issue 2025-12-29 16:30:04 +01:00
adam commented 2025-12-29 16:30:05 +01:00
Author
Owner
Copy Link

@Zorlin commented on GitHub (Sep 6, 2017):

This makes a lot of sense. +1.

@Zorlin commented on GitHub (Sep 6, 2017): This makes a lot of sense. +1.
adam commented 2025-12-29 16:30:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 11, 2017):

This is a convention of the Django framework and AFAIK cannot be easily changed. Besides, this directory does not merely hold configuration data: it also holds some core views and other bits. And changing it would unnecessarily complicate all existing installations.

@jeremystretch commented on GitHub (Sep 11, 2017): This is a convention of the [Django framework](https://docs.djangoproject.com/en/1.11/intro/tutorial01/#creating-a-project) and AFAIK cannot be easily changed. Besides, this directory does not merely hold configuration data: it also holds some core views and other bits. And changing it would unnecessarily complicate all existing installations.
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
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#1212
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?