I've recently (apparently without realising) been updated to Mopidy 3.0, which, as I now know, doesn't include the MPD frontend in the core anymore and apparently didn't pull it in as a dependency, so I was left trying to troubleshoot why my Mopidy server was suddenly not listening on port 6600 anymore.
A feature that would've been very helpful would be a warning of some kind if there is a section in the configuration that has no corresponding extension - for example: "configuration for missing extension mpd - do you need to install mopidy-mpd?" (with the latter part left out for any configuration section that doesn't match the well-known first-party extensions, or rewritten in a more generic way).
As of now, the only sign you get the mpd extensions is gone is that it disappears from the listed extensions and enabled frontends, and I feel like a warning like that would be very helpful for future troubleshooting.
I've recently (apparently without realising) been updated to Mopidy 3.0, which, as I now know, doesn't include the MPD frontend in the core anymore and apparently didn't pull it in as a dependency, so I was left trying to troubleshoot why my Mopidy server was suddenly not listening on port 6600 anymore.
A feature that would've been very helpful would be a warning of some kind if there is a section in the configuration that has no corresponding extension - for example: "configuration for missing extension mpd - do you need to install mopidy-mpd?" (with the latter part left out for any configuration section that doesn't match the well-known first-party extensions, or rewritten in a more generic way).
As of now, the only sign you get the mpd extensions is gone is that it disappears from the listed extensions and enabled frontends, and I feel like a warning like that would be very helpful for future troubleshooting.