.env file. You can move it into Enkryptify with the CLI or from the dashboard.
Import with the CLI
This is the fastest path and the same workflow used for every other source.1
Install and sign in
Install the CLI and authenticate:
2
Import the file
From the directory that holds your With no argument
.env, run:ek import reads .env in the current directory. Pass a path to import a different file, for example ek import .env.production. It then lets you choose the target workspace, project and environment and uploads the secrets.3
Clean up
When the import succeeds the CLI offers to delete the source file. Accept it so no plaintext copy is left on disk.
Import from the dashboard
Good for a quick one-off file when you are not at a terminal.1
Open your project
In the dashboard, open the project that matches your app or service.
2
Open Add secrets
Click Add secrets then choose Import and .env file.
3
Select environments
Choose the environments that should receive these values. For a local
.env this is usually development.4
Review and save
Check the parsed keys, remove anything you do not want to manage in Enkryptify then save.
Run locally
After importing, link the project and run your app through the CLI:npm run dev with your normal start command.