craft-cli / cli
Command line interface for Craft CMS
Installs: 21 938
Dependents: 2
Suggesters: 0
Security: 0
Stars: 136
Watchers: 3
Forks: 12
Open Issues: 4
Requires
- composer/ca-bundle: ^1.0
- craft-cli/base-command: ~0.0
- craft-cli/bootstrap: ^0.2.0
- psy/psysh: ~0.5.1
- symfony/console: ~2.7|~3.0
- symfony/event-dispatcher: ~2.7|~3.0
- symfony/process: ~2.7|~3.0
- vlucas/phpdotenv: ~2.4
- xamin/handlebars.php: 0.10.*
- dev-master
- 0.17.5
- 0.17.4
- 0.17.3
- 0.17.2
- 0.17.1
- 0.17.0
- 0.16.0
- 0.15.2
- 0.15.1
- 0.15.0
- 0.14.3
- 0.14.2
- 0.14.1
- 0.14.0
- 0.13.2
- 0.13.1
- 0.13.0
- 0.12.0
- 0.11.1
- 0.11.0
- 0.10.0
- 0.9.2
- 0.9.1
- 0.9.0
- 0.8.1
- 0.8.0
- 0.7.3
- 0.7.2
- 0.7.1
- 0.7.0
- 0.6.2
- 0.6.1
- 0.6.0
- 0.5.0
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.1
- 0.3.0
- 0.2.5
- 0.2.4
- 0.2.3
- 0.2.2
- 0.2.1
- 0.2.0
- 0.1.10
- 0.1.9
- 0.1.8
- 0.1.7
- 0.1.6
- 0.1.5
- 0.1.4
- 0.1.3
- 0.1.2
- 0.1.1
- 0.1.0
- 0.0.1
- 0.0.0
- dev-develop
This package is auto-updated.
Last update: 2024-11-29 04:46:42 UTC
README
Command line interface for Craft CMS.
Installation
If you are on Mac, you should install via Homebrew.
brew tap rsanchez/homebrew-craft-cli
brew install craft-cli
Otherwise, you should download the phar: https://github.com/rsanchez/craft-cli/releases/latest
php craft.phar <your:command>
See Composer Installation for alternate ways to install.
Usage
If you are using a multi-environment config, you must specify your environment either using the --environment=
flag on your commands, or set the CRAFT_ENVIRONMENT
env variable.
craft --environment="mysite.dev" show:config
CRAFT_ENVIRONMENT="mysite.dev" craft show:config
Craft CLI is dotenv aware, and will automagically load environment variables from a .env
file in your project root (path can be customised via .craft-cli.php
). You may set your Craft environment by setting a CRAFT_ENVIRONMENT
variable in your .env
file.
Commands
assets:pull
assets:push
clear:cache
console
db:backup
db:create
db:pull
db:push
db:restore
download
generate:command
help
init
install
install:plugin
list
rebuild:searchindexes
run:tasks
show:config
tail
update:assetsindexes
Assets Pull
Pull Asset files from a remote environment.
craft assets:pull --ssh-host=your.remote.server.com --ssh-user=yourUserName yourRemoteEnvironmentName
Assets Push
Push Asset files to a remote environment
craft assets:push --ssh-host=your.remote.server.com --ssh-user=yourUserName yourRemoteEnvironmentName
Clear Cache
Clear all Craft caches.
craft clear:cache
Select which cache(s) to clear from an interactive list.
craft clear:cache -s
Console
Start an interactive shell.
craft console
DB Backup
Backup your database to craft/storage/backups
.
craft db:backup
Backup your database to the specified path.
craft db:backup ./backup.sql
DB Create
Create a database
craft db:create --host=localhost --port=3306 --name=yourDbName --user=yourUserName --password=yourPassword
DB Pull
Pull a remote database to the local database.
craft db:pull --ssh-host=your.remote.server.com --ssh-user=yourUserName --force yourRemoteEnvironmentName
DB Push
Push your local database to a remote database.
craft db:push --ssh-host=your.remote.server.com --ssh-user=yourUserName --force yourRemoteEnvironmentName
DB Restore
Restore the database from the most recent backup from craft/storage/backups
.
craft db:restore --force
Restore the database from the specified .sql
file.
craft db:restore --force ./backup.sql
Download Craft
Download Craft to the current directory.
craft download
Create the specified directory and download Craft into it.
craft download path/to/directory
Generate Command
Generate a custom command file in the specified directory.
craft generate:command your:custom_command ./commands/
Generate a custom command file with a namespace.
craft generate:command --namespace="YourSite\Command" your:custom_command ./src/YourSite/Command/
Generate a custom command with arguments and options.
craft generate:command --options --arguments your_command ./commands/
Help
Display information about a command and its arguments/options.
craft help <command>
Init
Create an .craft-cli.php
config file in the current directory
craft init
This config file is only necessary if you if you are using Custom Commands or have renamed your craft
folder.
Install Craft
Download and install Craft to the current directory.
craft install
Create the specified directory and install Craft into it.
craft install path/to/directory
Install Plugin
Install a plugin from a GitHub repository.
craft install:plugin pixelandtonic/ElementApi
List
List the available commands.
craft list
Rebuild Search Indexes
craft rebuild:searchindexes
Run Tasks
Run all pending tasks.
craft run:tasks
Reset "running" (stalled) tasks and then run all tasks.
craft run:tasks --reset-running
Reset failed tasks and then run all tasks.
craft run:tasks --reset-failed
Show Config
Show all config items.
craft show:config
Show the specified config item.
craft show:config db.user
Tail
Show a tail of craft.log
craft tail
Update Asset Indexes
craft update:assetsindexes
Configuration
Craft CLI can be configured in two ways. You may use the craft init
command to generate a .craft-cli.php
file. Or, if you have installed Craft CLI via composer, you may add an extra
object to your composer.json
and a craft-cli
object within the extra
object:
{
"extra": {
"craft-cli": {
"commandDirs": {
"\\Your\\Namespace": "path/to/commands/"
}
}
}
}
Custom Commands
Craft CLI custom commands are Symfony Console Command objects. You can add custom commands to your .craft-cli.php
or composer.json
config by adding a namespace and folder path to the commandDirs
object.
You can generate a custom command file using the craft generate:command
command.
Troubleshooting
Your command-line PHP cannot connect to MySQL
You can test this by running this at the command line (change the DB credentials to your actual credentials):
php -r "var_dump(@mysql_connect('hostname', 'username', 'password', 'database_name'));"
If this prints false, then you know that your CLI PHP is not configured to connect to your database. This is frequently caused by an incorrect default MySQL socket setting.
If you are running MAMP, for instance, and are using the stock Mac OS command-line PHP, you will not be able to connect out-of-the-box. You will need to edit your /etc/php.ini
(or wherever your php.ini file is located) file and change the mysql.default_socket
and/or the mysqli.default_socket
to /Applications/MAMP/tmp/mysql/mysql.sock
.
Composer Installation
You can install globally:
composer global require craft-cli/cli
Make sure your global composer installation is added to your PATH in your ~/.bash_profile
(or ~/.profile
or ~/.bashrc
or ~/.zshrc
) so that you may run the binary from the command line:
export PATH=~/.composer/vendor/bin:$PATH
Or, you can install on a per project basis, rather than globally to your host system.
composer require craft-cli/cli
Then the command would be found in your vendor/bin
folder, so you'd run this at your command line:
vendor/bin/craft <your:command>