You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know ya'll are working on the documentation but I was just trying to use the CLI as a proof of concept.
I was able to link two devices nicely, I can see them both with charm keys and the "Current Key" switches in a sensible way between the two machines.
kv commands work fine for a single machine, but I can't figure out how to share across linked accounts. charm kv sync doesn't appear to do anything for me. Am I misunderstanding the usage? Is this only the purview of skate? I saw this (charmbracelet/skate#31) and I thought that I could just use charm kv.
Thanks for the cool tools!
The text was updated successfully, but these errors were encountered:
Hi! If skate and charm kv use different default db names but you should be able to see your skate db with charm if you specify it with the "@" syntax. So for instance to list all of your skate keys with charm you need to do this: charm kv list @charm.sh.skate.default. Let us know if that works, if not we can debug further!
Today I only see one entry after deleting all the files.
I think the issue was that I kv set stuff in both machines before linking and syncing.
I'm able to share values now, I guess I just didn't do the right order of operations.
I know ya'll are working on the documentation but I was just trying to use the CLI as a proof of concept.
I was able to link two devices nicely, I can see them both with
charm keys
and the "Current Key" switches in a sensible way between the two machines.kv
commands work fine for a single machine, but I can't figure out how to share across linked accounts.charm kv sync
doesn't appear to do anything for me. Am I misunderstanding the usage? Is this only the purview ofskate
? I saw this (charmbracelet/skate#31) and I thought that I could just usecharm kv
.Thanks for the cool tools!
The text was updated successfully, but these errors were encountered: