docs
created pr with
ps-129
added ps-130
-: ------- > 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 pr-63 | git am -3checkout any patchset in a patch request:
ssh pr.pico.sh print ps-X | 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
ps-129
docs: rewrite api-token page
Noelle Leigh
2025-04-13T16:51:44Z* Capitalized example items * Removed screenshot that showed the old TUI. I didn't replace it because I didn't want to use a different terminal style than the other screenshots. * 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)
+9
-8
posts/api-token.md
#
@@ -7,13 +7,14 @@ API tokens are used for when we cannot leverage SSH pubkey authentication.
Common examples:
-- account recovery
-- [connecting to our bouncer](/irc)
-- pico+ rss feed
+- Account recovery
+- [Connecting to our IRC bouncer](/irc)
+- Pico+ rss feed
-
+## Usage
-- SSH into our [pico TUI](/ui#ssh-tui)
-- Select "Manage Tokens" submenu
-- Type "n" to generate a new token
-- Save token someplace safe
+1. SSH into our [pico TUI](/ui#ssh-tui)
+2. Select "tokens" submenu
+3. Type <kbd>c</kbd> to generate a new token
+4. Give it a descriptive name
+5. Copy the generated token string to where you want to use it