Skip to content

Commit 136f5cc

Browse files
committed
update env description for telegram server guide
1 parent f3282bf commit 136f5cc

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

src/pages/guides/telegram-miniapp-server.mdx

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -140,15 +140,20 @@ npm install express jsonwebtoken @telegram-apps/init-data-node dotenv cors
140140
Create a `.env` file to store your sensitive data.
141141

142142
```env
143-
TELEGRAM_BOT_TOKEN=your_bot_token_here
144-
JWT_SECRET=your_secret_key
145143
NODE_ENV=development
146144
APP_URL="https://your-app-url.com"
145+
TELEGRAM_BOT_TOKEN=your_bot_token_here
146+
JWT_SECRET=your_secret_key
147147
JWT_KEY_ID=your_key_id
148148
```
149149

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

153158
---
154159

0 commit comments

Comments
 (0)