Skip to content

Commit

Permalink
update env description for telegram server guide
Browse files Browse the repository at this point in the history
  • Loading branch information
shahbaz17 committed Nov 28, 2024
1 parent f3282bf commit 136f5cc
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions src/pages/guides/telegram-miniapp-server.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -140,15 +140,20 @@ npm install express jsonwebtoken @telegram-apps/init-data-node dotenv cors
Create a `.env` file to store your sensitive data.

```env
TELEGRAM_BOT_TOKEN=your_bot_token_here
JWT_SECRET=your_secret_key
NODE_ENV=development
APP_URL="https://your-app-url.com"
TELEGRAM_BOT_TOKEN=your_bot_token_here
JWT_SECRET=your_secret_key
JWT_KEY_ID=your_key_id
```

The `NODE_ENV` environment variable allows you to detect whether the app is running in development
or production mode.
- The `NODE_ENV` is the environment in which the app is running.
- The `APP_URL` is the URL of your deployed app.
- The `JWT_SECRET` is the private key used to sign the JWT.
- The `TELEGRAM_BOT_TOKEN` is the Telegram bot token.
- The `JWT_KEY_ID` is a unique identifier in for the key used to sign the JWT. This ID helps
Web3Auth locate the correct public key from your JWKS endpoint for token verification. It must
match the `kid` value in your JWKS configuration.

---

Expand Down

0 comments on commit 136f5cc

Please sign in to comment.