How to use drush site-lists alias?

I several folders containing symlinks to my drupal sites. I’d like to use this folder structure to create an alias so I can run commands on each group of sites.

I’m trying to do what “drush @sites status” will do, but on a smaller subset.

I wrote the following based on the docs

// List the instances from the OU instances folder $full_path = "/opt/drupal/sites/instances"; if ($handle = opendir("$full_path")) {     while (false !== ($file = readdir($handle))) {         if(is_dir($full_path."/".$file)) {           if ($file != '.' && $file != '..')             $instances[] = $file;         }     } }  // Turn them into aliases so we just have to type @instance foreach ($instances as $instance) {      $site_list = [];      // Look at each instance     $site_paths = $full_path . "/" . $instance;      if ($file_handle = opendir("$site_paths")) {       // List out the folders in this instance       while (false !== ($site_folder = readdir($file_handle))) {          if(is_dir($site_paths."/".$site_folder)) {           // If the folder represents a drupal site           if ($site_folder != '.' && $site_folder != '..')             // Add it to this instances list             $site_list[] = '@' . $site_folder;         }       }     }      $aliases[$instance] = array(             'site-list' => $site_list,         ); } print_r($aliases); 

The cheeky print_r on the end shows my array as

 [partnership] => Array         (             [site-list] => Array                 (                     [0] => @www.1.co.uk                     [1] => @www.2.org                     [2] => @www.3.org.uk                     [3] => @www.4.org                     [4] => @www.5.eu                     [5] => @www.6.net                     [6] => @www.7.com                     [7] => @www.8-ri-2020.eu                     [8] => @www.9.edu                     [9] => @www.10.ac.uk                     [10] => @www.11.org                     [11] => @www.12.ac.uk                     [12] => @www.13.co.uk                     [13] => @www.14.org.uk                     [14] => @www.15.ac.uk                 )          ) 

I’ve changed the names to protect the innocent, but they are valid aliases.

When I run “drush @partnership status” I get

drush @partnership status You are about to execute 'status' non-interactively (--yes forced) on all of the following targets: Continue?  (y/n): y Invalid argument supplied for foreach() backend.inc:661  

How do I get drush to actually run through this alias list telling me the status of each site?

Sponsored by SupremePR
This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

How to use drush site-lists alias?

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.