Maintaining your Flow / Neos installation best practices for the use of composer, git and friends

Maintaining your Flow / Neos installation best practices for the use of composer, git and friends

With the introduction of Composer as dependency manager in TYPO3 Flow 2.0, the structure of a Flow-project has changed, most notably from using Git-submodules to manage packages, to letting Composer do that.

This leads to a number of questions: What is the best way to set up your SCM structure? How do you make sure that all team members has the same version of dependent libraries? When do you use your SCM or Composer to update packages? and probably a lot more.

This talk will take you through some of the pitfalls and best-practices of maintaining and cooperating on TYPO3 Flow projects

3cbf953e7a83c2405cfbfe952be9e265?s=128

christianjul

April 19, 2013
Tweet