Global parameters (WP-CLI): verschil tussen versies

Uit De Vliegende Brigade
Naar navigatie springen Naar zoeken springen
Regel 1: Regel 1:
 
== Global parameters ==
 
== Global parameters ==
  
Ik herhaal de ''global parameters'' niet in elke helptekst. Daarom hierbij:
+
Global parameters are not included at each command, but only here:
  
 
<pre>
 
<pre>
Regel 50: Regel 50:
 
== --debug ==
 
== --debug ==
  
De optie <code>--debug</code> toont debugging-informatie gedurende de executie van het WP-CLI-commando. Als het betreffende WP-CLI commando klaar is, ga je weer terug naar het gewone terminalscherm. Ik heb de indruk dat deze optie niet geschikt is als je gedurende executie van bv. een groot script, globaal op de hoogte gehouden wilt worden omtrent de voortgang.
+
The <code>--debug</code> option displays debugging information during the execution of the WP-CLI command. When the respective WP-CLI command has finished, you will return to the normal terminal screen. I have the impression that this option is not suitable if you want to be kept globally informed about the progress during the execution of, for example, a large script.
  
Je kunt aangeven om welke groep van debug-informatie het gaat. Ik denk dat je dat vanzelf ziet als je deze optie eerst zonder waarde gebruikt. De waardes die ik zo snel voorbij zag komen (onderbreek exectie met Ctrl-C, anders gaat 't vermoedelijk te snel):
+
You can specify which group of debug information it concerns. I think you'll see that automatically if you use this option with no value first. The values I saw passing by so quickly (interrupt execution with Ctrl-C, otherwise it will probably go too fast):
  
 
* bootstrap
 
* bootstrap
Regel 58: Regel 58:
 
* hooks
 
* hooks
  
Voorbeelden:
+
Examples:
 
 
 
<pre>
 
<pre>
 
# Toon alle debug-informatie
 
# Toon alle debug-informatie

Versie van 28 sep 2022 11:40

Global parameters

Global parameters are not included at each command, but only here:

GLOBAL PARAMETERS

--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",
    "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).

--[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.

--debug

The --debug option displays debugging information during the execution of the WP-CLI command. When the respective WP-CLI command has finished, you will return to the normal terminal screen. I have the impression that this option is not suitable if you want to be kept globally informed about the progress during the execution of, for example, a large script.

You can specify which group of debug information it concerns. I think you'll see that automatically if you use this option with no value first. The values I saw passing by so quickly (interrupt execution with Ctrl-C, otherwise it will probably go too fast):

  • bootstrap
  • commands
  • hooks

Examples:

# Toon alle debug-informatie
########################################
#
wp option list --fields=option_name --debug


# Toon alleen commands-debug-informatie
########################################
#
wp option list --fields=option_name --debug=commands

-path

I don't get --path to work. E.g., none of this works:

cd ~
wp plugin status /var/www/example.com
wp plugin status /var/www/example.com/

wp plugin status "/var/www/example.com"
wp plugin status "/var/www/example.com/"

wp plugin status '/var/www/example.com'
wp plugin status '/var/www/example.com/'

wp plugin status `/var/www/example.com`
wp plugin status `/var/www/example.com/`

Sources: