Download as PDF, PPTX
![Add custom repositories With composer.json: "require": { "fago/example": "1.*" } "repositories": [ { "type": "vcs", "url": "http://github.com/fago/example" } ]](https://image.slidesharecdn.com/efficientdevelopmentworkflowswithcomposer-161126160018/75/Efficient-development-workflows-with-composer-32-2048.jpg)
![Custom repositories Without composer.json: "repositories": [{ "type": "package", "package": { "name": "fago/example", "version": "0.1.0", "source": { "url": "github.com/fago/example", "type": "git", "reference": "0.1.0" } } }]](https://image.slidesharecdn.com/efficientdevelopmentworkflowswithcomposer-161126160018/75/Efficient-development-workflows-with-composer-35-2048.jpg)
![Adding in your fork "require": { "samson/yt": "devBRANCH as 2.0.0" }, "repositories": [ { "type": "vcs", "url": "https://github.com/fago/yt" } ],](https://image.slidesharecdn.com/efficientdevelopmentworkflowswithcomposer-161126160018/75/Efficient-development-workflows-with-composer-38-2048.jpg)
!["repositories": [ { "type": "composer", "url": "https://satis.example.com" } ],](https://image.slidesharecdn.com/efficientdevelopmentworkflowswithcomposer-161126160018/75/Efficient-development-workflows-with-composer-58-2048.jpg)
![Project configuration "repositories": [{ "type": "composer", "url": "https://assetpackagist.org" }], "require": { "oomphinc/composerinstallersextender": "*", }, "extra": { "installertypes": ["library"], "installerpaths": { "web/libraries/{$name}/": ["vendor:bower asset", "vendor:npmasset"] } }](https://image.slidesharecdn.com/efficientdevelopmentworkflowswithcomposer-161126160018/75/Efficient-development-workflows-with-composer-63-2048.jpg)
Efficient development workflows with composer
- 1.
- 2. About me ● WolfgangZiegler ● drupal.org/u/fago ● @the_real_fago at twitter
- 3. Wolfgang Ziegler //fago ● More than 10 years of Drupal experience ● Leading force behind the Drupal 8 Entity Field API improvements Maintainer of Typed Data API ● Creator of Rules, Field Collection, Profile2
- 4.
- 5.
- 6. What is it? ●Dependency manager for PHP ● Use and publish packages ● Package-metadata: composer.json ● Repository: packagist.org
- 7.
- 8.
- 9. Providing a package ●Add composer.json ● Tag releases Semantic→ versioning ● Add Git repository to packagist.org
- 10.
- 11. Using it inproject ● Add composer .json ● Specify ● Add dependencies "type": "project"
- 12. Using it ina project git clone branch 8.1.x https://git.drupal.org/project/ drupal.git cd drupal composer install
- 13. What happens? ● Readscomposer.lock and installs recorded versions ● Downloads code and puts it into ./vendor (or somewhere else) ● Generates a class autoloader
- 14. Composer update &locks ● composer update – Update all the dependencies and write new lock file ● composer install – Apply what's recorded in the lock file
- 15. Composer & VCS ●Commit composer.json ● For projects: Commit composer.lock ● For libraries: Commit composer.lock for tests ● Avoid commit vendor files
- 16. Versions & Composer ●Require versions like 2.1.* ● composer supports many different version constraints ● Specify allowed versions, not specific versions
- 17. Composer & DrupalProjects
- 18. Bye, bye, drushmake! ● composer replaces drush make ● Support for Drupal modules via: – https://packagist.drupalcomposer.org – https://packages.drupal.org/7 – https://packages.drupal.org/8
- 19.
- 20. Start a newd8 project composer createproject drupalcomposer/drupalproject
- 21. What does itdo? ● Adds Drupal into the „web“ dir ● Adds folder structure, drush, Drupal console, … ● Custom projects can add more stuff and/or customize things – Add Drupal modules & themes!
- 22. Drupal modules &./vendor? ● Composer package types: – library – project – drupalmodule – drupaltheme – drupalprofile – drupaldrush
- 23. Working with a composer-basedDrupal project
- 24. composer install allthe way! ● Do not forget to run composer install! ● After pulling changes, run it! ● Best: Add to deployment alias: composer install && drush updatedb && ...
- 25.
- 26.
- 27. Update your modules ●composer update ● Commit the changes in composer.lock !
- 28. Update a singlemodule composer update drupal/module composer update drupal/module withdepdendencies
- 29. Checking installed versions ●List all packages: composer show ● List directly added pagckages only: composer show D
- 30. Where did itgo? composer show P
- 31.
- 32. Add custom repositories Withcomposer.json: "require": { "fago/example": "1.*" } "repositories": [ { "type": "vcs", "url": "http://github.com/fago/example" } ]
- 33. SemVer branching ● Branches: –1.0.x – 1.1.x – 2.0.x ● Tags / Releases: – 1.0.0 – 1.0.1 – 1.1.0 – 2.0.0
- 34.
- 35.
- 36.
- 37. Fork & addyour fork ● Alternative to patch files ● Works great with the Github pull request workflow ● composer createproject drupal/module path 2.2.0 ● Add in the fork instead upstream
- 38. Adding in yourfork "require": { "samson/yt": "devBRANCH as 2.0.0" }, "repositories": [ { "type": "vcs", "url": "https://github.com/fago/yt" } ],
- 39. Keep builds fast ●composer fetches either „dist“ or „source“ packages ● Prefer „dist“ packages for fast builds & cache use! ● Pre-configured in drupal-project
- 40.
- 41. Merge conflicts? composer update lock ● „Nice“hash in composer.lock ● Just merge and resolve it by doing either
- 42.
- 43. composer scripts ● Usesvendor binaries! ● React on events like – post-package-install – post-create-project-cmd – .. ● Reference other scripts via @script ● Handy for documented developer short-cuts
- 44.
- 45. Avoid committing vendors! ●Smaller diffs & pull requests => easy to review! ● Keeps repositories smaller (only custom code) ● Work with vendor repositories without submodules
- 46. Builds & Deployment 1.Hostingtakes care of it 2.Deployment tools like capistrano or deployer (http://deployer.org) 3.Git-based deployments of build- branches or build-repositories
- 47. Git-based deployments ● Commonin the Drupal world as it is required by many Drupal hosters ● I like it :-)
- 48. Build branches Never mergebuild branches back! master => build/master version/2016CW47 => build/version/2016CW47 release/2016CW47 => build/release/2016CW47
- 49. Build branches ● Wekeep them in the same repository ● Enables possible future enhancements
- 50. Creating builds ● PHP-consolescript for creating builds ● Takes care of updating pre-existing build branches (think: build/master) ● Takes care of tags ● Takes care of vendor repositories
- 51. phapp cli ● Toolfor managing PHP applications ● Not yet many commands besides „phapp build“ ● https://github.com/ drunomics/phappcli
- 52. phapp build ● Custombuild scripts via phapp.yml per project => Allows adding things like npm ● Just build in place? → phapp build ● Build a branch? → phapp build BRANCH
- 53. Deployment updates ● Applychanges after code update ● Do not rely on special server environments! → More reliable deployments!
- 54. Deployment script tools ●composer scripts ● Robo ● Drush, Drupal console Add dependencies to the project!
- 55.
- 56. Why? ● Develop re-usablePHP libraries, e.g. REST clients ● Feature modules for kick-starting development composer require drunomics/dsk_media
- 57. Add your ownpackages ● Custom repositories at project ● Run your own packagist ● Use Toran Proxy ● Use satis & static files – Scans your repositories – Re-run after every change
- 58.
- 59. Edit your code ●Use source for your packages "config": { "preferredinstall": { "drunomics/*": "source", "*": "dist" } }
- 60. Issue: Some modules needlibraries
- 61. Handling libraries &assets ● Possible solutions: – Add them via custom repostories – composer scripts for running bower or npm on project install – fxp/composer-asset-plugin – ...
- 62.
- 63.
- 64.
- 65.
- 66.