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

[PR #11742] [MERGED] Closes #11592: Expose FILE_UPLOAD_MAX_MEMORY_SIZE as a setting #13834

New Issue
Closed
opened 2025-12-29 23:21:04 +01:00 by adam · 0 comments
adam commented 2025-12-29 23:21:04 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/11742
Author: @aronjohanns
Created: 2/13/2023
Status: ✅ Merged
Merged: 2/16/2023
Merged by: @jeremystretch

Base: develop ← Head: 11592-expose-setting

📝 Commits (4)

  • 38611a3 Closes #11592: Expose FILE_UPLOAD_MAX_MEMOMORY_SIZE as a setting
  • a65440d Merge branch 'netbox-community:develop' into 11592-expose-setting
  • 4ac78e1 change configuration settings to alphabetic order
  • 8b80ddd Small example and documentation

📊 Changes

3 files changed (+13 additions, -0 deletions)

View changed files

📝 docs/configuration/miscellaneous.md (+8 -0)
📝 netbox/netbox/configuration_example.py (+4 -0)
📝 netbox/netbox/settings.py (+1 -0)

📄 Description

Fixes: #11592

Exposes FILE_UPLOAD_MAX_MEMORY_SIZE as a setting so that it can be changed in configuration.py.
This addresses an issue where file uploads fails if file size is greater than django default value. With these changes a user will be able to increase the max file upload size to fit there need. I tested this and can confirm that these changes fixes netbox docker issue 897 by allowing the user to increase the max size.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/11742 **Author:** [@aronjohanns](https://github.com/aronjohanns) **Created:** 2/13/2023 **Status:** ✅ Merged **Merged:** 2/16/2023 **Merged by:** [@jeremystretch](https://github.com/jeremystretch) **Base:** `develop` ← **Head:** `11592-expose-setting` --- ### 📝 Commits (4) - [`38611a3`](https://github.com/netbox-community/netbox/commit/38611a350596a804363c1bd86264eb39e9d5a380) Closes #11592: Expose FILE_UPLOAD_MAX_MEMOMORY_SIZE as a setting - [`a65440d`](https://github.com/netbox-community/netbox/commit/a65440d8f769f1feda68a5c2b2e95f92881bf2b4) Merge branch 'netbox-community:develop' into 11592-expose-setting - [`4ac78e1`](https://github.com/netbox-community/netbox/commit/4ac78e10cd333aedf1de255d52812b503088db9a) change configuration settings to alphabetic order - [`8b80ddd`](https://github.com/netbox-community/netbox/commit/8b80dddf724f49465db7eb3712dbd6b6e5e79dee) Small example and documentation ### 📊 Changes **3 files changed** (+13 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/configuration/miscellaneous.md` (+8 -0) 📝 `netbox/netbox/configuration_example.py` (+4 -0) 📝 `netbox/netbox/settings.py` (+1 -0) </details> ### 📄 Description <!-- Thank you for your interest in contributing to NetBox! Please note that our contribution policy requires that a feature request or bug report be approved and assigned prior to opening a pull request. This helps avoid waste time and effort on a proposed change that we might not be able to accept. IF YOUR PULL REQUEST DOES NOT REFERENCE AN ISSUE WHICH HAS BEEN ASSIGNED TO YOU, IT WILL BE CLOSED AUTOMATICALLY. Please specify your assigned issue number on the line below. --> ### Fixes: #11592 <!-- Please include a summary of the proposed changes below. --> Exposes FILE_UPLOAD_MAX_MEMORY_SIZE as a setting so that it can be changed in configuration.py. This addresses an issue where file uploads fails if file size is greater than django default value. With these changes a user will be able to increase the max file upload size to fit there need. I tested this and can confirm that these changes fixes [ netbox docker issue 897](https://github.com/netbox-community/netbox-docker/issues/897) by allowing the user to increase the max size. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 23:21:04 +01:00
adam closed this issue 2025-12-29 23:21:04 +01:00
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 pull-request
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#13834
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?