One dotvault pull, the same .env everywhere: laptop, CI, cloud dev environments
This is part 2 of the series "dotvault, Start to Finish: One Command from Your Laptop to CI, Your Team, and Your AI Agents." dotvault will be released free of charge when this series ends. A .env rarely lives in one place. The same variables are needed in CI, on the server that runs the app, and in cloud development environments such as GitHub Codespaces, Codex cloud in ChatGPT and Claude Code on…
Once you have installed the dotvault CLI globally using npm i -g @earthlink/dotvault, the next step is to log in using dotvault login. You will be prompted to enter your email address and password, which is not echoed back to you. After successful login, dotvault whoami command displays your email, token expiry and organization details.
The token remains valid for 3600 seconds, after which it expires. A refresh token is also saved, allowing you to automatically log in without manually entering your credentials every hour. Dotvault whoami also reveals your personal email and the organization you belong to. This process of logging in once per place forms the foundation for the subsequent steps, ensuring consistent access to the same .env values across different environments like laptops, CI servers, cloud development environments, and AI agents.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
