mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2057] Can't track config files with git #1483
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1483
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @jsimonrichard on GitHub (May 16, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2057
Is your feature request related to a problem? Please describe.
I'd like to keep track of the NPM config files using git, but when those config files are generated they're owned by root. This makes it impossible to get track of them without using
sudoall the time.Describe the solution you'd like
It would be nice to have an option to specify the user used to create those config files. For example, https://vsupalov.com/docker-shared-permissions/ uses the flag
--user "$(id -u):$(id -g)"with thedocker runcommand.Describe alternatives you've considered
I'm not sure if this is a great solution, though. If there's a way to force git to accept files owned by root, that would probably be better, but I haven't figured out a way to do it yet.
@github-actions[bot] commented on GitHub (Feb 16, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 2, 2025):
Issue was closed due to inactivity.