Can Vue Storefront 2 projects share a version-controlled Docker Compose setup for multiple backend integrations?

Goal

Establish a single, version-controlled development environment that works across Magento, Shopify, and other backend integrations without requiring each developer to maintain custom Docker overrides or local .env files.

Constraints and uncertainty

The CLI-scaffolded docker-compose.yml only defines the frontend service and expects external API endpoints. The documentation recommends environment variables for backend configuration but does not provide a committed strategy for pinning backend versions, mock servers, or network topology. Community workarounds (docker-compose.override.yml, direnv, per-machine scripts) create drift and make onboarding inconsistent. The v1 integrated mock server was not carried forward, and there is no official GitHub Codespaces or Gitpod template to standardize cloud-based environments.

Questions

1. Which pattern allows the repository to define backend service definitions (including health checks and seeded data) while still letting developers swap between Magento, Shopify, and a local mock without editing tracked files?
2. How can the generated docker-compose.yml stay in sync with CLI updates so that dependency changes do not silently break the shared environment?
3. Does an official or community-maintained Gitpod/Codespaces configuration exist that reproduces the full stack, and if not, what minimal additions would make one reliable?