currently every deploy that I'm making of this form:
wispctl deploy -p dist/ -s atvouch.dev
asks both for:
- handle for deployment
- full oauth flow for my handle
I can see there's a --store <path> argument to wispctl deploy, but it may be more useful to keep state somewhere else automatically e.g ~/.config/wispctl/state.sqlite? could key handles by the current directory so you could login to multiple accounts on separate folders for their respective deployments
this is not required as part of this suggestion, but if the oauth tokens made by wispctl could be a full superset of all the operations wispctl needs (all the records needing to be read/written) that would be an UX boost since people wouldn't have to continuously re-login
i actually had it working fine when it was written in rust and then kept continuously forgetting to fix it after porting. an annoying issue is that the reference pds only gives refresh tokens that last 24 hours to 127.0.0.1. Keying by directory is pretty smart