Reconstruct your workspace on another machine
Use casesA laptop, a desktop, a server — and sooner or later one of them is replaced. What you want back is not a backup of an app's database; it is your notes.
The situation
An operator works across a laptop, a desktop, and a server — and sooner or later one of them is replaced. Because the vaults are Git repositories, a new machine is rebuilt from them: establish the pod, make the intended Git-backed vaults reachable, sync them, and rebuild the local indexes. The mechanism repeats on each additional machine.
How you do it
Have the agent walk what the account can reach and sort it into two groups: the vaults you can push to, which come onto this machine, and the ones you can only read, which are recorded as subscriptions. Ask for that split back before it calls the job done.
Needs: Lyt initialized.
Using Lyt, set this replacement machine up from GitHub: walk the repositories this account can reach, bring the Lyt vaults I can push to onto this machine, and record the ones I can only read as subscriptions. Before you report done, tell me which vaults ended up in each of those two groups.
With --auto, each cluster gets its default outcome without prompting: vaults you can push to are adopted onto this machine, vaults you cannot are recorded as external. Drop --auto for a read-only walk that reports what it finds and changes nothing. Assumes Lyt is installed and initialized on this machine.
lyt discover --auto --jsonWhat changes
A replaced machine is a rebuild from Git, and the indexes are made again locally. Keeping several machines in step from then on — how to check freshness before syncing, and what to do when local state drifts — is covered in the multiple machines guide.