summaryrefslogtreecommitdiff
path: root/.sqlx/query-c960562be5b34678c305895cc4aaa6d96ad25184042ea1f989499285d41400f8.json
diff options
context:
space:
mode:
authorOwen Jacobson <owen@grimoire.ca>2025-08-30 02:59:51 -0400
committerOwen Jacobson <owen@grimoire.ca>2025-08-30 02:59:51 -0400
commit96b62f1018641b3dc28cc189d314a1bff475b751 (patch)
tree1e10b660f2c68cb73d3c17703257ec0be51c36af /.sqlx/query-c960562be5b34678c305895cc4aaa6d96ad25184042ea1f989499285d41400f8.json
parent3bd63e20777126216777b392615dc8144f21bb9a (diff)
Allow administrators to rotate VAPID keys immediately if needed.
In spite of my design preference away from CLI tools, this is a CLI tool: `pilcrow --database-url <URL> rotate-vapid-key`. This is something we can implement here and now, which does not require us to confront the long-avoided issue of how to handle the idea that some users are allowed to make server-operational changes and some aren't, by delegating the problem back to the OS. The implementation is a little half-baked to make it easier to rip out later. I would ordinarily prefer to push both `serve` (the default verb, not actually named in this change) and `rotate-vapid-key` into their own, separate CLI submodules, with their own argument structs, but that change is much more intrusive and would make this effectively permanent. This can be yanked out in a few minutes by deleting a few lines of `cli.rs` and inlining the `serve` function. Nonetheless, nothing is as permanent as a temporary solution, so I've written at least some bare-minimum operations documentation on how to use this and what it does.
Diffstat (limited to '.sqlx/query-c960562be5b34678c305895cc4aaa6d96ad25184042ea1f989499285d41400f8.json')
0 files changed, 0 insertions, 0 deletions