Magento 2 Workflows
Download as PPTX, PDF1 like4,696 views
This document outlines workflows and tools for managing Magento 2 development. It discusses challenges with scalable and complicated processes and assumptions of skill. Lessons learned include keeping developer freedom and code integrity while maintaining accountability. Recommended tools include Vagrant for simplified developer setups, PHPStorm for code completion and testing, Git for version control, and Composer for dependencies. The workflow uses separate modules in a Git repository structure with branches for different environments and deployment automation.
Magento 2 Workflows
- 2. • Challenges • Solutions • HelpfulTools • Recommendations • Q/A Agenda
- 3. My Story
- 4. The Process
- 5. Challenges • Scalable • Assumptions of Skill • Lynchpins
- 6. • Too Complicated • Not Automated • Too Many Assumptions • I Thought Others Would Care Mistakes
- 7. • KISS • Guides,NotRules • OptimizeMercilessly • RightProcessForThe RightTeam • DrawYourLineIn The Sand Lessons Learned
- 8. • Keep Developer Freedom? • MaintainCode Integrity? • Keep Accountability? Developer Setup
- 9. • *nix(Unix / Linux)basedOS • All Extensionsmustmatchappropriate versions – PHP – Apache/ NGinX – MySQL – Etc… • TESTSMUST PASS! Developer Setup
- 10. • KeepTrack of ChangesEffectively? • Reduce Conflictsand Reconciliation? • Code Promotion? Code Management
- 11. • Git/ Github • GitBranching System Code Management
- 12. • WhatTools? • Scalability? • Non-versioned Assets? Code Promotion
- 13. Code Promotion • Deploybot • Git/ Github • Composer • M2 Command Line
- 15. • Vagrant • PHPStorm/ IDE • Composer • Git/ Github Tools
- 16. Vagrant • Simplify Developer Setup • Easily Distributed Environment • Flexible • Expandable (Docker/ AWS / etc.)
- 17. Vagrant • UsedSimple Vagrantfile and Shell Script • KeptFiles in Version Control • Allowed Simple DeveloperSetup $ ~/ git [email protected]:username/repo.git $~/vagrantup
- 18. Vagrant Performance • If it doesn’t change,don’t mount it! • Increase CPUs and Memory for the Box • Symlink var/ directories to /tmp/magento/var/* • NFS mount (exceptvar/) • Consider Vmware • Consider Docker
- 19. Consider Building Your Own Box Vagrant
- 20. PHPStorm • Code Completion • Automated Code Sniffs • Integrated Testing • Xdebug Support • Code Templates
- 21. PHPStorm
- 22. • Complete URNs $ ~/ php bin/magento dev:urn-catalog:generate./misc.xml PHPStorm
- 24. • Mess Detector • ECG Standards • PSR Standards Code Sniffs
- 25. Code Sniffs
- 26. WorkFlow
- 27. Git Repository Structure {root} - Vagrantfile - ClientName/ - Module01/ - Module02/ - Module03/
- 28. Each moduleis packaged separately. This allows maximum flexibility. Git Repository Structure
- 29. $ ~/ git [email protected]:company/clientrepo.git $ ~/ git checkout–b mybranch develop $ ~/vagrantup Developer WorkFlow
- 30. • Code is kept in separate repo • Maintainedand deployed in branches (dev, stage, prod, etc.) • Allows faster deployments and rollbacks • Client code is kept as artifacts on theserver. • Composer.json points to directorythat holds all artifacts. Deployment
- 31. $ ~/ git clone [email protected]:username/clientserverrepo.git $ ~/ git checkout -b<branchname> $ ~/ composercreate-project--repository-url=https://repo.magento.com/magento/project-community-edition ./ $ ~/ git commit –m “…” $ ~/ composerrequireclientname/module01clientname/module02(etc.) $ ~/ phpbin/magentodeploy:mode:set<mode> $ ~/ phpbin/magentomodule:enableClient_Module01Client_Module02 $ ~/ phpbin/magentosetup:upgrade $ ~/ git commit –m “…” Server Setup
- 32. $ ~/ git fetch –all $ ~/ git mergeorigin/stage $ ~/ php bin/magento setup:di:compile-multi-tenant $ ~/ git commit –m “…” $ ~/ git tag v1.0.10 $ ~/ (other misc…) Deployment
- 33. (onbranchproductioninrepo) $~/ gitfetch–all $~/ gitcheckout–b v1.0.10v1.0.10 $~/ phpbin/magentomodule:enable<module01><module02> $~/ phpbin/magentosetup:upgrade Production Deployment
- 34. Automation Git Hooks can automate deployment of code. Neverhook a production deployment! Deploybot can automate everything we’veseen as well as static asset generation, etc.