You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can we specify another installer-path for custom modules, that reside in an external private repository, so that the module will get installed in a custom directory?
Haven't had a chance to try this yet but looks promising.I'd be happy to add something to one of the readme files. Any ideas where info like this should go?
The listed package types drupal-core,drupal-module, etc are all registered in https://github.com/composer/installers. This is what allows them to be mapped to specific installation paths.
I think that the example snippet you listed would actually map all packages to "sites/example.com/modules/{$name}" which would cause a lot of problems.
If you'd like to specify an install location for a custom module, you may be able to use https://github.com/mnsami/composer-custom-directory-installer. I haven't tried it myself, but I believe that you can create a composer.json in your custom module, define the type as composer, and then use this library to map the specific package to a specific directory.
How can we specify another installer-path for custom modules, that reside in an external private repository, so that the module will get installed in a custom directory?
Something like this would be helpful I think:
"docroot/modules/custom/{$name}": ["type:drupal-custom-modules"],
Update:
Doing some googling I found that you can do the following:
Haven't had a chance to try this yet but looks promising.I'd be happy to add something to one of the readme files. Any ideas where info like this should go?
source: https://getcomposer.org/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md
The text was updated successfully, but these errors were encountered: