How walshdsouza/shadow-sync works
Env-Sync is a CLI for creating or joining rooms and synchronizing each teammate’s local .env file. The main workflow is: save room credentials, derive a shared key locally, watch local edits, encrypt and send updates through a WebSocket relay, then decrypt and apply remote state with timestamp and empty-overwrite protections. The relay forwards encrypted messages between room members. The README describes the zero-trust and conflict-resolution capabilities; the graph also includes the direct start workflow. Relationships are limited to the shown source and documented architecture.
Main entry points: sync.js Sync Coordinator · cli.js CLI Commands · server.js WebSocket Relay · watcher.js File Watcher
Components 12
Room Setup
- CLI Commands
src/cli.js - Room Config
src/config.js - Key Derivation
src/crypto.js
Sync Client
- Sync Coordinator
src/sync.js - File Watcher
src/watcher.js - WebSocket Client
src/NetworkManager.js - Payload Crypto
src/crypto.js
Local State
- State Manager
src/StateManager.js - Local .env
Room Relay
- WebSocket Relay
server/server.js
Other components
- Developer
- Room Peers
Connections 13
- Developer → CLI Commands: runs commands
README.md - CLI Commands → Room Config: saves or loads
src/cli.js - CLI Commands → Key Derivation: derives key
src/cli.js - CLI Commands → Sync Coordinator: starts sync
src/cli.js - Sync Coordinator → State Manager: reads and evaluates
src/sync.js - State Manager → Local .env: reads and writes
src/StateManager.js - Sync Coordinator → File Watcher: starts watching
src/sync.js - File Watcher → Sync Coordinator: reports edits
src/sync.js - Sync Coordinator → Payload Crypto: encrypts and decrypts
src/sync.js - Sync Coordinator → WebSocket Client: sends and receives
src/sync.js - WebSocket Client → WebSocket Relay: connects to relay
README.md - WebSocket Relay → Room Peers: forwards room messages
server/server.js - Room Peers → WebSocket Relay: sends room messages
server/server.js