Build artifacts are pushed to mavfarm-embed S3 bucket with the convention:
s3://mavfarm-embed/<ENVIRONMENT>/embedded/<APP_VERSION>
Additionally artifacts are also pushed to the "latest" directory:
s3://mavfarm-embed/<ENVIRONMENT>/embedded/latest.
<APP_VERSION> is taken from "version" field in packages.json file.
Staging build and deployment is performed when you merge your changes to the stage branch.
Production build and deployment is performed when you merge your changes to the master branch.
We have CloudFront configured to serve static assets like .js scripts and images from S3 bucket. All requested objects are cached directly on CloudFront PoPs (Points of Presence). For /embedded/* request path assets are served from s3://mavfarm-embed/<ENVIRONMENT>/embedded/. For the rest of the files the default behaviour is to server objects from cdn.lost.show S3 bucket. It's not recommended to put different objects under the same file name (path) because it can be cached by our clients.
https://cdn.staging.lost.show/embedded/* => s3://mavfarm-embed/staging/embedded/
https://cdn.staging.lost.show/* => s3://cdn.lost.show/staging/
https://cdn.lost.show/embedded/* => s3://mavfarm-embed/production/embedded/
https://cdn.lost.show/* => s3://cdn.lost.show/production/