P2P Key Sync
Project keys are shared with your workspace peers automatically. When you create or edit a key, the change is encrypted and synced directly between devices using localWiki’s peer-to-peer sync layer. There is no central server holding your secrets.
How Sync Works
- You edit a key on your machine.
- localWiki encrypts the change with your workspace encryption key.
- The encrypted delta is broadcast to connected peers.
- Each peer decrypts and applies the change locally.
Peers that are offline receive the update the next time they connect. Sync is eventually consistent — every team member will converge to the same state.
Only workspace members with access to the project key store receive updates.
Conflict Resolution
When two teammates edit the same key at the same time, localWiki detects the divergence and marks the key with a conflict badge in the UI.
Resolving Conflicts
Open the project keys panel and look for keys with the red “conflict” indicator. Click Resolve to open the conflict resolution dialog. You have three options:
- Keep local — use the value from your device.
- Use remote — accept the value from the other device.
- Use new value — enter a completely new value to replace both.
The conflict dialog shows the remote update timestamp so you can make an informed decision.
Conflicts block injection via lol run. The CLI will report “unresolved conflict” errors until you resolve them in the desktop app. Run lol doctor to check for conflicts before deploying.
Stale Key Warnings
Keys that have not been updated in more than 7 days are flagged as stale in the key list. This is a visual reminder to review and rotate credentials regularly.