Files
store-scraper-bot/.env.deploy.example
T
tiennm99 cad84e21a4 feat: accept KV_REST_API_* env vars as Upstash fallback
Vercel Marketplace Upstash integration injects KV_REST_API_URL and
KV_REST_API_TOKEN — different names from vanilla Upstash signup
(UPSTASH_REDIS_REST_URL / UPSTASH_REDIS_REST_TOKEN). Adapter and
migration script now accept either form, so the operator doesn't have
to duplicate values when sharing an Upstash DB provisioned via the
Vercel integration. UPSTASH_* takes precedence when both are set.
2026-05-09 20:17:06 +07:00

23 lines
936 B
Bash

# Operator-only file: holds the credentials the deploy + migrate scripts need.
# Copy to .env.deploy and fill in. NEVER commit .env.deploy.
# Telegram (must match values set as Vercel env vars)
TELEGRAM_BOT_TOKEN=
TELEGRAM_WEBHOOK_SECRET=
# Where Telegram should send webhook updates after Phase 6 cutover.
# Format: https://<your-vercel-url>/api/webhook
# Variable name kept as WORKER_URL for register-webhook.js compatibility.
WORKER_URL=https://store-scraper-bot.vercel.app/api/webhook
# Upstash Redis credentials — required by migrate-atlas-to-upstash.js.
# If the Vercel Marketplace Upstash integration is set up, the bot also
# accepts KV_REST_API_URL / KV_REST_API_TOKEN as fallbacks (see upstash.js).
UPSTASH_REDIS_REST_URL=
UPSTASH_REDIS_REST_TOKEN=
KEY_PREFIX=store-scraper-bot:
# Legacy Java-bot MongoDB Atlas — required for one-shot Phase 5 migration only.
# After successful cutover, remove this line.
MONGODB_URI=