Managing WordPress with Composer and Git
summary
Demonstrates using Composer to install and update WordPress core, plugins and themes, and shows how combining Composer with Git creates a modern workflow for team development and multi-environment deployments. Covers tooling and processes to simplify updates, version control and deployments for WordPress projects.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 0:54Why Composer for WordPress
- 2:21Composer basics
- 4:35Installing plugins
- 6:21composer.json and lock
- 7:24Dev vs prod installs
- 9:14WP-CLI via Composer
- 10:16Version constraints
- 11:23Semantic versioning
- 12:30PHP version and extensions
- 13:32WordPress core via Composer
- 14:34Plugins and themes as packages
- 15:58Directory structure
- 17:06Custom WordPress directory
- 18:07Security with permissions
- 18:50Custom plugins via Composer
- 19:55Private plugin repos
- 20:41Proxy repos for packages
- 21:26Parallel package install
- 22:12Versioning WordPress projects
- 23:16Git ignore best practices
- 24:43Selective Git inclusion
- 25:04Master branch workflow
- 25:45Tagging releases
- 26:30Feature branches
- 27:13Separate repos per plugin
- 28:40Team workflows
- 29:28Defining versions in Git
- 30:11Line endings and config
- 31:15Excluding files from Git
- 31:37Automated actions on push
- 32:41Continuous delivery setup
- 33:26Heroku and tools
- 34:11Examples and resources
- 34:33Base config setup
- 35:19Quick project setup
- 36:02Summary and Q&A
