Parse .env files, detect duplicate or invalid variables, and copy a deployment ENV report without raw values.
Input / Output
Input, output, and copy actions stay in this main surface. Examples and reference checks are separated below.
Local session
Input state is saved only in this browser so you can restore the last workspace without an account.
Open examples, checks, and related tools only after the primary input/output flow is done.
Validate deploy config
Validate YAML or Compose structure, inspect environment values, then format JSON config fragments before shipping.
Check indentation, YAML parse errors, and Compose service diagnostics.
Review duplicate, malformed, empty, or secret-like environment values.
Format JSON config fragments and inspect shape before copying.
Before copying
Common failure cases
Related tools
Guides
Open examples, checks, and related tools only after the primary input/output flow is done.
APP_ENV=production
API_URL=https://api.example.comexport FEATURE_FLAG=true
TIMEOUT_MS=5000SECRET_KEY="redacted value"ENV examples
Variables
3
Duplicates
0
Malformed lines
0
Secret-like keys
0
Review key names and value shape before copying config.
Line 1
APP_ENV
productionLine 2
API_URL
https://api.example.comLine 3
FEATURE_FLAG
trueENV deployment report
Copy a safe deployment handoff report with variable counts, warning notes, and checklist items without raw values.
Variables
3
Duplicates
0
Malformed lines
0
Secret-like keys
0
URL-like values
1
Empty values
0
Public-prefixed keys
0
Raw values included
No, raw values are excluded.
Deployment checklist
# ENV deployment report
- Checked at: Browser copy time
- Variables: 3
- Duplicates: 0
- Malformed lines: 0
- Secret-like keys: 0
- URL-like values: 1
- Empty values: 0
- Public-prefixed keys: 0
- Raw values included: No, raw values are excluded.
- Secret-like key names: Count only; names and values are excluded.
## Non-secret key list
APP_ENV, API_URL, FEATURE_FLAG
## Review notes
- No obvious ENV parsing warnings detected. Confirm required hosting variables before deployment.
## Deployment checklist
- Compare this key list with the hosting, CI, and server runtime variable list.
- Resolve duplicate keys before copying values because the final loader may keep only one assignment.
- Move production secrets into a secret manager or hosting variable store instead of sharing raw values.
- Confirm public-prefixed keys are safe for client-side exposure.
- After deployment, verify the public URL, DNS, and server response rather than trusting config parsing alone.Useful next steps
Copy-ready output
Parsed variables: 3
Parsed JSON:
{
"APP_ENV": "production",
"API_URL": "https://api.example.com",
"FEATURE_FLAG": "true"
}