Return composer type

[luckyraul]

No description provided.

[mobilizer]

I would suggest to not include "magento-module", so it is NOT copied to .modman/ and left outside of Magento root. Personally I prefer it in vendor directory, because there is no need for Magmi to be in Magento root.

Maybe some other change, that is related to these potential changes in composer.json: Add symlink to the Magmi cli interface to bin. #414

[luckyraul]

In my opinion not all users want to have cli only

[mobilizer]

@luckyraul Yes, of course. Magmi web interface is needed and great for setup and test.

Currently you need to point the webserver to the magmi web/ folder separately. E.g. on a subdomain.

(My concerns: Personally I also don't feel good with the htauth authentication used in Magmi right now. This is open for brute force attacks. (Unless I am missing any method implemented against it?)

[luckyraul]

At least you have an ability to disable deploy rather then not to have any change of auto-deploy.

[coredevel]

+1 for this, it's down to developer/devops to decide whether or not to include in the project's composer file for production release, for example we have dev, integration, staging, production and production-private where composer json's differ for each env.