luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Do not soft purge 

Soft purging is great, but we warm the cache immediately after deploy, and even then, if a user happens to be visiting the site in that few hundred milliseconds, they eat the time of a Fastly-S3 lookup, which is still 100x better than 99% of the websites out there.
This commit is contained in:
Seth Vargo 2017-02-27 14:36:08 -05:00 committed by GitHub
parent 10edf881fc
commit 73d307c361
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website/scripts/deploy.sh
View File

@ -89,7 +89,7 @@ if [ -z "$NO_UPLOAD" ]; then
modify "s3://hc-sites/$PROJECT/latest/" modify "s3://hc-sites/$PROJECT/latest/"
fi fi
# Perform a soft-purge of the surrogate key. # Perform a purge of the surrogate key.
if [ -z "$NO_PURGE" ]; then if [ -z "$NO_PURGE" ]; then
echo "Purging Fastly cache..." echo "Purging Fastly cache..."
curl \ curl \
@ -99,7 +99,6 @@ if [ -z "$NO_PURGE" ]; then
--request "POST" \ --request "POST" \
--header "Accept: application/json" \ --header "Accept: application/json" \
--header "Fastly-Key: $FASTLY_API_KEY" \ --header "Fastly-Key: $FASTLY_API_KEY" \
--header "Fastly-Soft-Purge: 1" \
"https://api.fastly.com/service/$FASTLY_SERVICE_ID/purge/site-$PROJECT" "https://api.fastly.com/service/$FASTLY_SERVICE_ID/purge/site-$PROJECT"
fi fi