-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Missing ddev poser
in DDEV, when using README instructions
#58
Conversation
Following the instructions, butting the error: >> Error: unknown command "poser" for "ddev" >> Run 'ddev --help' for usage. Fix it by adding project type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know why this problem happens sometimes to some people; It's a result of code not being discovered and the project type not being discovered from the code I guess. But this approach of specifying the project type is certainly a way around it. but composer is going to have to create that code at some point.
Co-authored-by: Randy Fay <[email protected]>
@rfay thanks, that makes sense. I had this issue twice, so I though would be good to specify it, as it doesn't hurt in general. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be fine.
It would be good to chase this down @elaman and try to figure out what actually happens in the case you and others have encountered. See if you can reproduce it. DDEV defaults to the php
project type when it doesn't discover code that it recognizes as Drupal code.
However,
(which isn't in a release yet, hint hint @weitzman ) would also solve the problem you had.
What was going on was that the special commands added by this add-on were only valid for drupal*
project type, but that wasn't that useful a distinction anyway.
ddev poser
in DDEV, when using README instructions
I made a release so this superflous now. |
Thanks for the release. However, the problem of wrong project type ( |
This project shows its command for all project types now, so fixing it is no longer in scope, i think. You could move this issue to another project if desired. |
The Issue
Following the instructions, butting the error:
How This PR Solves The Issue
Fix it by adding --project-type option.
Manual Testing Instructions
Follow the instruction defined in the readme.