0
Detect unintentional multiple `*.config.php` files to catch weird config problems
Source: nextcloud/server#46665 · opened by @joshtrichards
Detect unintentional multiple *.config.php files to catch weird config problems : Sometimes an administrator makes a manual backup of their existing config before making an adjustment. If they name it {anything}.config.php this results in them unintentionally having overlapping config files. And it also means the backup takes precedence. This creates all sorts of unexpected behaviors that can be difficult to isolate (and may give the appearance of bugs)[^exhibitA].
No pledges yet. Be the first to back this.
Comments
Similar requests
[RFC / Feature Proposal] Relaxing Strict PHP Upper-Bound Enforcement into Configurable Soft Warnings for Emergency Security Mitigations (e.g., `php2shell`)
1 vote · 0 comments
Optimal approach to managing the value of `interned_strings_buffer`
0 votes · 0 comments
Try to detect when mismatched SAPI versions (i.e. CLI versus web-side) are in-use
0 votes · 0 comments
Export Bluesky, Fediverse, and IMPP to system contacts
0 votes · 0 comments
Setup check to identify unrecognized `config.php` entries
0 votes · 0 comments
No comments yet.