PHP Composer mixed with Git Submodules and Symfony2 -

I have a project here which is a big Symphony 2 app, I try to present git submodules for those components I am making a house here in the house. The point here is that each component requires a composer package to work properly for itself and now I have a compositor package for the symphony 2 app and composer package for the component and I am not dependent on these dependencies How To Setup >

At the moment, I'm manually running 'composer install' for each component (GIT subdue), which means that each component has its own 'vendor' folder, it is far from ideal, so I come to the stack How to get good advice about keeping this 'symphony composer dependencies' and 'component composer dependency' easy.

I do not have to make sure that versions of the dump of the symfony2 app are synchronized component duplicates, making it easy for me to setup it without running 'composer update' with every GIT subpule and Need to be maintained.

Thank you!

Edit

Now I am using the repository key of the compiler for a private gitbepage of its URL companies. I am able to pull in a single private repo, I call it Repo A. When I add a repo and repo a requirement repo be it does not solve it properly.

The following error message occurs:

key

findings

Package of Victorate / Database component is present as one of the properties defined in this context. The end solution was to use Satis to set up here, which is a personal edition of 'Packist' working with Packagalist.

I do the setup on 'Setup' and a 'repository' in my main app composer .json file now when the name of the package is evaluated, it will use your custom settings server To give you a GIT URL too.

I would say your best bet is to add those components through the composer, as Git is in opposition to submodules. It makes coding and maintenance a bit more complicated, but it ensures that your application is aware of all real dependencies.

If you do not want them to be public and have a simple way of handling them, then I will deploy a system locally and register them all there, which is your composer. Jason Caitis joins the repo.

Satis is a simple version of the package, as long as the server and machine that runs composer installs , reaches your personal repository, and they have some more There is a documentation on the Composer website here:

You will then setup packages.yourcompany.com and add it to your composer.json as an alternative source for the package. Everything is private.

The response to the edit: This is happening because it is compatible with the composer, which means that the "repository" is known only to the musician of your project. Johnson, repo There is no address in it, then it can not be found that you have to redefine the repository in that one even using "Satis" using all the composers to the "thirty seven" Should be included in the JSON files

In your app, the "repository" stuff was added to the repo A and B, it should all work out.