It needs to be documented somewhere that users need to run:
drush switch:profile old_profile new_profile
As there's no README, placing this on the project page is fine.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | profile_switcher-add_documentation-3121337-9.patch | 2.19 KB | colan |
Comments
Comment #2
colanComment #3
tim-dielsThe drush command only accepts one argument so the drush command is
drush switch:profile new_profileComment #4
colanI believe that's incorrect. I used two as per the code in function profile_switcher_drush_command(). As you can see, there are two arguments there. It's possible that
profile_to_deleteisn't being used, however.This confusion is exactly why all of this needs to be documented. :)
Comment #5
joachim commentedThe documentation here is wrong:
I've fixed that, so this can possibly be closed?
Does the Drush help for the command provide enough detail?
Comment #6
colanPossibly, but folks won't *know* about the Drush command if it's not documented. Either add a README or put info on the project page.
The command that worked for me, above, was Drush 8 (currently required for Aegir). If it runs differently for different versions of Drush, that also needs to be documented.
As there's no usage documentation whatsoever, I didn't even realize it was a Drush command. I was searching through the Web UI trying to figure out how to run the thing. I had to dig into the code to figure out it was only a Drush command. Users shouldn't have to do that.
Say it's a Drush command, and tell folks how to run it.
Comment #7
joachim commentedI've changed the project page to start with:
> This module provides a Drush command to switch between install profiles found in /profile directory.
I'll take a patch for a README :)
Comment #8
colanThanks! Here's the patch.
Comment #9
colanComment #10
colanComment #12
joachim commentedCommitted! Thanks!