Config
Config Edit
wp config edit
Launches system editor to edit the wp-config.php file.
OPTIONS
[--config-file=<path>] : Specify the file path to the config file to be edited. Defaults to the root of the WordPress installation and the filename "wp-config.php".
EXAMPLES
# Launch system editor to edit wp-config.php file
$ wp config edit
# Edit wp-config.php file in a specific editor
$ EDITOR=vim wp config edit
GLOBAL PARAMETERS
These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.
| Argument | Description | 
|---|---|
| --path=<path> | Path to the WordPress files. | 
| --url=<url> | Pretend request came from given URL. In multisite, this argument is how the target site is specified. | 
| --ssh=[<scheme>:][<user>@]<host|container>[:<port>][<path>] | Perform operation against a remote server over SSH (or a container using scheme of "docker", "docker-compose", "docker-compose-run", "vagrant"). | 
| --http=<http> | Perform operation against a remote WordPress installation over HTTP. | 
| --user=<id|login|email> | Set the WordPress user. | 
| --skip-plugins[=<plugins>] | Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded. | 
| --skip-themes[=<themes>] | Skip loading all themes, or a comma-separated list of themes. | 
| --skip-packages | Skip loading all installed packages. | 
| --require=<path> | Load PHP file before running the command (may be used more than once). | 
| --exec=<php-code> | Execute PHP code before running the command (may be used more than once). | 
| --context=<context> | Load WordPress in a given context. | 
| --[no-]color | Whether to colorize the output. | 
| --debug[=<group>] | Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help. | 
| --prompt[=<assoc>] | Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values. | 
| --quiet | Suppress informational messages. |