jonpugh / ash
Global CLI for managing sites using Consolidation Site Aliases.
Installs: 1 067
Dependents: 0
Suggesters: 0
Security: 0
Stars: 8
Watchers: 1
Forks: 0
Open Issues: 2
Requires
- consolidation/robo: ^4.0
- consolidation/site-alias: ^4.0
- consolidation/site-process: ^5.2
README
A global CLI to list sites and run commands on them. Very similar to global drush site:alias
command.
Overview
This project is a global cli designed to run commands against multiple sites using Consolidation's Site Aliases.
This is a possible replacement for global Drush.
Commands
site
site:exec [e] Run a command against a site (in the root directory.)
site:get [get] Show contents of a single site alias.
site:list [sl|ls] List available site aliases.
site:value Access a value from a single alias.
site-spec
site-spec:parse Parse a site specification.
Alias syntax
For simpler access to the site:exec
command, you can use the alias syntax:
ash @alias command-to-execute
History
This tool was built from the ashes of a small tool created by the consolidation/site-alias
team called alias-tool.
It was inspired by the need to retire global drush.
Installation
Ash is a CLI designed to run globally, but can be installed in a composer project as well. Here are 3 options for installing:
-
Site local
composer require
composer require jonpugh/ash`
-
Composer Global require command and add to PATH:
-
Run the following command to install
ash
to your user's global composer directory:composer global require jonpugh/ash
-
To make
ash
available globally, set the PATH variable:export PATH="~/$COMPOSER_HOME/vendor/bin:$PATH"
Put this in your
~/.bashrc
or similar file.
Notes:
-
This will install a
composer.json
file to the globalCOMPOSER_HOME
directory. -
The bin scripts will be installed in
$COMPOSER_HOME/vendor/bin
. -
Your
COMPOSER_HOME
may vary. Refer to thecomposer global --help
command for more information aboutCOMPOSER_HOME
. -
From
composer global --help
:You can use this to install CLI utilities globally, all you need is to add the COMPOSER_HOME/vendor/bin dir to your PATH env var. COMPOSER_HOME is c:\Users<user>\AppData\Roaming\Composer on Windows and /home/<user>/.composer on unix systems. If your system uses freedesktop.org standards, then it will first check XDG_CONFIG_HOME or default to /home/<user>/.config/composer Note: This path may vary depending on customizations to bin-dir in composer.json or the environmental variable COMPOSER_BIN_DIR. Read more at https://getcomposer.org/doc/03-cli.md#global ```
-
-
Source install.
For development, install the source, and if desired, set a symlink to make
ash
available globally.git clone git@github.com:jonpugh/ash.git cd ash composer install sudo ln -s $PWD/ash /usr/local/bin/ash
-
Phar install.
Coming Soon.
Setup
Once the ash
command works, you need to tell it where your sites are. You can create alias files manually, or use the site:add
command.
ash site:add
This command makes it easy to add new global site aliases.
To use, run ash site:add
in the directory to your Drupal site. (@todo: allow adding from any directory)
If your site has the file ./drush/sites/self.yml
, these aliases will be included in the global alias list.
Configuration
See ash.yml for default config:
# Copy this file to ~/.ash/ash.yml if overriding is needed. ash: alias_directories: - "${env.HOME}/.ash"
Put alias files in one of the directories defined in alias_directories
.
Remember to name the files $APP.site.yml
instead of self.site.yml
See Drush Site Alias Documentation for details on how to create alias files.
Usage
Given you have added the example file examples/operations.site.yml to $HOME/.ash/operations.site.yml
, you can run the following commands:
List all aliases
# List all aliases from global config (~/.ash/*) $ ash ls '@ash.operations.local': root: /home/jonpugh/Work/Operations/operations/web uri: 'https://operations.lndo.site' env: HOME: /home/jonpugh '@ash.operations.mars': root: /home/jonpugh/Work/Operations/operations/web uri: 'https://mars.lndo.site' env: HOME: /home/jonpugh
List site local aliases.
If you are running ash
from a drupal codebase, it will detect and load all aliases in the drush/sites
folder.
# List all aliases from a specific site. $ cd path/to/myproject $ ash ls '@self.prod': host: sites.watch user: platform root: /var/platform/projects/siteswatch/prod uri: 'https://sites.watch' $ ash exec @self.prod drush status
These aliases are also compatible with drush.
Run a command on the site
The main ash site:exec
command uses SiteAlias
& SiteProcess
, so commands will automatically be run on the remote server via SSH. See additional options at https://www.drush.org/12.x/site-aliases/#additional-site-alias-options
Docker-compose aliases can also be used. https://www.drush.org/12.x/site-aliases/#docker-compose-and-other-transports)
# Execute a command in the site's folder, on the site's server. $ ash exec @self.prod drush status Drupal version : 9.5.10 Site URI : http://default PHP binary : /usr/bin/php8.1 PHP config : /etc/php/8.1/cli/php.ini PHP OS : Linux PHP version : 8.1.20
If options are needed, use the --
as divider between ash
command and target command.
$ ash exec @ash.operations.live -- drush wd-tail --extended
Ash aliases are drush aliases, so this is an equivalent command:
$ drush @ash.operations.live wd-tail --extended
@TODO
- Allow aliases to only contain name.environment. Currently all aliases get
@ash
pre-pended. - Allow syntax
ash @alias command
instead ofash site:exec @alias command
. Need to find out how drush processes argv to set current alias.
Contributing
Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.
Versioning
We use SemVer for versioning. For the versions available, see the releases page.
Authors
- Jon Pugh
- Greg Anderson - Original
alias-tool
script and command files.
See also the list of contributors who participated in this project. Thanks also to all of the drush contributors who contributed directly or indirectly to site aliases.
License
This project is licensed under the MIT License - see the LICENSE file for details