ENV
Environment variables as a file.
Where it came from
ENV files come from the dotenv pattern, popularized by Heroku's twelve-factor app methodology around 2010: config belongs in the environment, not in code. A .env file is just a local dump of those variables.
Tools like Docker Compose and countless CLIs read .env on startup. It is the simplest possible secret-passing mechanism — and the easiest to leak if committed to git.
How it works
Each line is KEY=VALUE. Values may be quoted; # starts a comment. No sections, no nesting — it is a flat key→string map by design.
UWC parses .env into a JSON object (quotes stripped, comments dropped) and can serialize JSON back into a .env, all client-side. Nothing leaves the browser.
Convert ENV
Turn a .env into editable JSON and back — locally, so secrets never upload.