-
Notifications
You must be signed in to change notification settings - Fork 18
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
Change README file to better help users with available commands #208
Comments
I just submitted #209 But, in looking closer at Should we just try and keep the README up to date? If so, what other commands should be listed? |
bcex, bcim, bp, dlb, en, dis, pml |
ctl |
@serundeputy - What is |
I've updated the PR with all suggestions except ctl and reorganized them in groupings/order that make sense to me (the best criteria), happy to hear feedback on alternative organization of the list. |
You want drush help ctl |
ctl is only available in >= 1.1.0 |
So, I'm working with Lando and the following default recipe:
How do I tell it to use Drush 1.1.0? |
I think pmu works too |
In the config section add backdrush: 1.1.0 |
Thanks. I had to destroy and restart lando environment (rebuild did not work). But, I got it working. |
OK, finally finished making a change before you managed to suggest another addition! ;-) |
merged: #209 |
I am one of those "developers" that seldom uses the
help
option for commands when using the CLI. I should make better use of this resource, but in the past as I was getting started, this page often just confused me.I tend to look at the list of available commands on the README file for drush and forget that there are apparently many more commands supported.
I think it would be great if we kept a full list of commands in the README file, but at a minimum I am going to suggest a clear adding a clear instruction to users to check the
help
page for more options.I will submit a PR to this effect (and it will include adding two more favorites of mine to the README, without being comprehensive). I would be happy for someone to edit this PR or write a new one. Also, I will be happy to revise this PR based upon feedback.
The text was updated successfully, but these errors were encountered: