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

Clarify "Replicating NetBox" section "Cache Invalidation" #4236

New Issue
Closed
opened 2025-12-29 18:34:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:34:10 +01:00
Owner
Copy Link

Originally created by @cs-1 on GitHub (Nov 2, 2020).

Originally assigned to: @jeremystretch on GitHub.

Change Type

[X] Addition
[X] Correction
[ ] Deprecation
[ ] Cleanup (formatting, typos, etc.)

Area

[ ] Installation instructions
[ ] Configuration parameters
[ ] Functionality/features
[ ] REST API
[X] Administration/development
[ ] Other

Proposed Changes

We use a staging server to test changes to NetBox and thus replicate our production server regularly using an Ansible playbook. While implementing the replication I realised that the section "Cache Invalidation" of "Replicating NetBox" needs two changes:

  • It's not entirely clear from the documentation whether to run python3 manage.py invalidate all on the source machine or the destination machine if you're unfamiliar with the internals of NetBox. This should should be explained in this section.
  • The command python3 manage.py invalidate all doesn't work without prior issuing source /opt/netbox/venv/bin/activate. This should be corrected.
Originally created by @cs-1 on GitHub (Nov 2, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. Please indicate the nature of the change by placing an X in one of the boxes below. --> ### Change Type [X] Addition [X] Correction [ ] Deprecation [ ] Cleanup (formatting, typos, etc.) ### Area [ ] Installation instructions [ ] Configuration parameters [ ] Functionality/features [ ] REST API [X] Administration/development [ ] Other <!-- Describe the proposed change(s). --> ### Proposed Changes We use a staging server to test changes to NetBox and thus replicate our production server regularly using an Ansible playbook. While implementing the replication I realised that the section "Cache Invalidation" of "Replicating NetBox" needs two changes: - It's not entirely clear from the documentation whether to run `python3 manage.py invalidate all` on the source machine or the destination machine if you're unfamiliar with the internals of NetBox. This should should be explained in this section. - The command `python3 manage.py invalidate all` doesn't work without prior issuing `source /opt/netbox/venv/bin/activate`. This should be corrected.
adam added the status: acceptedtype: documentation labels 2025-12-29 18:34:10 +01:00
adam closed this issue 2025-12-29 18:34:10 +01:00
adam commented 2025-12-29 18:34:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 5, 2020):

Fixed in b39019ce

@jeremystretch commented on GitHub (Nov 5, 2020): Fixed in b39019ce
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: 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#4236
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?