fıdeliusDownload

Exporting a .env

Most tools don't need a .env: run them with accio my-app <command> and they get their keys without a file on disk. A .env is for tools that only read a file (like env_file in Docker Compose), apps started from a GUI, or pasting into a dashboard. A .env.example tells teammates and agents which keys a project needs, without any values.

Export a .env

  1. Select the project, then choose Secrets > Export .env…, or Control-click the project in the sidebar.
  2. Choose the folder. Fidelius remembers it for next time.
  3. Check the preview. It lists the key names that will be written and any that are left out.
  4. Click Export and confirm with Touch ID or your password.

The file holds the project's own keys only. Keys in shared aren't included, though they still reach commands run with accio. If a .env is already there, Replace moves the old one to the Trash first.

The .env holds your values in plain text, readable only by you. Delete it when you no longer need it.

Keys that are left out

Keep the .env out of git

Before you export, Fidelius checks whether git would commit the file.

Export a .env.example

Choose Secrets > Export .env.example…. It lists the key names with no values, so it doesn't ask for Touch ID. If one already exists, Fidelius asks before moving it to the Trash.

Copy as .env

Choose Secrets > Copy as .env to copy the project's keys as .env lines, for example to paste into a hosting dashboard. It asks for Touch ID, and the clipboard clears after 60 seconds.

From a terminal