On another thought… DietPi decides what runs on which port. That will probably match defaults, with exceptions as this in some cases. Is there an easy way to manage (inside dietpi) what runs on which port? I could image having something like dietpi-ports where you can co trol what runs on which port, using cli flags for underlying commands so that app-local config is indeed ignored. But instead embrace the fact that Dietpi is in control of software installed through dietpi-software and ensure it behaves as documented, or let users manage it on their own.