[SERVER-36150] Improved Default Config File Handling Created: 16/Jul/18 Updated: 22/Jul/19 Resolved: 22/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Lord (Inactive) | Assignee: | Mathew Robinson (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Dev Tools 2019-07-01, Dev Tools 2019-07-15 |
| Participants: |
| Description |
|
Today a command-line value for [-f|--config] must be passed to the mongod binary as there are no built-in default config files used. We minimize the pain today for Linux users within our packaging by specifying a default config file of /etc/mongod.conf in the sysvinit script / systemd unit file (e.g. Red Hat). AFAICT, we offer no such help on Windows or macOS – and those are the platforms where the users are most likely to need the help as:
The end result is a lower quality user experience which violates our otherwise great user story around easily getting MongoDB up and running. It would be great if we could improve this user experience by managing global default config file paths and a progression of overrides. For example:
As a competitive example, see MySQL. In the case of MySQL it's become far too complicated and convoluted–but we can find a nice middle ground. |