Allowing custom modules to be added while in local dev environment#5
Allowing custom modules to be added while in local dev environment#5ivangrynenko wants to merge 1 commit intogovCMS:masterfrom
Conversation
|
This would be great. Personally I'm putting modules at I think the location should be such that a module can override a contrib module. For example, we have been doing bug-fixes on field_group module, and we need to have a custom version that overrides the one in govcms. The order-of-discovery is described here, and please note that there is no reliable order of precendence between |
|
If you're in local dev, you can set these volumes in docker-compose.override.yml thus: |
|
Oh, well that pretty much solves it. Except I notice my gitignore doesn't include |
|
you can commit the docker-compose.override if you want some permanency - it'll not run in Lagoon, just locally |
|
But it will run in Gitlab.... so i think you can't commit it? |
While working on GovCMS 8 in my local, I need some custom modules - primarily for development reasons.
For example, devel and devel_generate help me to work on features requiring some content, I can generate content, terms, users easily.
At the moment GovCMS8 has no way of adding those modules.
This PR introduces a directory /modules/ along with a docker-compose mountable volume. Any module that I place into /modules/ directory locally available for my development.
This PR should be considered from the point of Lagoon deployment and is likely requires a custom task of removing either the /modules/* directories from the build artifact or altering the docker-compose.yml, removing the volume definition.