iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website: force mime-types for some assets on deploy 

Should fix occassional issues with application/octet-stream mime type
assets breaking JS/CSS on site.
This commit is contained in:
Paul Hinze 2016-04-07 10:39:08 -05:00
parent b605c88c18
commit bcec4c4ffb
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/scripts/deploy.sh
View File

@ -61,6 +61,18 @@ if [ -z "$NO_UPLOAD" ]; then
--add-header="Cache-Control: max-age=31536000" \ --add-header="Cache-Control: max-age=31536000" \
--add-header="x-amz-meta-surrogate-key: site-$PROJECT" \ --add-header="x-amz-meta-surrogate-key: site-$PROJECT" \
sync "$DIR/build/" "s3://hc-sites/$PROJECT/latest/" sync "$DIR/build/" "s3://hc-sites/$PROJECT/latest/"
# The s3cmd guessed mime type for text files is often wrong. This is
# problematic for some assets, so force their mime types to be correct.
s3cmd \
--mime-type="application/javascript" \
modify "s3://hc-sites/$PROJECT/latest/**/*.js"
s3cmd \
--mime-type="text/css" \
modify "s3://hc-sites/$PROJECT/latest/**/*.css"
s3cmd \
--mime-type="image/svg+xml" \
modify "s3://hc-sites/$PROJECT/latest/**/*.svg"
fi fi
# Perform a soft-purge of the surrogate key. # Perform a soft-purge of the surrogate key.