Comments on: The What, How and Why of WP-CLI: WordPress in Your Terminal

By: Working With The Command Line and WP-CLI – WPShout

Working With The Command Line and WP-CLI – WPShout — Tue, 06 Jun 2017 17:16:13 +0000

[…] The What, How and Why of WP-CLI: WordPress in Your Terminal […]

By: Anatomy of a WP-CLI Command: wp database import | WPShout

Anatomy of a WP-CLI Command: wp database import | WPShout — Tue, 09 May 2017 15:56:03 +0000

[…] The What, How and Why of WP-CLI: WordPress in Your Terminal […]

By: Shawn Hooper

Shawn Hooper — Wed, 01 Feb 2017 14:30:51 +0000

Search and Replace is definitely one of the most valuable uses of WP-CLI available, in my opinion. In addition to Matt’s comment about using the –dry-run flag, my other favourite is the –export option, which allows you to do a search and replace, but instead of making the changes to the database, it creates a SQL file with changes made there. So, you’re in your dev environment, but need to prepare a copy of the database for production?

wp search-replace mydevdomain.local productionexample.com –export=production.sql

Boom! You have a file ready to import into your production environment, but your database in development still works!

By: C.A. Gross

C.A. Gross — Wed, 01 Feb 2017 05:21:46 +0000

Learning what WP-CLI can do for me has been on my to-do list for a long time–this article was a step in the right direction. Thanks very much for it.

I’m actually interested in potentially using WP-CLI for automation–specifically WordPress installs. Do you have a tutorial or description you could maybe recommend that might get me started?

By: Matt Gross

Matt Gross — Tue, 31 Jan 2017 17:52:39 +0000

Quick note on using search-replace: I always us the –dry-run flag before running a live search replace. It helps to provide a first level sanity check and many times has prevented some tragic misspellings. Should certainly be built into the workflow to make sure the results match your expectations.