vip dev-env create [options]
Create a VIP Local Development Environment
Options
Argument | Description |
---|---|
-a , --app-code | Use the application code from a local directory or use “demo” for VIP skeleton code |
-d , --debug | Activate debug output |
-e , --elasticsearch | Enable Elasticsearch (needed by Enterprise Search) |
-h , --help | Output the help for the (sub)command |
-A , --mailhog | Enable MailHog (disabled by default) |
-r , --media-redirect-domain | Domain to redirect for missing media files. This can be used to still have images without the need to import them locally. |
-u , --mu-plugins | Use a specific mu-plugins changeset or local directory |
-m , --multisite | Enable multisite install |
-H , --photon | Enable Photon. By default it is disabled. |
-P , --php | Explicitly choose PHP version to use |
-p , --phpmyadmin | Enable PHPMyAdmin component. By default it is disabled |
-s , --slug | Custom name of the dev environment |
-S , --statsd | Enable statsd component. By default it is disabled |
-t , --title | Title for the WordPress site |
-v , --version | Output the version number |
-w , --wordpress | Use a specific WordPress version |
-x , --xdebug | Enable XDebug. By default it is disabled |
-X , --xdebug_config | Extra configuration to pass to xdebug via XDEBUG_CONFIG environment variable |
Examples
# Create a local environment $ vip dev-env create # Create a local environment with the slug "my_site" # Assigning unique slugs to environments allows multiple environments to be created. $ vip dev-env create --slug=my_site # Create a local multisite dev environment with a subdirectory structure, running WP v6.2 and loading local application code from "~/git/my_code" $ vip dev-env create --multisite=subdirectory --wordpress="6.2" --app-code="~/git/my_code" # Create a local environment based on some of the settings of production environment of application "mytestsite" $ vip @mytestsite.production dev-env create
Global Options
Argument | Description |
---|---|
-a , --app=<app> | Specify the app |
-d , --debug | Activate debug output |
-e , --env=<env> | Specify the environment |
-h , --help | Output the help for the (sub)command |
-v , --version | Output the version number |
-y , --yes | Run the command in production without a confirmation prompt |
Last updated: July 03, 2023