4 ms·
> For instance, themes and plugins for Wordpress, Magento, etc. are often de facto installed by their mere presence at conventional locations inside the projec
by Navarr 12y ago
> For instance, themes and plugins for Wordpress, Magento, etc. are often de facto installed by their mere presence at conventional locations inside the project tree, and this is the only way to “install” them.
> In such a situation, going with submodules (or subtrees) probably is the right solution
As a Magento Developer, I'm afraid submodules wouldn't work for Magento plugins. As they unfortunately have to be installed to multiple top-level project directories. It is a nightmare (and is better served by the composer efforts for dependency management).
- tokenizerrr 12y agoThe last time I worked on Magento, and it has been a while, we would install the dependency in a single directory, and then you'd run a tool over it to "install" it into the proper locations. Sadly I cannot remember the name of this tool, but from memory it seems you could combine that with submodules? We used this so we could track an entire extension's source code in Git, and move them around easily. edit: I was thinking of modman
- icebraining 12y agoCan't you use symlinks?