installer-build-prod

[turtle0x1]

Hey cool library,

Unless im missing something, would you accept a PR to support an installer-build-prod option to overwrite the values in installer-build ?

I think I would need to modify here ?

composer-custom-directory-installer/src/Composer/CustomDirectoryInstaller/PackageUtils.php

Line 29 in 1ccaf2d

if(!empty($extra['installer-paths'])) {

[mnsami]

@turtle0x1 can you elaborate ? what is wrong with using the installer-paths ?

[turtle0x1]

I want different paths between dev & prod ?

[mnsami]

why don't you use require-dev ? @turtle0x1 , isn't it the purpose of it in first place?

but anyways, you can just use the same mechanism but with different folder name

[turtle0x1]

For example:

I have project X which is made up of 3 components (A, B & C)

A, B & C are hard dependencies (not dev dependencies) but often I want to develop project X and all three components at one one time

X, A, B & C each need to be in there own "git directory" so I can pull, commit & push indivually, and in project X i can use any changes made to A, B & C without having to commit & push them (and then update satis)

But when it comes to production it no longer benefits me to have A, B, C to be installed in /some/random/directory over application_dir/vendor