https://github.com/backdrop/backdrop-issues/issues/1238#issuecomment-141...
When the module is enabled backdrop would check that there is no naming issues, warn of any path issues and copy these files into the sites config folder.
I think this would be a good idea in any case. We shouldn't allow modules to be enabled at all if they have conflicting config file names with any existing config.
GitHub Issue #:
1242
Recent comments
I recently ran into the same error: Exception: The configuration directory in settings.php is specified as 'files/config_[some-random-CMI-ID-here]/active', but this...
Live deployment Configuration Directory error
https://github.com/shabib-m/tailwindcss/wiki
Free Backdrop Theme built on Tailwind CSS v3 (Based on Basis) - Seeking Feedback & Ideas!
Admin Edit - note the image above is a link to the YouTube video.
Free Backdrop Theme built on Tailwind CSS v3 (Based on Basis) - Seeking Feedback & Ideas!