· 7 min · Eanvi
Sync secrets with the Eanvi CLI
Login, init, pull, push, sync, and diff — the daily loop for keeping local env files honest against encrypted remote state.
A checkout, not a vault on disk
The CLI treats your local env file as a working copy. eanvi login authenticates the machine. eanvi init writes .eanvi/config.json with the project, environment, and file path. From there, pull and push are the two verbs that matter.
eanvi pull downloads decrypted secrets and writes the target file. eanvi push uploads local changes and refuses to clobber remote versions unless you pass --force. eanvi diff shows added, modified, and removed keys before you commit to a write.
CI without a human
In pipelines, authenticate with an API key instead of an interactive login. Pull into the job’s filesystem, run the build, and let the runner discard the workspace. Reveals and pulls still land in the audit log, so a leaked key in CI is a traceable event rather than a mystery.
eanvi doctor checks installation, auth, config, and API connectivity when something feels off. Use it before you rewrite the config by hand.