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

Store PDF files linked to Circuits (Acceptance Certificates) #833

New Issue
Closed
opened 2025-12-29 16:26:10 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:26:10 +01:00
Owner
Copy Link

Originally created by @InsaneSplash on GitHub (Apr 5, 2017).

Would it be a consideration to include the ability to attach PDF files to a Circuit. It would be really helpful to allow one to attach the acceptance certificate for a circuit and have reference to it within the same environment.

The files can be uploaded and stored on disk, and only a link to the file stored in the DB and there is no real need to store the files in the DB for indexing etc.

Agreed that one could include a file share link to a file server, but to keep all relevant information stored in one location, it would make sense that it could be opened within the browser at the point of reviewing a circuit.

This might have some reference to issue #182

Originally created by @InsaneSplash on GitHub (Apr 5, 2017). Would it be a consideration to include the ability to attach PDF files to a Circuit. It would be really helpful to allow one to attach the acceptance certificate for a circuit and have reference to it within the same environment. The files can be uploaded and stored on disk, and only a link to the file stored in the DB and there is no real need to store the files in the DB for indexing etc. Agreed that one could include a file share link to a file server, but to keep all relevant information stored in one location, it would make sense that it could be opened within the browser at the point of reviewing a circuit. This might have some reference to issue #182
adam closed this issue 2025-12-29 16:26:10 +01:00
adam commented 2025-12-29 16:26:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 5, 2017):

I don't believe NetBox should act as a file store. An argument could be made to support file attachments for any of the primary models in NetBox, but that's not its purpose. #152 works because there's a lot of value in serving image media directly from NetBox, but there are much more suitable tools for storing miscellaneous attachments.

Alternatively, I suggest creating a custom URL field on the circuit model pointing to the document hosted elsewhere.

@jeremystretch commented on GitHub (Apr 5, 2017): I don't believe NetBox should act as a file store. An argument could be made to support file attachments for any of the primary models in NetBox, but that's not its purpose. #152 works because there's a lot of value in serving image media directly from NetBox, but there are much more suitable tools for storing miscellaneous attachments. Alternatively, I suggest creating a custom URL field on the circuit model pointing to the document hosted elsewhere.
adam commented 2025-12-29 16:26:11 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Apr 5, 2017):

OK, would it be possible then to allow the creation of a custom field URL, but display a name and not the URL itself?
Sometimes these things (URLS) can get really long, and all that is required is a name to click on.

@InsaneSplash commented on GitHub (Apr 5, 2017): OK, would it be possible then to allow the creation of a custom field URL, but display a name and not the URL itself? Sometimes these things (URLS) can get really long, and all that is required is a name to click on.
adam commented 2025-12-29 16:26:11 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Apr 5, 2017):

@InsaneSplash Probably related to #969

@lampwins commented on GitHub (Apr 5, 2017): @InsaneSplash Probably related to #969
adam commented 2025-12-29 16:26:12 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Apr 5, 2017):

Yeah that would be a big help if we are required to use external URLs to reference related data. I could write a separate tool to upload the pdf file, and then using the custom URL could map it to the file on the webserver. The only requirement would be to be able to apply a custom URL for all circuits with a variable of the circuit. Having to type in the URL for each circuit would defeat the purpose since it would add additional overhead that could be scripted.

@InsaneSplash commented on GitHub (Apr 5, 2017): Yeah that would be a big help if we are required to use external URLs to reference related data. I could write a separate tool to upload the pdf file, and then using the custom URL could map it to the file on the webserver. The only requirement would be to be able to apply a **custom URL for *all* circuits** with a variable of the circuit. Having to type in the URL for each circuit would defeat the purpose since it would add additional overhead that could be scripted.
adam commented 2025-12-29 16:26:12 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Apr 10, 2017):

Perhaps a compromise could be dropbox/g-drive integration so one could easily link documents stored in "the cloud" ... API for these are quite robust and public ... if implemented in a such a manner, perhaps EU's could write integrations for other platforms as they see fit?

Just spit balling

@bellwood commented on GitHub (Apr 10, 2017): Perhaps a compromise could be dropbox/g-drive integration so one could *easily* link documents stored in "the cloud" ... API for these are quite robust and public ... if implemented in a such a manner, perhaps EU's could write integrations for other platforms as they see fit? Just spit balling
adam commented 2025-12-29 16:26:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 2, 2017):

Seems like #969 could work for this. Closing this one out.

@jeremystretch commented on GitHub (May 2, 2017): Seems like #969 could work for this. Closing this one out.
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#833
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?