Pixeldust Drupal Support Service

Using Drush without local copy of Drupal, only calling site aliases – No site aliases found

We have a project which does not contain a Drupal codebase. It’s Cypress.io test with Drush 9 added using Composer. I would like to execute Drush with site alias to work with the remote site while running tests.

I’m able to call Drush from Cypress test just fine. The Cypress part actually does not matter at all as the behaviour is the same when I run Drush command directly.

The setup:

  • composer init fresh project
  • composer require drush/drush
✔ rk:/tmp/drushtest> vendor/bin/drush version  Drush version : 9.7.1 ✔ rk:/tmp/drushtest> vendor/bin/drush sa --debug  [preflight] Config paths: /tmp/drushtest/vendor/drush/drush/drush.yml  [preflight] Alias paths:   [preflight] Commandfile search paths: /tmp/drushtest/vendor/drush/drush/src  [bootstrap] Starting bootstrap to none [0.09 sec, 7.33 MB]  [bootstrap] Drush bootstrap phase 0 [0.09 sec, 7.34 MB]  [bootstrap] Try to validate bootstrap phase 0 [0.09 sec, 7.34 MB]  [success] No site aliases found. [0.09 sec, 7.36 MB]
  • Already there is nothing in Alias paths.
  • Added some drush aliases to drush/sites/remoteproject.site.yml (valid yml file that is working in the Drupal project)
  • While debugging this I tried to add a drush.yml config file to point drush to the alias.
✔ rk:/tmp/drushtest> tree . ├── composer.json ├── composer.lock ├── drush │   └── sites │       └── remoteproject.site.yml ├── drush.yml └── vendor     ├── ...  ✔ rk:/tmp/drushtest> cat drush.yml  drush:   paths:     alias-path:       - drush/sites/remoteproject.site.yml  ✔ rk:/tmp/drushtest> vendor/bin/drush sa --debug --config=drush.yml  [preflight] Config paths: /tmp/drushtest/drush.yml,/tmp/drushtest/vendor/drush/drush/drush.yml  [preflight] Alias paths: drush/sites/remoteproject.site.yml  [preflight] Commandfile search paths: /tmp/drushtest/vendor/drush/drush/src  [bootstrap] Starting bootstrap to none [0.08 sec, 7.34 MB]  [bootstrap] Drush bootstrap phase 0 [0.08 sec, 7.34 MB]  [bootstrap] Try to validate bootstrap phase 0 [0.08 sec, 7.34 MB]  [success] No site aliases found. [0.08 sec, 7.37 MB]

So I convinced Drush to see the site alias file, but the alias itself is not loading.

When I try to use the alias:

✔ rk:/tmp/drushtest> vendor/bin/drush @remoteproject.remotesite.dev status -debug --config=drush.yml  [preflight] The alias @remoteproject.remotesite.dev could not be found.

Is this conceptually wrong? (Having only Drush and calling remote site using site alias.) Am I just missing some option? Or is this ready to be “promoted” to Github bug report / feature request?

Thanks!

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.

Let's Talk About a 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

Using Drush without local copy of Drupal, only calling site aliases – No site aliases found

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.
MASTER YOUR DRUPAL SEO
Pixeldust and Pantheon Drupal Development
256