awss3-deploy!Build Statustravis-imagetravis-url !npm versionnpm-imagenpm-url !Licenselicense-imagelicense-url
Deploy artefacts with aws-cli to S3
localdirectory to a
destdirectory of an S3 bucket. Sets a
cache-controlheader to a far-future expiry (one year) for everything except
index.html, which is set to
no-cache, no-store. Archives existing
destunder a datetime directory scheme. Intended to be used as a TravisCI deploy scripttravis-dpl.
# pip install awscli npm install --save awss3-deploy
BUCKET="mybucket" LOCAL_DIR="dist" UPLOAD_DIR="dev" ./node_modules/.bin/awss3-deploy
before_deploy: - export BUCKET=mybucket LOCAL_DIR=dist UPLOAD_DIR=dev deploy: provider: script script: awss3-deploy skip_cleanup: true
I think you might frequently ask questions like these
Why not Travis' default S3 deployment provider?
- It does not support per-object cache-control headers (yet; see: #170)
- We needed additional life-cycle/archival rules (alternatively, AWS Lambda could be used)