Magento Stack Exchange is a question and answer site for users of the Magento e-Commerce platform. It only takes a minute to sign up.
Sign up to join this community
Im developing an extension and would want to use some composer extensions in it. So I have a composer.json file in app/code/Vendor/Extension/ path.
Do I simply run composer update in the extension directory? This will put the vendor directory into the extension right? Is there a way I can have magento pick up the composer.json of my extension when I run a update from root?
Also most importantly what is the best practice in this?
There are two options here:
Described in the comments: create a package or a repository from your extension. If you don't want to push it to the world, you can create a Git repo locally. The repo should contain just your extension and composer.json in the root. Then link your extension's repository as a package to the Magento project in Magento's composer.json (see an example in https://getcomposer.org/doc/04-schema.md#repositories). Use "dev-xxx" version, where xxx is the branch name in your repo - then Composer will always be fetching the latest commit. Then, when you run composer update your package will be loaded with all its dependencies.
Leave file structure as is and duplicate all dependencies, autoload and any other deployment-specific information from your extension's composer.json you the Magento's root composer.json. Then when running composer update (in Magento root) all dependencies of your extension will be deployed.
composer create-project command. In this case your customer's project owns the root composer.json, so it's OK to modify it.
Jul 28, 2016 at 21:19
/path/to/magento/vendor? Any required package for your extension should be located into arequiredirective see getcomposer.org/doc/04-schema.md#require. When you will docomposer.phar updateinto magento root folder, the extension will be installed into the vendor folder and thanks to autoloader from composer, your own extension will get access to ithttps://github.com/diglin/Diglin_Username2then push it to github and submit your repo on packagist. After that you can trigger this command on magento to install your extension via composer into the vendor folder:composer.phar require namespace/modulename.namespace/modulename= name of the extension in composer.jsonhttps://github.com/composer/satisto create something similar to packagist but for your intern purpose. I didn't configured myself but it is possible to set access rights here getcomposer.org/doc/articles/…