You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The deploy manager only gets called after every module is successfully installed / updated.
So if the composer process breaks at some point, every module that has been processed till then won't get deployed after continuing the routine.
For example composer.json contains three modules and you're about to install them:
Module 1 gets processed
Module 2 gets processed and for whatever reason breaks the install process
After fixing the issue you continue installing and module 2 gets installed and module 3 gets instalelled fine, but the deploy mechanism isn't called for the first module, because it has been processed earlier (without reaching the deploy manager)
So it would come in handy to process every module on its own.
Download, install / deploy = done - next one ..
The text was updated successfully, but these errors were encountered:
The deploy manager only gets called after every module is successfully installed / updated.
So if the composer process breaks at some point, every module that has been processed till then won't get deployed after continuing the routine.
For example
composer.json
contains three modules and you're about to install them:After fixing the issue you continue installing and module 2 gets installed and module 3 gets instalelled fine, but the deploy mechanism isn't called for the first module, because it has been processed earlier (without reaching the deploy manager)
So it would come in handy to process every module on its own.
Download, install / deploy = done - next one ..
The text was updated successfully, but these errors were encountered: