mirror of
https://github.com/netbox-community/netbox.git
synced 2025-07-22 20:12:00 -06:00
Updated Frequently Asked Questions (markdown)
parent
06866e5a87
commit
6b39691167
@ -71,7 +71,7 @@ However, if you encounter a new commercially-available interface type that has n
|
||||
|
||||
NetBox supports the attachment of images to certain models, namely sites, racks, and devices. This feature was added as a convenience to provide readily-accessible photographic documentation of installations. For instance, a data center technician might opt to upload a close-up photo of a device and its connections to clarify where each named interface resides on the box.
|
||||
|
||||
While NetBox might seem like an ideal place to store additional documents (PDFs, configurations, etc.), these are best maintained with the rest of your network's static documentation in a dedicated file store with appropriate access controls and revision history. Although other files cannot be uploaded to NetBox, you can link to them from NetBox in the comments section of an object, or within a custom URL field. Feature request [#969](https://github.com/digitalocean/netbox/issues/969) (currently a work in progress) will make this approach easier by introducing support for templatized URLs to external resources.
|
||||
While NetBox might seem like an ideal place to store additional documents (PDFs, configurations, etc.), these are best maintained with the rest of your network's static documentation in a dedicated file store with appropriate access controls and revision history. Although other files cannot be uploaded to NetBox, you can link to them from NetBox in the comments section of an object, with custom links or within a custom URL field.
|
||||
|
||||
# Why Aren't Device Type Component Modifications Retroactive?
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user