feat(envs): standardized env examples and add new redis connection ur…

…l env

.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=<https://your-production-domain.com,https://another-trusted-domain.com>
 
 # 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=<true or any non zero value>
+# ANIWATCH_API_VERCEL_DEPLOYMENT=<true or any non zero value>
+
+# env to use optional redis caching functionality
+ANIWATCH_API_REDIS_CONN_URL=<rediss://default:your-secure-password@your-redis-instance-name.provider.com:6379>