From 9d379ec4fe99782dc8e5340f2895cf11399bb1f9 Mon Sep 17 00:00:00 2001 From: Ritesh Ghosh Date: Sat, 7 Dec 2024 21:05:50 +0530 Subject: feat(envs): standardized env examples and add new redis connection url env --- .env.example | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/.env.example b/.env.example index c9e59b3..f1c627e 100644 --- a/.env.example +++ b/.env.example @@ -2,7 +2,7 @@ ANIWATCH_API_PORT=4000 # env to control allowed origins -ANIWATCH_API_CORS_ALLOWED_ORIGINS=https://your-production-domain.com,https://another-trusted-domain.com +ANIWATCH_API_CORS_ALLOWED_ORIGINS= # RATE LIMIT # duration to track requests (in milliseconds) for rate limiting. here, 30*60*1000 = 1800000 = 30 minutes @@ -12,12 +12,14 @@ ANIWATCH_API_MAX_REQS=70 # CAUTION: # For personal deployments, if you wanna have rate limitting -# in your application, then set this env to your deployed -# instance's hostname, otherwise don't set or have this env at all. -# If you set this env to an incorrect value, you may face other issues. - +# in your application, then set the env below to your deployed +# instance's hostname, otherwise don't set or have it at all. +# If you set the env below to an incorrect value, you may face other issues. # ANIWATCH_API_HOSTNAME="api-aniwatch.onrender.com" # NOTE: this env is "required" for vercel deployments -# ANIWATCH_VERCEL_DEPLOYMENT= +# ANIWATCH_API_VERCEL_DEPLOYMENT= + +# env to use optional redis caching functionality +ANIWATCH_API_REDIS_CONN_URL= -- cgit v1.2.3