The deployment scripts need to run docker-prep.sh before building Docker images
to package the @bytelyst/* dependencies as tarballs. This step was missing
after reverting the base image approach.
Generated with [Devin](https://cli.devin.ai/docs)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Reverting deployment script changes that were part of the base image approach.
The base image strategy is too complex for the current pnpm workspace structure.
Reverting to the proven docker-prep.sh tarball approach.
Generated with [Devin](https://cli.devin.ai/docs)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Update deployment scripts to pull shared base images instead of running
docker-prep.sh to pack @bytelyst/* tarballs.
Changes:
- Remove docker-prep.sh execution
- Add base image pull step (backend and web)
- Use local cache if pull fails
Benefits:
- Faster deployment (no tarball packing)
- Simpler deployment process
- Consistent package versions via base images
Generated with [Devin](https://cli.devin.ai/docs)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
The deployment scripts were missing the docker-prep.sh step which is required
to pack @bytelyst/* packages into .docker-deps directory and modify package.json
files to use local tarballs. Without this, Docker build fails trying to install
packages from npm registry instead of local tarballs.
Generated with [Devin](https://cli.devin.ai/docs)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
