Skip to content
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

Making composer install /vendor/bin in the usual place and providing a link for /bin. #140

Closed

Conversation

gregharvey
Copy link
Contributor

Why?

Because lots of CI expect to find tools like drush in vendor/bin, it's the composer standard. I presume Lando needs the ./bin directory to contain these tools so it can present them? This solution attempts to make that available for Lando by committing a link, while allowing composer to install things in the "usual" places.

I understand if you don't accept this, it's just a suggestion and it only took a minute to make. :-)

@gregharvey
Copy link
Contributor Author

Another option would be to fix the ddev and Lando configs (and GitHub Actions) so you don't need the composer line setting the bin dir at all?

@finnlewis
Copy link
Member

@andybroomfield just mentioned that Acquia expects it to be in /vendor/bin.

@andybroomfield
Copy link
Contributor

This is with Cloud next and cloud actions, after a call with an Acquia engineer. We're making that change to our composer.json to align with Acquia expectations, otherwise cloud actions fail as it can't find drush. As mentioned above this only affects new projects so we will need to document that change and rational for it.

@finnlewis
Copy link
Member

Closing this in favour of #143 , thanks @gregharvey

@finnlewis finnlewis closed this Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants