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.
This commit is contained in:
parent
a32bc34171
commit
089654e092
1 changed files with 5 additions and 4 deletions
|
@ -608,8 +608,9 @@ const buildItemWakaValueLoader = () =>
|
||||||
// API would, and avoid putting pressure on our Google Sheets API quotas.
|
// 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
|
// (Some kind of internal memcache or process-level cache would be a more
|
||||||
// idiomatic solution in a monolith server environment!)
|
// idiomatic solution in a monolith server environment!)
|
||||||
const url =
|
const url = process.env.VERCEL_URL
|
||||||
process.env.NODE_ENV === "production"
|
? `https://${process.env.VERCEL_URL}/api/allWakaValues`
|
||||||
|
: process.env.NODE_ENV === "production"
|
||||||
? "https://impress-2020.openneo.net/api/allWakaValues"
|
? "https://impress-2020.openneo.net/api/allWakaValues"
|
||||||
: "http://localhost:3000/api/allWakaValues";
|
: "http://localhost:3000/api/allWakaValues";
|
||||||
const res = await fetch(url);
|
const res = await fetch(url);
|
||||||
|
|
Loading…
Reference in a new issue