From 089654e092638182aa45b11c9b437c4257c2a28e Mon Sep 17 00:00:00 2001 From: Matchu Date: Wed, 7 Apr 2021 22:02:10 -0700 Subject: [PATCH] Use VERCEL_URL for waka loader if given Oh right, our preview deploy was loading the prod allWakaValues data! Now it uses the VERCEL_URL env variable to request from the current deployment instead. --- src/server/loaders.js | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/server/loaders.js b/src/server/loaders.js index 0f1b734..88a811f 100644 --- a/src/server/loaders.js +++ b/src/server/loaders.js @@ -608,10 +608,11 @@ const buildItemWakaValueLoader = () => // API would, and avoid putting pressure on our Google Sheets API quotas. // (Some kind of internal memcache or process-level cache would be a more // idiomatic solution in a monolith server environment!) - const url = - process.env.NODE_ENV === "production" - ? "https://impress-2020.openneo.net/api/allWakaValues" - : "http://localhost:3000/api/allWakaValues"; + const url = process.env.VERCEL_URL + ? `https://${process.env.VERCEL_URL}/api/allWakaValues` + : process.env.NODE_ENV === "production" + ? "https://impress-2020.openneo.net/api/allWakaValues" + : "http://localhost:3000/api/allWakaValues"; const res = await fetch(url); if (!res.ok) { throw new Error(