-
Notifications
You must be signed in to change notification settings - Fork 397
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
Install BLT alias automatically for developers #284
Comments
In order to do this, we'd need to either:
|
I've been investigating how to accomplish this today. In its current form, the install-alias.sh script requires appropriate input from a prompt before it will actually install the alias. Scripts run as composer scripts do not support user input as a response to a prompt from a shell script. See composer/composer#4036. It is relatively straightforward to add a script definition to I think running |
…ate setup instructions in onboarding.md. (acquia#284).
Installing automatically causes issues in some environments, E.g., we don't want aliases installed for us on Travis CI, and some people may use tools like fish, in which case adding the alias automatically will be unwelcome. But as as compromise I've made it much simpler: I don't think we should run |
One slight thing, the same function that works in fish, causes zsh to exit to iTerm/Term or the window itself will close (if zsh is set as default shell) if blt is ran in a directory fails the conditions in the function mentioned in #662 |
When a developer clones a project repo built on the new composer-based BLT, they have to do something like this:
composer install
./vendor/bin/blt local:setup
I think we could consolidate this to automatically run the local setup as part of the composer install. We should at least install the BLT alias so they don't have to poke around the vendor directory for the BLT binary.
The text was updated successfully, but these errors were encountered: