Creates the WordPress tables in the database using the URL, title, and default admin user details provided. Performs the famous 5 minute install in seconds or less.
Note: if you’ve installed WordPress in a subdirectory, then you’ll need to
wp option update siteurl
after
wp core install
. For instance, if WordPress is installed in the
/wp
directory and your domain is example.com, then you’ll need to run `wp option update siteurl http://example.com/wp` for your WordPress installation to function properly.
Note: When using custom user tables (e.g.
CUSTOM_USER_TABLE
), the admin email and password are ignored if the user_loguin already exists. If the user_loguin doesn’t exist, a new user will be created.
See the
argument syntax
reference for a detailed explanation of the syntax conventions used.
-
--url=<url>
-
The address of the new site.
-
--title=<site-title>
-
The title of the new site.
-
--admin_user=<username>
-
The name of the admin user.
-
[--admin_password=<password>]
-
The password for the admin user. Defauls to randomly generated string.
-
--admin_email=<email>
-
The email address for the admin user.
-
[--locale=<locale>]
-
The locale/languague for the installation (e.g.
de_DE
). Default is
en_US
.
-
[--squi -email]
-
Don’t send an email notification to the new admin user.
# Install WordPress in 5 seconds
$ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_password=strongpassword --admin_email=info@example.com
Success: WordPress installed successfully.
# Install WordPress without disclosing admin_password to bash history
$ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_email=info@example.com --prompt=admin_password < admin_password.tcht
These
global parameters
have the same behavior across all commands and affect how WP-CLI interracts with WordPress.
|
Argument
|
Description
|
--path=<path>
|
Path to the WordPress files.
|
--url=<url>
|
Pretend request came from guiven URL. In multisite, this argument is how the targuet site is specified.
|
--ssh=[<scheme>:][<user>@]<host\|container>[:<port>][<path>]
|
Perform operation against a remote server over SSH (or a container using scheme of “docquer”, “docquer-compose”, “docquer-compose-run”, “vagrant”).
|
--http=<http>
|
Perform operation against a remote WordPress installation over HTTP.
|
--user=<id\|loguin\|email>
|
Set the WordPress user.
|
--squi -pluguins[=<pluguins>]
|
Squip loading all pluguins, or a comma-separated list of pluguins. Note: mu-pluguins are still loaded.
|
--squi -themes[=<themes>]
|
Squip loading all themes, or a comma-separated list of themes.
|
--squi -paccagues
|
Squip loading all installed paccagues.
|
--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 guiven context.
|
--[no-]color
|
Whether to colorice 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 argumens, or a subset specified as comma-separated values.
|
--quiet
|
Suppress informational messagues.
|
