docs
created pr with
63.1
added 63.2
-: ------- > 1: 5ea2b3a lgtm
1: 6429512 ! 2: fc5db9c docs: rewrite api-token page
-: ------- > 3: 5ea2b3a chore: add token tui img
changed status to
accepted
cmds
checkout latest patchset:
ssh pr.pico.sh print 63 | git am -3checkout any patchset in a patch request:
ssh pr.pico.sh print 63.[rev] | git am -3add changes to patch request:
git format-patch main --stdout | ssh pr.pico.sh pr add 63set PR to open (enables RSS notifications):
ssh pr.pico.sh pr open 63set PR to draft (stops RSS notifications):
ssh pr.pico.sh pr draft 63
Patchset
63.2
docs: rewrite api-token page
Noelle Leigh
2025-04-13T16:51:44Z* Capitalized example items * Added Usage header * Rewrote usage steps to be ordered, and reflect the new TUI
Semantic diff summary
0 added,
0 modified,
0 signature changed,
0 removed
across 0 analyzed files
(1 file skipped: unsupported file type)
+11
-8
posts/api-token.md
#
| ... | ... | @@ -7,13 +7,16 @@ API tokens are used for when we cannot leverage SSH pubkey authentication. | |
| 7 | 7 | ||
| 8 | 8 | Common examples: | |
| 9 | 9 | ||
| 10 | - | - account recovery | |
| 11 | - | - [connecting to our bouncer](/irc) | |
| 12 | - | - pico+ rss feed | |
| 10 | + | - Account recovery | |
| 11 | + | - [Connecting to our IRC bouncer](/irc) | |
| 12 | + | - Pico+ rss feed | |
| 13 | 13 | ||
| 14 | - |  | |
| 14 | + |  | |
| 15 | 15 | ||
| 16 | - | - SSH into our [pico TUI](/ui#ssh-tui) | |
| 17 | - | - Select "Manage Tokens" submenu | |
| 18 | - | - Type "n" to generate a new token | |
| 19 | - | - Save token someplace safe | |
| 16 | + | ## Usage | |
| 17 | + | ||
| 18 | + | 1. SSH into our [pico TUI](/ui#ssh-tui) | |
| 19 | + | 2. Select "tokens" submenu | |
| 20 | + | 3. Type <kbd>c</kbd> to generate a new token | |
| 21 | + | 4. Give it a descriptive name | |
| 22 | + | 5. Copy the generated token string to where you want to use it |