Is the composer an updated atom?

Story: can I run composer updateon a running site without worrying about which dependencies are updated first?

A longer story. I am trying to find out if the actual update process is atomic by the composer.

Are dependencies updated / activated immediately when everything is downloaded and OK is checked, or is each of them updated immediately after it is downloaded? What if one update fails in the middle?

Cannot find documents about this, so I hope someone can help! If this is documented, I would be pleased with the link.

+5
source share
2 answers

No, it is not.

Even for the linker, setting for each dependency update is:

  • ( )
  • ( )

(, - github), .

( , , )

, . * / .

, / . :  -  - PHP , , , undefined.

-.

2 - ( , )

- , , -, . - .

, , . .

3 - (, )

- , .

:  - -,  - , (< 200ms)  - (< 10ms)  -

~ 200 , .

: https://serverfault.com/questions/654780/how-to-suspend-nginx-requests-during-backend-upgrades. , .

+2

, , , - , . .

:

composer update --dry-run

composer update . , .

+2

All Articles