wp-cli mit Homebrew, dnf, MacPorts, Nix, pacman, zypper, scoop installieren

Projektlinks

• Homepage
• Repository
• Paketmanager-Seite

Befehle und Aliase

• wp

Projektgeschichte

The WP-CLI GitHub repository was created on 2011-09-10, and the current WordPress.org page says WP-CLI has shipped continuously since 2011. A 2016 project post identifies Andreas Creten as WP-CLI's founder and Daniel Bachhuber as maintainer, capturing the project's mid-2010s concern with reducing its bus factor and strengthening long-term governance.

In late 2016, WP-CLI's sustainability discussion became public. Daniel Bachhuber wrote that WP-CLI had become too large to maintain purely as volunteer work, and an update on 2016-12-28 announced that WP-CLI was now an official WordPress project. The January 2017 follow-up framed this as a continuation plan: development would continue on GitHub, the website would move toward WordPress.org, and responsibility would no longer rest on one maintainer.

Adoptionsgeschichte

By May 2016, Bachhuber described WP-CLI as hugely important to the WordPress ecosystem, with thousands of regular developers and tens or hundreds of companies integrating it deeply into business processes. That adoption reflected a clear need in WordPress operations: repeatable admin tasks, deployment steps, content imports, database changes, and plugin/theme work are easier to automate from a CLI than through a web UI.

WP-CLI's officialization also reflected WordPress's broader ecosystem model. It remained a community-maintained tool, but with a clearer home under WordPress.org and public governance for releases and contribution.

Wie es verwendet wird

Typical WP-CLI usage starts with the wp command. Developers run commands such as wp core download or update, wp plugin install or activate, wp db export, wp search-replace, wp user, wp cron, and wp media to script site administration. The official command reference lists commands for core, config, database, cron, media, menus, users, posts, and many other WordPress subsystems.

WP-CLI is also extensible: WordPress.org describes custom commands and community packages, and many hosts, deployment scripts, CI jobs, and maintenance playbooks rely on it as the stable automation surface for WordPress.

Warum Paket-Nerds sich dafür interessieren

WP-CLI is significant because it turned a browser-centered CMS into something Unix-shaped: commands, subcommands, config files, exit statuses, and scripts. For package maintainers and operations engineers, it is the standard bridge between WordPress and normal deployment automation.

It is also an example of a community tool becoming official infrastructure after adoption proved its importance. The project did not start as WordPress core, but by 2016-2017 its ecosystem role was large enough that WordPress.org stewardship became the maintenance answer.

Zeitleiste

• 2011-09-10: wp-cli/wp-cli GitHub repository is created.
• 2014-03-27: v0.12.0 is published in GitHub releases.
• 2016-05-12: Public GitHub issue discusses WP-CLI's bus factor and organizational stability.
• 2016-12-28: Make WordPress update announces WP-CLI is now an official WordPress project.
• 2017-01-03: Follow-up post explains the official WordPress.org transition.
• 2025-05-07: v2.12.0 is published in GitHub releases.

Related projects

• WordPress core is the CMS that WP-CLI operates.
• The WP-CLI command reference and Make WordPress CLI handbook are the official documentation surfaces.
• Community WP-CLI packages extend the base command set.

Quellen

• https://api.github.com/repos/wp-cli/wp-cli
• https://api.github.com/repos/wp-cli/wp-cli/releases/latest
• https://api.github.com/repos/wp-cli/wp-cli/releases?per_page=100
• https://developer.wordpress.org/cli/commands/
• https://github.com/wp-cli/wp-cli/issues/2743
• https://make.wordpress.org/cli/2016/06/23/future-wp-cli/
• https://make.wordpress.org/cli/2016/12/12/the-big-question/
• https://make.wordpress.org/cli/2017/01/03/lets-do-this/
• https://wordpress.org/cli/