WP-CLI has over 1,000 commands, but you only need about 20 to handle 90% of daily WordPress development tasks. Master these essential commands, and you’ll dramatically increase your productivity and efficiency.

In this guide, you’ll learn the 20 most powerful WP-CLI commands that professional WordPress developers use daily—complete with practical examples and real-world use cases.

Why Master Essential WP-CLI Commands?

WP-CLI documentation lists hundreds of commands, but most developers use the same core set repeatedly.

Problems with GUI WordPress Management

Repetitive clicking: Installing 10 plugins means 10 separate install-and-activate workflows.

No batch operations: Can’t update all themes or export all user data at once.

Time waste: Simple tasks like flushing cache require multiple page loads.

No automation: Can’t script routine maintenance or deployment tasks.

Context switching: Moving between terminal and browser breaks workflow.

Essential Commands Advantages

Speed: Execute complex operations in seconds instead of minutes.

Muscle memory: Same 20 commands handle most scenarios across all sites.

Scriptable: Chain commands together for powerful automation workflows.

SSH-ready: Manage remote servers without leaving your terminal.

Reliable: Commands work identically across all WordPress installations.

According to WordPress developer surveys, developers who use WP-CLI save an average of 5-10 hours per week on routine tasks.

Core WordPress Commands

Manage WordPress core installation and configuration.

1. Check WordPress Version

# Show current WordPress version
wp core version

# Show detailed version info
wp core version --extra

# Check if core update available
wp core check-update

Use Case: Quickly verify WordPress version before applying updates or troubleshooting compatibility issues.

2. Update WordPress Core

# Update to latest version
wp core update

# Update to specific version
wp core update --version=6.4.2

# Preview update without installing
wp core update --dry-run

Pro Tip: Always backup database before core updates with wp db export backup.sql.gz.

3. Verify WordPress Installation

# Check if WordPress is installed
wp core is-installed

# Check and return exit code (useful in scripts)
wp core is-installed && echo "WordPress is installed"

# Verify file integrity
wp core verify-checksums

Use Case: Verify WordPress files haven’t been corrupted or tampered with during security audits.

Learn more in the official WP-CLI core commands documentation.

Plugin Management Commands

Control plugins efficiently from command line.

4. List Installed Plugins

# List all plugins
wp plugin list

# Show only active plugins
wp plugin list --status=active

# Export to CSV for inventory
wp plugin list --format=csv > plugins-inventory.csv

5. Install and Activate Plugins

# Install plugin
wp plugin install wordfence

# Install and activate immediately
wp plugin install contact-form-7 --activate

# Install multiple plugins at once
wp plugin install wordfence yoast-seo autoptimize --activate

Use Case: Set up standard plugin stack on new WordPress installations in seconds.

6. Update Plugins

# Update all plugins
wp plugin update --all

# Update specific plugin
wp plugin update wordfence

# Preview updates without installing
wp plugin update --all --dry-run

Pro Tip: Use --dry-run on production to preview which plugins need updates before applying them.

Theme Management Commands

Manage WordPress themes quickly.

7. List and Activate Themes

# List all themes
wp theme list

# Activate theme
wp theme activate twentytwentyfour

# Install and activate theme
wp theme install astra --activate

8. Update Themes

# Update all themes
wp theme update --all

# Update specific theme
wp theme update astra

Use Case: Keep all themes updated for security without clicking through admin panel.

Database Management Commands

Handle database operations safely and efficiently.

9. Export Database

# Basic database export
wp db export

# Export with custom filename
wp db export backup-$(date +%Y%m%d).sql

# Export with compression (recommended)
wp db export backup.sql.gz

Critical: Export before any major changes—updates, migrations, or content modifications.

10. Import Database

# Import database
wp db import backup.sql

# Import compressed database
wp db import backup.sql.gz

11. Search and Replace URLs

# Replace URLs in database
wp search-replace 'http://oldsite.com' 'https://newsite.com'

# Preview changes without applying (always use first!)
wp search-replace 'old.com' 'new.com' --dry-run

# Replace with report showing all changes
wp search-replace 'old' 'new' --report --dry-run

Use Case: Essential for site migrations, domain changes, and HTTP to HTTPS upgrades. Learn more about WordPress database management.

12. Optimize Database

# Optimize all tables
wp db optimize

# Check database for errors
wp db check

# Repair corrupted tables
wp db repair

User Management Commands

Create and manage WordPress users from terminal.

13. List Users

# List all users
wp user list

# Show only administrators
wp user list --role=administrator

# Export users to CSV
wp user list --format=csv > users.csv

14. Create Users

# Create user (prompts for password)
wp user create johndoe john@example.com

# Create with specific role
wp user create editor1 editor@example.com --role=editor

# Create and send password via email
wp user create newuser user@example.com --send-email

Use Case: Quickly onboard new team members or clients without using WordPress admin.

15. Reset User Password

# Reset password (sends email)
wp user reset-password admin

# Set specific password
wp user update admin --user_pass=NewSecureP@ssw0rd123

Content Management Commands

Manage posts, pages, and content efficiently.

16. List Posts

# List all posts
wp post list

# Show only published posts
wp post list --post_status=publish

# Filter by category
wp post list --category_name=tutorials

# Count total posts
wp post list --format=count

17. Create and Update Posts

# Create post
wp post create --post_title="New Post" --post_status=publish

# Create with content
wp post create --post_title="Hello" --post_content="Post content here" --post_status=publish

# Update post
wp post update 123 --post_title="Updated Title"

Use Case: Bulk create test content for development environments or automate content publishing.

Cache and Maintenance Commands

Keep WordPress running smoothly with maintenance commands.

18. Flush Cache and Permalinks

# Flush object cache
wp cache flush

# Flush rewrite rules (permalinks)
wp rewrite flush

# Combined flush for troubleshooting
wp cache flush && wp rewrite flush

Use Case: First step in troubleshooting 404 errors or stale content issues.

19. Clean Transients

# Delete expired transients
wp transient delete --expired

# Delete all transients (safe, they regenerate)
wp transient delete --all

# List all transients
wp transient list

Pro Tip: Deleting expired transients can reduce database size by 10-30% on older sites.

Configuration and Options Commands

Manage WordPress configuration and options.

20. Manage Options

# Get option value
wp option get siteurl

# Update option
wp option update blogdescription "My awesome site"

# List all options (warning: very long output)
wp option list

# Add new option
wp option add custom_setting "custom value"

Use Case: Quickly change site URL, title, or custom plugin settings without database queries.

Command Combinations for Power Users

Chain essential commands for powerful workflows.

Quick Site Setup

# Install WordPress, plugins, and configure
wp core download
wp config create --dbname=wordpress --dbuser=root --dbpass=password
wp core install --url=example.com --title="My Site" --admin_user=admin --admin_email=admin@example.com
wp plugin install wordfence contact-form-7 yoast-seo --activate
wp theme install astra --activate

Complete Site Backup

# Backup database and files
DATE=$(date +%Y%m%d)
wp db export backup-$DATE.sql.gz
tar -czf files-backup-$DATE.tar.gz wp-content/
echo "Backup complete: backup-$DATE.sql.gz + files-backup-$DATE.tar.gz"

Site Health Check

# Check core, verify files, update everything
wp core version
wp core verify-checksums
wp plugin update --all --dry-run
wp theme update --all --dry-run
wp db check

Next Steps

You now have the 20 essential WP-CLI commands that cover 90% of daily WordPress development tasks.

Recommended Learning Path

Week 1: Practice core commands

• Install/update WordPress core
• Manage plugins and themes
• Basic database exports

Week 2: User and content management

• Create and manage users
• Bulk content operations
• Search-replace operations

Week 3: Automation basics

• Chain commands together
• Create simple backup scripts
• Automate routine maintenance

Week 4: Advanced workflows

• Build deployment scripts
• Implement automated testing
• Create custom commands

Advanced Topics

1. WP-CLI Configuration Files – Customize WP-CLI behavior
2. WP-CLI Packages – Extend functionality with community packages
3. Custom WP-CLI Commands – Build your own commands

Get More Resources

Download WP-CLI command cheatsheet – Quick reference for all 20 commands

Join our email course for:

• Weekly WP-CLI tutorials
• Advanced automation techniques
• Real-world case studies

Conclusion

These 20 essential WP-CLI commands form the foundation of efficient WordPress development. You don’t need to memorize hundreds of commands—just master these core operations.

What we covered:

✅ Core WordPress management (version, update, verify)
✅ Plugin and theme operations (install, update, activate)
✅ Database commands (export, import, search-replace, optimize)
✅ User management (create, list, password reset)
✅ Content operations (list, create, update posts)
✅ Maintenance commands (cache flush, transients, options)

Start using these commands daily, and within two weeks they’ll become second nature. Your productivity will skyrocket, and you’ll wonder how you ever managed WordPress without them.

Ready to level up? Learn WP-CLI automation with bash scripts or advanced database operations.

Questions about essential WP-CLI commands? Drop a comment below!

Found this helpful? Share with other WordPress developers.

The post 20 Essential WP-CLI Commands Every WordPress Developer Should Know appeared first on WP-CLI Mastery.

WP-CLI config files automate command options, set project defaults, create custom aliases, and configure environment-specific settings. One wp-cli.yml file eliminates repetitive typing and standardizes WP-CLI behavior across your team.

In this guide, you’ll learn WP-CLI config file best practices, from basic setup to advanced configurations used by professional WordPress development teams managing multiple environments.

Why Use WP-CLI Config Files?

WP-CLI configuration simplifies command execution and ensures consistency across environments.

Problems Without Config Files

Repetitive flags: Typing --path, --url, --allow-root on every command.

Environment inconsistency: Different settings on dev, staging, and production.

Team confusion: Each developer uses different WP-CLI settings.

Command complexity: Long commands with multiple flags are error-prone.

No standardization: Can’t enforce best practices across projects.

WP-CLI Config File Advantages

DRY principle: Configure once, use everywhere.

Environment-aware: Different configs for dev, staging, production.

Team consistency: Everyone uses same WP-CLI settings.

Shorter commands: wp plugin list instead of wp plugin list --path=/var/www/html --allow-root.

Version controlled: Config files tracked in Git ensure reproducibility.

According to WP-CLI documentation, config files are essential for professional WordPress workflows.

WP-CLI Config File Basics

Understand WP-CLI config file locations and structure.

Config File Locations

WP-CLI searches for config files in this order:

# 1. Current directory and parents (project-specific)
./wp-cli.yml
../wp-cli.yml
../../wp-cli.yml

# 2. User's home directory (global defaults)
~/.wp-cli/config.yml

# 3. System-wide config (rarely used)
/etc/wp-cli/config.yml

Priority: Project-specific configs override global configs.

Basic wp-cli.yml Structure

# wp-cli.yml - Basic configuration

# WordPress installation path
path: /var/www/html

# Allow root user (for servers)
allow-root: true

# Site URL
url: https://example.com

# Disable colorized output
color: false

# Quiet mode (suppress informational messages)
quiet: false

# Debug mode
debug: false

Place in your WordPress root directory:

cd /var/www/html
nano wp-cli.yml

Test Config File

# Show current config
wp cli info

# Show which config files are loaded
wp cli info | grep "WP-CLI config"

# Test path setting
wp option get siteurl

Learn more in the WP-CLI config documentation.

Project-Specific Configuration

Configure WP-CLI for individual WordPress projects.

Complete Project Config

# wp-cli.yml - Complete project configuration

# Core settings
path: wp
url: https://example.com
allow-root: true

# Output settings
color: true
quiet: false
debug: false

# Command aliases
@staging:
  ssh: user@staging-server.com/var/www/staging

@production:
  ssh: user@prod-server.com/var/www/production

# Default parameters for commands
plugin list:
  - --format=table
  - --fields=name,status,version,update

theme list:
  - --format=table
  - --fields=name,status,version

post list:
  - --post_type=post
  - --orderby=date
  - --order=DESC
  - --posts_per_page=20

# Require specific WP-CLI version
require:
  - wp-cli/wp-cli: ^2.9

# Custom PHP binary
php: /usr/bin/php8.1

# Apache modules (for server info)
apache_modules:
  - mod_rewrite

WordPress in Subdirectory

# When WordPress is in a subdirectory

path: public/wp

# or
path: wordpress

# or
path: htdocs/wordpress

Custom Database Configuration

# Override database settings (for testing)

dbname: test_database
dbuser: test_user
dbpass: test_password
dbhost: localhost

# Use custom table prefix
dbprefix: custom_

Global User Configuration

Set default WP-CLI behavior for all projects.

Create Global Config

# Create config directory
mkdir -p ~/.wp-cli

# Create global config file
nano ~/.wp-cli/config.yml

Global Config Template

# ~/.wp-cli/config.yml - Global defaults

# Always allow root (useful for servers)
allow-root: true

# Color output enabled
color: true

# Show errors
debug: false
quiet: false

# Custom command aliases (available everywhere)
alias:
  ll: plugin list --status=active
  tl: theme list --status=active
  flushall: cache flush && rewrite flush
  quickbackup: db export backup-$(date +%Y%m%d).sql.gz

# Default formats
plugin list:
  - --format=table

# Disable auto-check for updates
disable_auto_check_update: true

# Custom package path
packages_dir: ~/.wp-cli/packages/

Personal Aliases

# Useful custom aliases in global config

alias:
  # Quick commands
  status: core is-installed && db check
  info: core version && option get siteurl

  # Maintenance shortcuts
  mm-on: maintenance-mode activate
  mm-off: maintenance-mode deactivate

  # Cleanup operations
  cleanup: |
    post delete $(post list --post_status=trash --format=ids) --force
    transient delete --expired
    cache flush

  # Security checks
  security: |
    core verify-checksums
    plugin verify-checksums --all

  # Quick site backup
  backup: |
    db export backups/db-$(date +%Y%m%d-%H%M%S).sql.gz
    echo "Backup complete"

Environment-Specific Configs

Different configurations for development, staging, and production.

Multi-Environment Setup

# Project structure with environment configs
/var/www/
├── wp-cli.yml              # Base config
├── wp-cli.local.yml        # Development overrides
├── wp-cli.staging.yml      # Staging overrides
└── wp-cli.production.yml   # Production overrides

Base Config (wp-cli.yml)

# wp-cli.yml - Shared across all environments

path: public
color: true

# Commands available in all environments
alias:
  status: core is-installed && db check

Development Config (wp-cli.local.yml)

# wp-cli.local.yml - Development settings

url: http://localhost:8080
debug: true
allow-root: true

# Enable all error output
WP_DEBUG: true
WP_DEBUG_LOG: true
WP_DEBUG_DISPLAY: true

# Development-specific aliases
alias:
  seed: scaffold post-content --count=50
  reset-db: db reset --yes && core install --url=http://localhost:8080 --title="Dev Site" --admin_user=admin --admin_email=dev@example.test

Production Config (wp-cli.production.yml)

# wp-cli.production.yml - Production settings

url: https://example.com
debug: false
quiet: false
allow-root: true

# Disable dangerous commands
disabled_commands:
  - db drop
  - db reset
  - scaffold

# Production-safe aliases
alias:
  deploy: |
    maintenance-mode activate
    plugin update --all
    theme update --all
    core update
    cache flush
    rewrite flush
    maintenance-mode deactivate

Use Environment Configs

# Load specific config with --config flag
wp --config=wp-cli.local.yml plugin list
wp --config=wp-cli.production.yml core update

# Or use WP_CLI_CONFIG_PATH environment variable
export WP_CLI_CONFIG_PATH=wp-cli.staging.yml
wp plugin list

Learn about WordPress environments best practices.

Advanced Configuration Options

Professional config features for complex workflows.

SSH Remote Execution

# Execute commands on remote servers

@staging:
  ssh: user@staging.example.com/var/www/staging
  path: /var/www/staging

@production:
  ssh: user@prod.example.com/var/www/production
  path: /var/www/production

# Usage:
# wp @staging plugin list
# wp @production core update

HTTP Basic Auth

# For sites behind HTTP authentication

http:
  user: admin
  password: secretpassword

Custom PHP Binary

# Use specific PHP version

php: /usr/bin/php8.1

# or with full path
php_bin: /opt/php/8.1/bin/php

Require Specific Packages

# Ensure WP-CLI packages are installed

require:
  - wp-cli/doctor-command
  - wp-cli/profile-command
  - aaemnnosttv/wp-cli-login-command

Disable Commands

# Prevent dangerous commands on production

disabled_commands:
  - db drop
  - db reset
  - site delete
  - scaffold

Command-Specific Defaults

Set default options for frequently used commands.

Plugin Command Defaults

plugin install:
  - --activate

plugin list:
  - --format=table
  - --fields=name,status,version,update

plugin update:
  - --dry-run # Always preview first

Database Defaults

db export:
  - --add-drop-table

db import:
  - --skip-optimization

search-replace:
  - --dry-run
  - --report
  - --precise

Post Defaults

post list:
  - --post_type=post
  - --orderby=date
  - --order=DESC
  - --posts_per_page=25
  - --fields=ID,post_title,post_status,post_date

post create:
  - --post_status=draft
  - --post_author=1

Security and Team Configs

Secure configs for team collaboration.

Secrets in Environment Variables

# Don't hardcode credentials in config files!

# WRONG (insecure)
http:
  user: admin
  password: secretpassword

# RIGHT (use environment variables)
http:
  user: ${WP_CLI_HTTP_USER}
  password: ${WP_CLI_HTTP_PASSWORD}

Set in shell:

export WP_CLI_HTTP_USER="admin"
export WP_CLI_HTTP_PASSWORD="secretpassword"

.gitignore for Config Files

# .gitignore

# Ignore local overrides
wp-cli.local.yml
wp-cli.*.local.yml

# Ignore configs with secrets
wp-cli.secrets.yml

# Keep base configs
!wp-cli.yml
!wp-cli.example.yml

Team Config Template

# wp-cli.example.yml - Template for team

path: public
url: REPLACE_WITH_YOUR_URL
allow-root: true
# Copy this to wp-cli.local.yml and customize
# cp wp-cli.example.yml wp-cli.local.yml

Next Steps

You now have comprehensive WP-CLI config file knowledge for professional workflows.

Recommended Learning Path

Week 1: Basic configs

• Create project wp-cli.yml
• Set up global config
• Test common settings

Week 2: Environment configs

• Create dev/staging/prod configs
• Set up SSH aliases
• Test environment switching

Week 3: Advanced features

• Custom command defaults
• Team configurations
• Security best practices

Week 4: Optimization

• Refine configs for workflow
• Document team standards
• Share configs via Git

Advanced Topics

1. WP-CLI Package Development – Build custom commands
2. WP-CLI in CI/CD – Automated testing configs
3. Multi-Site Configs – Network-wide settings

Get More Resources

Download config templates including:

• Project config examples
• Environment-specific configs
• Team collaboration templates

Join our email course for:

• Weekly WP-CLI tutorials
• Configuration best practices
• Workflow optimization tips

Conclusion

WP-CLI config files transform repetitive command-line work into streamlined, consistent workflows that save time and prevent errors across your entire team.

What we covered:

✅ Config file locations and search order
✅ Project-specific and global configurations
✅ Environment-specific setups (dev/staging/prod)
✅ Advanced options (SSH, custom defaults, aliases)
✅ Command-specific defaults and optimizations
✅ Security and team collaboration practices

Master these configurations, and you’ll never type redundant WP-CLI flags again—just clean, efficient commands that work consistently everywhere.

Ready for more? Learn WP-CLI aliases and shortcuts or custom command development.

Questions about WP-CLI config files? Drop a comment below!

Found this helpful? Share with other WordPress developers.

The post WP-CLI Config Files: Best Practices and Advanced Configuration (2025) appeared first on WP-CLI Mastery.

In this comprehensive guide, you’ll learn how to install and configure WP-CLI on Ubuntu and Debian Linux systems from scratch. Whether you’re a beginner or experienced developer, this step-by-step tutorial will have you up and running in less than 10 minutes.

What is WP-CLI and Why Use It?

WP-CLI is a powerful command-line tool for managing WordPress installations. Instead of clicking through the WordPress admin panel, you can execute commands directly from your terminal.

Key Benefits of WP-CLI

Time Savings: Update all plugins across 50 sites with one command instead of logging into each site manually.

Automation: Schedule backups, updates, and maintenance tasks with cron jobs.

Bulk Operations: Perform actions on hundreds of posts, users, or sites simultaneously.

Remote Management: Manage WordPress sites via SSH without needing FTP or admin panel access.

DevOps Integration: Integrate WordPress into your CI/CD pipelines and deployment scripts.

Real-World Use Cases

• Update all WordPress core, plugins, and themes across 100+ sites in minutes
• Import/export databases during migrations
• Generate test content for development environments
• Automate WordPress installation and configuration
• Search and replace URLs after moving sites
• Manage WordPress Multisite networks efficiently

According to WordPress.org, over 43% of all websites use WordPress. If you manage even 2-3 WordPress sites, WP-CLI will save you hours every week.

Prerequisites

Before installing WP-CLI, ensure your system meets these requirements:

System Requirements

• Operating System: Ubuntu 18.04+ or Debian 9+ (this guide focuses on these distributions)
• PHP: Version 7.4 or higher (WordPress 6.0+ requirement)
• SSH Access: Terminal access to your server
• WordPress: An existing WordPress installation (or plan to install one)
• Root/Sudo Access: Permission to install system packages

Check Your PHP Version

First, verify you have PHP installed and check the version:

php -v

You should see output like:

PHP 8.1.2 (cli) (built: Jan 15 2025 10:30:45)
Copyright (c) The PHP Group
Zend Engine v4.1.2

If PHP is not installed or the version is below 7.4, install or update it:

# Ubuntu/Debian
sudo apt update
sudo apt install php-cli php-mbstring php-xml php-mysql -y

The php-cli, php-mbstring, and php-xml extensions are required for WP-CLI to function properly.

Check for Existing WordPress Installation (Optional)

If you already have WordPress installed, note the installation path. Common locations:

• /var/www/html
• /var/www/yourdomain.com/public_html
• /home/username/public_html

You’ll need this path to run WP-CLI commands later.

Installing WP-CLI on Ubuntu/Debian

There are several methods to install WP-CLI. We’ll use the official recommended method: downloading the Phar (PHP Archive) file.

Step 1: Download WP-CLI

Download the latest WP-CLI Phar file using curl:

curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar

Alternative: If you don’t have curl installed, use wget:

wget https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar

This downloads wp-cli.phar to your current directory.

Step 2: Verify the Phar File Works

Before installation, test that the Phar file is working:

php wp-cli.phar --info

You should see output showing WP-CLI information:

OS:     Linux 5.15.0-58-generic #64-Ubuntu SMP x86_64
Shell:  /bin/bash
PHP binary:    /usr/bin/php8.1
PHP version:   8.1.2
php.ini used:  /etc/php/8.1/cli/php.ini
MySQL binary:  /usr/bin/mysql
MySQL version: mysql  Ver 8.0.31-0ubuntu0.22.04.1

If you see this output, WP-CLI is working correctly.

Step 3: Make the File Executable

Add executable permissions to the Phar file:

chmod +x wp-cli.phar

Step 4: Move to System Path

Move the Phar file to a directory in your system PATH so you can run it from anywhere:

sudo mv wp-cli.phar /usr/local/bin/wp

Now you can run WP-CLI using the wp command instead of php wp-cli.phar.

Step 5: Verify Installation

Confirm WP-CLI is installed correctly:

wp --info

If you see the WP-CLI information output, congratulations! WP-CLI is successfully installed.

Expected output:

OS:     Linux 5.15.0-58-generic #64-Ubuntu SMP x86_64
Shell:  /bin/bash
PHP binary:    /usr/bin/php8.1
PHP version:   8.1.2
WP-CLI version: 2.9.0

Verifying Your Installation

Let’s run a few basic commands to ensure everything works properly.

Check WP-CLI Version

wp cli version

Output:

WP-CLI 2.9.0

Get Help

View available WP-CLI commands:

wp help

This displays a comprehensive list of all WP-CLI commands organized by category.

Test with a WordPress Installation

If you have WordPress installed, navigate to your WordPress directory and check the installation:

cd /var/www/html
wp core version

Output:

6.4.2

This confirms WP-CLI can successfully communicate with your WordPress installation.

Common Issue: If you get “Error: This does not seem to be a WordPress installation,” you’re either not in a WordPress directory or the path is incorrect. Make sure you’re in the root WordPress directory containing wp-config.php.

Configuring WP-CLI

WP-CLI can be configured globally or per-project using configuration files. This allows you to set default parameters and customize behavior.

Global Configuration File

Create a global config file in your home directory:

mkdir -p ~/.wp-cli
nano ~/.wp-cli/config.yml

Add basic configuration:

# ~/.wp-cli/config.yml

# Disable color output (useful for logs)
color: true

# Set default user for commands that require one
user: admin

# Quiet mode (suppress informational messages)
quiet: false

# Path to WordPress installation (optional, useful if you manage one main site)
path: /var/www/html

# Apache/Nginx modules directory
apache_modules: /usr/lib/apache2/modules

Save and exit (CTRL+X, then Y, then Enter in nano).

Project-Specific Configuration

For project-specific settings, create a wp-cli.yml file in your WordPress root directory:

cd /var/www/html
nano wp-cli.yml

Add project-specific configuration:

# /var/www/html/wp-cli.yml

# Specify the WordPress path (useful for non-standard structures)
path: wp

# Disable email sending during commands
# (prevents notification emails during bulk operations)
skip-plugins:
  - disable-emails

# Set default user for content operations
user: editor

# URL of the WordPress site (for proper link generation)
url: https://yourdomain.com

Important: The project-specific wp-cli.yml takes precedence over the global ~/.wp-cli/config.yml file.

Useful Configuration Options

Here are some additional configuration options you might find useful:

# Require confirmation for destructive operations
require:
  - confirmation

# Set custom command directory for your own commands
require:
  - /path/to/custom-commands.php

# HTTP request timeout (default: 30 seconds)
http-timeout: 60

# Set debug mode
debug: false

Learn more about configuration in the official WP-CLI config documentation.

Setting Up Command Aliases

WP-CLI aliases let you create shortcuts for frequently-used commands, making your workflow more efficient.

Creating Bash Aliases

Add these to your ~/.bashrc or ~/.bash_aliases file:

nano ~/.bashrc

Add these useful aliases at the end of the file:

# WP-CLI Aliases
alias wpcli='wp'
alias wpv='wp core version'
alias wpu='wp core update'
alias wppu='wp plugin update --all'
alias wptu='wp theme update --all'
alias wpdb='wp db export'
alias wpsearch='wp search-replace'
alias wpflush='wp cache flush'
alias wplist='wp plugin list'

Save and reload your bash configuration:

source ~/.bashrc

Now you can use shortcuts like:

wpv          # Check WordPress version
wppu         # Update all plugins
wpflush      # Clear cache

WP-CLI Native Aliases

WP-CLI also supports its own alias system for remote sites. Edit your config file:

nano ~/.wp-cli/config.yml

Add site aliases:

# ~/.wp-cli/config.yml

# Define site aliases
@production:
  ssh: user@production-server.com/var/www/html

@staging:
  ssh: user@staging-server.com/var/www/staging

@local:
  path: /var/www/html

Now you can run commands on remote sites:

# Update plugins on production
wp @production plugin update --all

# Export database from staging
wp @staging db export

# Check version on local
wp @local core version

This is incredibly powerful for managing multiple WordPress installations. Read more about WP-CLI aliases in the official handbook.

Updating WP-CLI

WP-CLI should be updated regularly to get new features, bug fixes, and security patches.

Check for Updates

wp cli check-update

Update to Latest Stable Version

wp cli update

Update to Nightly Build (Unstable)

For testing or if you need bleeding-edge features:

wp cli update --nightly

Warning: The nightly build may be unstable. Only use it for development/testing environments.

Verify New Version

After updating, confirm the new version:

wp cli version

Update Frequency

• Production servers: Update monthly or when security patches are released
• Development/staging: Update whenever a new stable version is available
• Check release notes: Review WP-CLI GitHub releases before updating production

Troubleshooting Common Issues

Issue 1: “wp: command not found”

Problem: After installation, running wp returns “command not found.”

Solutions:

1. Verify the file is in your PATH:

which wp

2. If nothing is returned, the file might not be in /usr/local/bin. Check if that directory is in your PATH:

echo $PATH

3. If /usr/local/bin isn’t in your PATH, add it to ~/.bashrc:

echo 'export PATH=$PATH:/usr/local/bin' >> ~/.bashrc
source ~/.bashrc

4. Alternatively, move wp to /usr/bin instead:

sudo mv /usr/local/bin/wp /usr/bin/wp

Issue 2: “Failed to get PHP binary path”

Problem: WP-CLI can’t find the PHP binary.

Solution: Specify the PHP binary path explicitly:

wp --path=/usr/bin/php8.1 core version

Or add it to your config file:

# ~/.wp-cli/config.yml
php: /usr/bin/php8.1

Find your PHP binary path:

which php

Issue 3: Permission Denied Errors

Problem: WP-CLI commands fail with permission errors.

Solutions:

1. Run commands as the web server user (usually www-data on Ubuntu/Debian):

sudo -u www-data wp plugin list

2. Or adjust file ownership:

sudo chown -R www-data:www-data /var/www/html

Important: Never run WP-CLI as root in production. Always use the appropriate web server user.

Issue 4: “This does not seem to be a WordPress installation”

Problem: WP-CLI doesn’t recognize your WordPress installation.

Solutions:

1. Ensure you’re in the WordPress root directory containing wp-config.php:

ls -la wp-config.php

2. If WordPress is in a subdirectory, specify the path:

wp --path=/var/www/html/wordpress core version

3. Or set the path in your config file (see Configuring WP-CLI section).

Issue 5: Memory Limit Errors

Problem: Commands fail with “Allowed memory size exhausted” errors.

Solution: Increase PHP memory limit:

php -d memory_limit=512M /usr/local/bin/wp plugin update --all

Or permanently increase it in php.ini:

sudo nano /etc/php/8.1/cli/php.ini

Find and modify:

memory_limit = 512M

Restart PHP if needed:

sudo systemctl restart php8.1-fpm

Need More Help?

• Official WP-CLI Documentation
• WP-CLI GitHub Issues
• WordPress Stack Exchange
• WP-CLI Community Slack

Next Steps

Now that WP-CLI is installed and configured, you’re ready to start managing WordPress from the command line!

Essential Commands to Learn Next

1. 20 Essential WP-CLI Commands Every WordPress Developer Should Know – Master the most important commands
2. WP-CLI Config Files: Best Practices – Advanced configuration techniques
3. Automate WordPress Backups with WP-CLI – Build your first automation script

Recommended Learning Path

Week 1: Practice basic commands

• wp core version, wp plugin list, wp theme list
• Learn wp help [command] to explore documentation

Week 2: Database operations

• Export/import databases: wp db export, wp db import
• Search and replace: wp search-replace

Week 3: Automation basics

• Write simple bash scripts using WP-CLI
• Set up cron jobs for automated tasks

Week 4: Advanced techniques

• Custom WP-CLI commands
• Integration with deployment pipelines

Join the WPCLI Mastery Community

Want to master WordPress automation and save 10+ hours per week?

Join our free email course and get:

• Free WordPress backup automation script
• Weekly WP-CLI tips and tricks
• Early access to WPCLI Mastery course ($99 early bird pricing)

Conclusion

Installing WP-CLI on Ubuntu and Debian is straightforward and takes less than 10 minutes. Once installed, you’ll have a powerful tool that can save you hours of manual WordPress administration work.

The key steps we covered:

1. Download the WP-CLI Phar file
2. Make it executable and move to system PATH
3. Verify installation with wp --info
4. Configure global and project-specific settings
5. Set up command aliases for efficiency
6. Keep WP-CLI updated regularly

With WP-CLI installed, you’re now equipped to manage WordPress sites like a DevOps professional. The commands you learn will compound over time—what takes hours in the WordPress admin panel can often be done in seconds with WP-CLI.

Ready to level up? Check out our complete WP-CLI command reference or start automating your WordPress backups.

Have questions about installing WP-CLI? Drop a comment below, and I’ll help you troubleshoot!

Share this guide with other WordPress developers who could benefit from WP-CLI.

The post How to Install and Configure WP-CLI on Ubuntu/Debian (2025 Complete Guide) appeared first on WP-CLI Mastery.