In a standard CookieCutter application, building the frontend triggers frontend/build/build-pre.js, which creates version.ts, a required file (for environment.ts). This requires a package.json in the root level of the project and an initialized git repo. When we build the frontend container, we have neither.
The current approach hardcodes the git repo in the compose file and lets the user add a version tag in env, but it makes more sense to supply this information in the deployment module.
In a standard CookieCutter application, building the frontend triggers
frontend/build/build-pre.js, which createsversion.ts, a required file (forenvironment.ts). This requires apackage.jsonin the root level of the project and an initialized git repo. When we build the frontend container, we have neither.The current approach hardcodes the git repo in the compose file and lets the user add a version tag in env, but it makes more sense to supply this information in the deployment module.