ee shell

Brings up a shell to run wp-cli, composer etc.

SYNOPSIS

ee shell [<site-name>] [--user=<user>] [--service=<service>] [--command=<command>]

OPTIONS

[<site-name>]
: Name of website to run shell on. If omitted, EasyEngine uses the site whose folder you’re in.

[--user=<user>]
: Set the user to exec into shell.

[--service=<service>]
: Set the service whose shell you want.
Default: php

[--command=<command>]
: Command to non-interactively run in the shell.

EXAMPLES

# Open shell for site
$ ee shell example.com

# Open shell with root user
$ ee shell example.com --user=root

# Open shell for some other service
$ ee shell example.com --service=nginx

# Run command non-interactively
$ ee shell example.com --service=nginx --command='nginx -t && nginx -s reload'

GLOBAL PARAMETERS

--sites_path=<path>
    Absolute path to where all sites will be stored.

--locale=<locale>
    Locale for WordPress.

--le-mail=<le-mail>
    Mail-id to be used for letsencrypt.

--env=<env>
    EasyEngine server environment.

--wp-mail=<wp-mail>
    Default Mail-id to be used for WordPress site installation.

--sysctl=<true/false>
    Whether to add sysctl config in docker-compose.

--skip-tty=<true/false>
    Skip tty allocation for remote command execution.

--custom-compose=<custom-compose file>
    Path to custom compose file.

--[no-]color
    Whether to colorize the output.

--debug[=<group>]
    Show all PHP errors; add verbosity to EE bootstrap.

--quiet
    Suppress informational messages.