You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
Definitely something I'd like to do/consider. In #55 I made it so Drupal VM can create a set of Drush aliases for configured Drupal sites (based on the configured vhosts); for Drupal Console, how do you tell the console where your drupal sites live?
Is it based on the current working directory only, or is there some sort of aliasing system?
I noticed hechoendrupal/drupal-console#515 mentions a ~/.console/config.yml file (yay YAML!), but there's no mention in the docs of how to run arbitrary console commands on different Drupal installations...?
@geerlingguy DrupalConsole does not support site aliases out of the box now, but I spent a couple of days working with Greg Anderson on a console/drush integration the result was several updates to Console and this PR to drush:
I've added a new Ansible Galaxy role, geerlingguy.drupal-console, which installs Drupal Console and aliases it properly. Local testing seems good to go, so I'm going to push out an update soon, and then you can ssh into the VM (with vagrant ssh) and drupal away!
The only thing that's not working yet is self-updating Drupal Console, but hopefully that will get resolved upstream in hechoendrupal/drupal-console#615 soon.
http://drupalconsole.com/
The text was updated successfully, but these errors were encountered: