Onboarding a new teammate
They run one command, confirm a code in the browser once, and the repo plus its .env are both sitting in their working directory.
No more "can you send me the env file" in a DM.
CLI
envshare is a small command-line tool that clones the repo behind an environment and writes its .env for you, respecting the same password, 2FA, and access-key protection as the web app.
Authenticate once with a device code, the same flow GitHub's CLI uses. From there, every pull is a single command.
$ envshare login-> Confirm this code in your browser: QKR4-6BULOK Logged in.$ envshare clone acme/api-gatewayCloning git@github.com:acme/api-gateway.git...OK Wrote api-gateway/.env
Three moments where a terminal command beats opening the browser.
They run one command, confirm a code in the browser once, and the repo plus its .env are both sitting in their working directory.
No more "can you send me the env file" in a DM.
Already have the repo cloned? envshare pull refreshes .env from whatever the workspace currently holds, in place.
The .env in your editor matches what's actually deployed.
Update the value once in the workspace, then everyone re-runs envshare pull instead of passing the new key around by hand.
The exposure window is one pull, not one thread.
One package, no separate download. Run it with npx, or install it once if you'll use it daily.
npx @kpz231/envshare login
# or install once:
npm install -g @kpz231/envshare
envshare loginFive commands cover the whole workflow.
envshare loginStarts a device-code login and saves your CLI session locally.
envshare listLists every environment your account can access, by workspace.
envshare clone <name>Clones the linked repo and writes its .env, prompting for a password or 2FA code if the environment is protected.
envshare pullRe-downloads .env into the current directory, for repos already cloned.
envshare logoutRevokes the local session and forgets the saved token.
Create a workspace, upload your first .env file, and share it with your team in under two minutes.