-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drush alias #29
Comments
#29: Add `drush site-set` after site installation.
I still think this makes sense regardless of this, especially using the behat extension with its alias feature. |
I agree it makes sense, although I'm not familiar with the alias feature of the behat extension, will look into it. Ideally I was hoping to take a super simple approach to the Alias, by piping the output of 'drush sa @self' from within the site directory out to an alias file, which would get you halfway there, but the assigned alias would be 'self', which is relatively un-descriptive. The other reason I didn't go down that track is just my lack of understanding on how best to fork and test a composer based package with Travis. I did try forking, and updating the namespace for the drupal_ti, but it appears it's not as easy as that, so any advice would be appreciated. |
Forking is really simple: Just fork and then instead of:
you do something like:
drupal_ti can work from everwhere. That is the trick I use to have drupal_ti test 'itself'. |
Thanks, that's clearly obvious. I'll give it a spin shortly. |
It'd be really nice if a Drush alias was created and 'drush use'd so that interactions with the Drupal site could be done without the need of navigating the filesystem.
The text was updated successfully, but these errors were encountered: