Remove EDGE_CACHE_TIME_SECONDS

- open question comment on why destructing is necessary
This commit is contained in:
2023-09-03 20:35:13 -05:00
parent 00acd8160a
commit d5e0b9b274
2 changed files with 2 additions and 3 deletions
-1
View File
@@ -18,7 +18,6 @@ export const serverSchema = z.object({
MAX_DISTANCE: z.coerce.number().positive(),
CENTER_LATITUDE: z.coerce.number().min(-90).max(90),
CENTER_LONGITUDE: z.coerce.number().min(-180).max(180),
EDGE_CACHE_TIME_SECONDS: z.coerce.number().int().nonnegative().default(60),
REDIS_URL: z.string().url(),
DISCORD_TOKEN: z.string(),
DISCORD_TARGET_USER_ID: z.string(),
+2 -2
View File
@@ -16,8 +16,7 @@ const _serverEnv = serverSchema.safeParse({
MAX_DISTANCE: process.env.MAX_DISTANCE,
CENTER_LATITUDE: process.env.CENTER_LATITUDE,
CENTER_LONGITUDE: process.env.CENTER_LONGITUDE,
EDGE_CACHE_TIME_SECONDS: process.env.EDGE_CACHE_TIME_SECONDS,
REDIS_URL: process.env.REDIS_URL,
REDIS_URL: process.env.REDIS_URL,
DISCORD_TOKEN: process.env.DISCORD_TOKEN,
DISCORD_TARGET_USER_ID: process.env.DISCORD_TARGET_USER_ID,
TIMEZONE: process.env.TIMEZONE
@@ -42,4 +41,5 @@ for (let key of Object.keys(_serverEnv.data)) {
}
}
// Why is destructing necessary here? Type
export const env = { ..._serverEnv.data };