Import & export .env

Setting variables one at a time is fine for a few, but when you are moving a project you want to bring a whole .env at once. Helicarrier supports bulk import and export on a service’s Variables tab.

Import a .env

Paste or upload a .env file and Helicarrier bulk-adds the variables. The parser is forgiving — it handles:

• KEY=value lines
• Quoted values
• # comments and blank lines
• export prefixes
• CRLF line endings

Double-quoted values are unescaped the standard .env way (\n becomes a newline, \" becomes ", and so on). So a JSON or PEM secret stored the escaped way — KEY="{\"type\":...\\n...}" — imports back as clean, parseable content rather than arriving with its escapes intact.

Import skips and reports anything it should not overwrite: managed database credentials, reference-set keys, and invalid names. You will see a summary of what was set and what was skipped.

Export

Export mirrors import. Copy all or Download .env produces KEY=value lines, escaping values symmetrically so a secret round-trips byte-for-byte — export a value and re-import it and you get exactly the same thing back. Export is a confirmed, audit-logged reveal (see Environment variables).

Precedence still applies

Imported variables are the service’s own variables, so they sit above environment groups but below references in the precedence order. Importing does not touch attached groups or references.

Next

• Review the full variable model in Environment variables.
• Share common values via Environment groups.