Vercel Env Checker

Docker Compose env interpolation

Check Compose variables before a missing env name breaks a run.

Paste a Compose snippet and a list of .env names. This local checker reports referenced names, defaults, required markers, env_file boundaries, and secret-like variable names without storing values.

Compose inputs

Names only
Do not paste API keys, tokens, passwords, database URLs, or real environment variable values. The report prints names only.

Interpolation result

fail

1 referenced env name need a local source or a default.

Referenced names3
Missing names1
Defaults1
Required1

Names found

DATABASE_URLLOG_LEVELNEXT_PUBLIC_SITE_URL
fail

Missing interpolation names

DATABASE_URL need a matching local source or default.

warn

Boundary to review

env_file loads container runtime values; it does not automatically satisfy Compose interpolation.

warn

Boundary to review

Secret-like names were detected. Check presence only and avoid copying real values into tools.

Safe report

Docker Compose env interpolation check
Status: fail
Summary: 1 referenced env name need a local source or a default.

Referenced names (3): DATABASE_URL, LOG_LEVEL, NEXT_PUBLIC_SITE_URL
Names present in pasted .env list (2): LOG_LEVEL, NEXT_PUBLIC_SITE_URL
Missing names: DATABASE_URL
Defaulted names: LOG_LEVEL
Required names: DATABASE_URL
Secret-like names: DATABASE_URL

Warnings:
- env_file loads container runtime values; it does not automatically satisfy Compose interpolation.
- Secret-like names were detected. Check presence only and avoid copying real values into tools.

Checklist:
- Confirm Docker Compose interpolation reads from the shell environment or the project .env file.
- Keep env_file entries for container runtime values, not Compose interpolation assumptions.
- Use ${VAR:?message} for required settings that should fail fast.
- Do not print secret values while debugging; log only whether a name is present.