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

Add umask 022 to install.sh script #11856

New Issue
Closed
opened 2025-12-29 21:50:45 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:50:45 +01:00
Owner
Copy Link

Originally created by @robduffy2010 on GitHub (Nov 20, 2025).

NetBox version

v4.4.6

Feature type

Other

Proposed functionality

When running the install.sh script on hardened servers, which typically use umask 027, the install.sh script creates files with the wrong permissions, preventing Netbox from starting. To ensure that Netbox installs correctly across different environments and to harmonize installations, it would be helpful to add umask 022 to the start of the install.sh script.

While not strictly necessary from what I can tell, it would also be helpful to add Umask=022 to the netbox.service.

If accepted, I can submit a PR.

Use case

Harmonize the Netbox installation process across different environments. Of course, admins could troubleshoot the permissions issue but there's no reason not to have an installation script that works for everyone.

Database changes

No response

External dependencies

No response

Originally created by @robduffy2010 on GitHub (Nov 20, 2025). ### NetBox version v4.4.6 ### Feature type Other ### Proposed functionality When running the install.sh script on hardened servers, which typically use umask 027, the install.sh script creates files with the wrong permissions, preventing Netbox from starting. To ensure that Netbox installs correctly across different environments and to harmonize installations, it would be helpful to add umask 022 to the start of the install.sh script. While not strictly necessary from what I can tell, it would also be helpful to add Umask=022 to the netbox.service. If accepted, I can submit a PR. ### Use case Harmonize the Netbox installation process across different environments. Of course, admins could troubleshoot the permissions issue but there's no reason not to have an installation script that works for everyone. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetbox labels 2025-12-29 21:50:45 +01:00
adam closed this issue 2025-12-29 21:50:45 +01:00
adam commented 2025-12-29 21:50:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2025):

The installation script is meant to serve as a bare minimum tool for installing NetBox in the most common environments. We've resisted proposals to expand it to cover more complex scenarios (e.g. hardened) because they lead to creep in complexity and maintenance burden over time. While I appreciate your use case, unfortunately you'll need to make any changes to the installation script necessary to ensure compatibility with your specific environment.

@jeremystretch commented on GitHub (Nov 20, 2025): The installation script is meant to serve as a bare minimum tool for installing NetBox in the most common environments. We've resisted proposals to expand it to cover more complex scenarios (e.g. hardened) because they lead to creep in complexity and maintenance burden over time. While I appreciate your use case, unfortunately you'll need to make any changes to the installation script necessary to ensure compatibility with your specific environment.
adam commented 2025-12-29 21:50:47 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Nov 21, 2025):

@robduffy2010, something that dawned on me is that perhaps the netbox-community/customizations project might be a good place for this sort of more nuanced config to live and be maintained by the community.

@jnovinger commented on GitHub (Nov 21, 2025): @robduffy2010, something that dawned on me is that perhaps the [netbox-community/customizations](https://github.com/netbox-community/customizations) project might be a good place for this sort of more nuanced config to live and be maintained by the community.
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 netbox type: feature
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#11856
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?