#35708 added 660+ lines of bash + PowerShell to wrap docker compose
and merge a new .env.default with the user's .env. Native Compose
already provides everything that script does:
- `${VAR:-default}` interpolation in compose.yaml gives per-key
defaults without a separate .env.default file.
- Auto-loaded .env in the project dir interpolates ${VAR:-default}
on the value side, so COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},
${DB_TYPE:-postgresql} expands correctly without a wrapper.
- `profiles:` on services already gates DB / vector-store selection.
- Maintaining two scripts (bash + PowerShell) duplicates env-file
parsing logic that compose owns natively, with subtle differences
(e.g. PowerShell's Get-Content uses system encoding, the bash
script's awk parser doesn't handle inline `# comment` after a
value).
Drop the wrappers and `.env.default`. Restore the README to the
two-step `cp .env.example .env && docker compose up -d` flow.
The .env.example placeholder cleanups landed in #35708 are kept.
Net: -712 lines, same UX modulo one extra `cp` step.
