Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Composer & Deployer for enterprise - Oleksii Kalinichenko

104 views

Published on

Будемо розбирати "Composer" та "Deployer" для великих компаній на прикладі JYSK

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Composer & Deployer for enterprise - Oleksii Kalinichenko

  1. 1. Composer & Deployer for Enterprise Oleksiy Kalinichenko Drupal DevLead at JYSK
  2. 2. Composer.json files in JYSK Projects: Main
  3. 3. Composer.json files in JYSK Projects: Main
  4. 4. Composer.json files in JYSK Projects: Main
  5. 5. Composer.json files in JYSK Projects: Main
  6. 6. Composer.json files in JYSK Projects: Main
  7. 7. Composer.json files in JYSK Projects: Main
  8. 8. Composer.json files in JYSK Projects: Main
  9. 9. Composer.json files in JYSK Projects: Main
  10. 10. Composer.json files in JYSK Projects: Main
  11. 11. Composer.json files in JYSK Projects: Main
  12. 12. Composer.json files in JYSK Projects: Main
  13. 13. Composer.json files in JYSK Projects: Main
  14. 14. Composer.json files in JYSK Projects: Main
  15. 15. Composer.json files in JYSK Projects: Main
  16. 16. Composer.json files in JYSK Projects: Main “composer.patches.json”
  17. 17. Composer.json files in JYSK Projects: Main “composer.patches.json”
  18. 18. Composer.json files in JYSK Projects: Main “composer.patches.json”
  19. 19. Composer.json files in JYSK Projects: Main Drush command “policy.drush.inc”
  20. 20. Composer.json files in JYSK Projects: Main Drush command “policy.drush.inc”
  21. 21. Composer.json files in JYSK Projects: Main Drush command “policy.drush.inc”
  22. 22. Common Problems and Solutions with Drupal + Composer FAQ
  23. 23. VENDOR How do I deploy a Drupal codebase if the `vendor` directory isn't in the codebase?
  24. 24. CKEditor I need to put a library (e.g. CKEditor for Webform) in the `libraries` directory, and not in `vendor`. Is this even possible with Composer?
  25. 25. NON-Packagist One frontend library I need to add to my site (for a module, not a theme) is not on Packagist. How can I `composer require` it without it being on Packagist?
  26. 26. D7 / D8 What's the best way to start building the codebase for a new Drupal 8 (Drupal 8) website?
  27. 27. */modules If I have a multisite installation, how can I put certain modules in one `sites/site-a/modules` directory, and others in another `sites/site-b/modules` directory?
  28. 28. UI Using the command line to install modules is a lot to ask. Isn't there some sort of UI I could use?
  29. 29. version conflict What happens if there are dependencies required by two modules or core and a module, and there's a conflict with version requirements?
  30. 30. custom module How can I include libraries and shared modules that I made for my own sites (they're not on Packagist)?
  31. 31. make file I have a Drush make file for my site. Can I easily convert this to a `composer.json` file?
  32. 32. composer.json I set up my Drupal 8 site by downloading archives from Drupal.org and copying them into the codebase. How can I convert my codebase to use a `composer.json` file?
  33. 33. `^` and `~` What is the difference between `^` and `~` in version requirements, and should I use one over the other?
  34. 34. composer update When I run `composer update` a lot of weird things happen and everything is updated, even if I don't want it to be updated. Is there a way I can just update one module at a time?
  35. 35. composer install When I run `composer install` on my production server, it runs out of memory. How can I avoid this issue?
  36. 36. security For security reasons, I need to verify that the code I'm running in production wasn't hacked or modified. How can I do this if I'm using Composer to manage my dependencies?
  37. 37. re-cloning I totally screwed up some of the dependencies on my site while I was tinkering with them. Is there any way to 'nuke' all the things in my codebase that Composer manages so I can do a fresh `composer install` and get them back into the correct state (short of deleting my entire codebase and re-cloning my site locally)?
  38. 38. composer.lock My team constantly battles with `composer.lock` file merge conflicts. How can we avoid this painful experience?
  39. 39. tips Do you have any other tips for making Composer use easier and more delightful?

×