2 ms·

I've been very happy with all the open sourced WordPress tools coming out.. WP-CLI has been a huge time saver for me.. Use it on dev and production environment

I've been very happy with all the open sourced WordPress tools coming out.. WP-CLI has been a huge time saver for me.. Use it on dev and production environments I recently revisited the Roots theme and have been using it on all projects. About to try Genesis out. I've been having trouble keeping track of dev/production DB's so I'm hoping this will help solve this problem

ericclemmons 13y ago
The last time I tried out WP-CLI was, admittedly, ~ year ago, where I believe the limitation was that you administered the WordPress install on the same machine it ran on, rather than administering via ansible, capistrano, or other DevOps tools. What I've been building instead is likening WordPress development to our other PHP/Node applications, where changing themes, installing plugins, and migrating data is done first locally, prepped for migration (either via a script, or just just deploying the entire DB back out), then released alongside other PRs. Regarding Roots, I'm impressed with it, but decided to leave Roots, _s, and other themes/frameworks out by default, since the community is largely fragmented (us as well) regarding which is best. The problem I'm solving next is the automated compilation of assets that's generally handled via Assetic, CodeKit, and other tools, but isn't part of the standard WP workflow.