The following command line utilities support a development workflow, including version control, code generation and templates, and API CLI's.
It is assumed that you already have git installed.
Confirm that the install location is in your
export INSTALL_PATH='/usr/local/bin' # download install-composer.php: wget -q 'https://getcomposer.org/installer' -O 'install-composer.php' # install: verify install-composer.php php install-composer.php --install-dir=$(INSTALL_PATH) --filename=composer
Confirm the install by running composer on the command line and you should see:
mzd☯ artichoke :>composer ______ / ____/___ ____ ___ ____ ____ ________ _____ / / / __ \/ __ `__ \/ __ \/ __ \/ ___/ _ \/ ___/ / /___/ /_/ / / / / / / /_/ / /_/ (__ ) __/ / \____/\____/_/ /_/ /_/ .___/\____/____/\___/_/ /_/ Composer version 1.8.4 2019-02-11 10:52:10 Usage: command [options] [arguments]
Download the PHP Archive. A CLI HTTP client like curl or wget is recommended.
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
Copy the archive to a location in your
mv wp-cli.phar /usr/local/bin/wp
And verify the install
Download and put
cv somewhere in your
curl -O https://download.civicrm.org/cv/cv.phar chmod ugo+x cv.phar mv cv.phar /usr/local/bin/cv
In CiviCRM plugins are called, Extensions. Yet, in the civix help, extensions are called "modules". For example:
civix generate:module. (Don't ask me why, but CiviCRM was grounded in Drupal development for many years.)
Most circumstances call for extending CiviCRM by creating an extension, though other (historic) techniques also exist.
curl https://download.civicrm.org/civix/civix.phar -o /usr/local/bin/civix chmod +x /usr/local/bin/civix
Besides generating extension boilerplate, civix is often used to do the following: