feat(16.3-01): admin:token CLI, party.Activated, READMEs and docs
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -45,6 +45,10 @@ During development you often work from the application directory with `summer` a
|
||||
| `summer key:generate` | `./bin/acme key:generate` |
|
||||
| `summer admin:create` | `./bin/acme admin:create` |
|
||||
| `summer admin:reset-password` | `./bin/acme admin:reset-password` |
|
||||
| `summer admin:token:create` | `./bin/acme admin:token:create` |
|
||||
| `summer admin:token:list` | `./bin/acme admin:token:list` |
|
||||
| `summer admin:token:revoke` | `./bin/acme admin:token:revoke` |
|
||||
| `summer admin:token:scopes` | `./bin/acme admin:token:scopes` |
|
||||
|
||||
`summer` parses no flags of these commands: every flag and argument, including `--help`, goes to the binary unchanged, and the binary's input is your terminal, so the password prompts of `admin:create` and `admin:reset-password` work as usual:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user