Hi, am I able to somehow have two different sets of repositories based on some env?
I'm developing a modular app and I'm loading in different modules through Composer.
For development purposes I use local symlinked copies but for deployments I want to have VCS repositories for those. Changing the files back and forth is quite tedious so I was wondering if there is a way I can make it easier.
➜ ~/Sites/PhpProject3 php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');" PHP Warning: copy(https://getcomposer.org/installer): failed to open stream: Host is down in Command line code on line 1 Warning: copy(https://getcomposer.org/installer): failed to open stream: Host is down in Command line code on line 1
https://github.com/wapmorgan/MediaFilewith dependencies into one bundle? If so where I can read about it
requirestatement you used to add the dependency)
"create" : [ "@phinx create --template=MigrationTemplate.php.dist", "@unlock" ],
"create" : [ "@phinx create --template=MigrationTemplate.php.dist", "@unlock" ], "unlock" : "chmod -R 777 db/migrations && :",
jms/serializerthat uses annotations from doctrine. For the annotations to be workable it seems I am required to add
Doctrine\Common\Annotations\AnnotationRegistry::registerLoader('class_exists');at the start of my project. I'm thinking it'd be nice if I could somehow incorporate this into the generated
autoload.php-file, so that it's always called exactly once without me having to spell it out all over the place. Is this somehow possible?
curl -s https://getcomposer.org/installer | phpto install composer, and I now have tons of warnings about deprecation of package names which doesn't match a certain pattern. My question is: when the 2.0 will be available, will it be installed by my last command ? And is there any information about the 2.0 release, will it make the 1.X composer down, or will packagist still be working with older versions of composer ? It would be nice that there would be an installer for the 1.X and another installer for the 2.X . By doing this, projects deployed in CI/CD using this installer would not fetch by error the 2.X (which could crash if package names aren't valid)