Export and restore

Open a context's settings and use Export .env. Download or copy a .env, or download a names-only .env.example. A .env holds readable values.

Open Backups in the account menu and use Back up. Pick one or more projects, and the contexts to include from each. Several projects download as one .zip.

• Encrypted: a .getmyenv-backup file per project. It holds ciphertext and encrypted keys. A backup opens with the Vault password or the recovery code in effect when it was made. A newer Vault password or recovery code does not open it. Backups made before recovery codes open with their Vault password only. After a vault reset, an older backup still opens with the Vault password or recovery code it was made with. Restoring it puts its values back, readable with your new key. It does not bring back the old vault.
• .env.example: variable names only. No values.

We don't keep the files. The Backups page lists each download, with the projects that were in it.

On Backups or Projects, use Restore with a .getmyenv-backup file. From a .zip, pick one file inside. It creates a new project with the same contexts. Existing projects are not changed. The browser opens the file and uploads names and ciphertext.

• npx getmyenv export -o .env: plaintext .env of one open context.
• npx getmyenv backup -o project.getmyenv-backup: encrypted backup of the open contexts.
• npx getmyenv restore project.getmyenv-backup: restore into this folder's project. Owner only. Values go into open contexts with the same slug. Values with the same name are replaced. Other variables stay. Read-only contexts and contexts the project doesn't have are skipped. Use --dry-run to preview.