Just wondering if there could be an option during Docker installation of the CMS to mount all of the CMS files locally, rather than within docker?
90% of people probably won’t need this (therefore being be an option), but it would certainly be useful when testing with developer builds etc as it allows easy access to the files and patching rather than going through Docker shell.
The xibo-cms repository contains a docker-compose.yml file which can be used to do this, although you need to install manually, as you did with the Vagrantfile of the past.
Mapping the internal content in releases breaks the concept of containerisation, exactly because the user can then change the environment by patching files, etc.
I’d imagine we will need to speed up release cycles once the move to Docker is complete, simply because patching becomes much harder.