Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Sean Clarke10,256 Points
I'm curious, what about using Composer to manage themes, plugins, and even WP updates?
I got into using it along with git and more recently gulp ssh (for running the update commands on staging/live).
Some advantages & the workflow
- Project repo is tiny and super fast to deploy as it contains only composer.json (a description of the repos and versions you want to include, and no actual files).
- Manage custom and premium plugins using git/bitbucket, inc branches/versions
- Keeps everything fairly modular and independent
- Workflow: Edit your themes/plugins locally, push changes to appropriate repos/branches, then run composer updates on remote servers which 'detects' repo updates (according to versions set in composer.json)
Takes a little setting up and 'getting the concept clear in mind' but could be a useful augmentation and addition to what you've shared in the course here Jesse - which is great by the way, lots of useful gems to work right into my ever evolving workflow : )))