View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000875 | XMB1 | New Features | public | 2025-12-24 07:58 | 2025-12-28 07:02 |
| Reporter | miqrogroove | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Target Version | 1.12.00 | ||||
| Summary | 0000875: Allow Relocation of config.php | ||||
| Description | For an extra layer of security, it needs to be possible to change the location of the config.php file without breaking everything. | ||||
| Additional Information | Many search results on this topic recommend placing the config file outside of the web root, or placing the passwords in environment variables. I don't think these options are particularly simple or efficient on their own. I would like to take a direction in which the config.php file simply contains an extra variable $configPath which optionally points to a secondary file. This allows XMB to look for overrides in a customized location with little to no performance impact. This also preserves the ability to upgrade the configuration in future versions, because the values aren't getting locked away in some other system resource or auto included file. | ||||
| Tags | No tags attached. | ||||
| MySQL Version | |||||
| PHP Version | |||||
| Web Server | |||||
| Browser | |||||
| Flags | |||||
| Original Reporter | |||||
| SVN Revision | |||||
| Git Commit | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-24 07:58 | miqrogroove | New Issue | |
| 2025-12-28 07:02 | miqrogroove | Additional Information Updated |