PowerOn/service-teams-browser-bot
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update docs: multi-instance Gateway support

Browse source 
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
ValueOn AG 2026-02-13 23:00:54 +01:00
parent ab970292d9
commit a4062fc57c
1 changed files with 23 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
AZURE_SETUP.md
View file

@ -105,17 +105,36 @@ az containerapp registry set \
### 3.1 Environment Variable im Gateway ### 3.1 Environment Variable im Gateway
In `env_int.env` (oder Azure App Service Configuration): Der Bot Service ist **multi-instance-fähig**: Ein Bot kann mit allen Gateway-Instanzen (main, int, dev) arbeiten.
In **jeder** Gateway-Instanz die gleiche Bot URL konfigurieren:
**env_main.env:**
``` ```
TEAMSBOT_BROWSER_BOT_URL=https://teams-browser-bot.happysky-12345.westeurope.azurecontainerapps.io TEAMSBOT_BROWSER_BOT_URL=https://teams-browser-bot.<xyz>.azurecontainerapps.io
``` ```
**env_int.env:**
```
TEAMSBOT_BROWSER_BOT_URL=https://teams-browser-bot.<xyz>.azurecontainerapps.io
```
**env_dev.env:**
```
TEAMSBOT_BROWSER_BOT_URL=https://teams-browser-bot.<xyz>.azurecontainerapps.io
```
**Wie es funktioniert:**
1. Gateway sendet Join-Request an Bot mit `gatewayWsUrl` Parameter
2. `gatewayWsUrl` enthält die volle WebSocket-URL zurück zum aufrufenden Gateway
3. Bot verbindet sich zur richtigen Gateway-Instanz (main/int/dev)
### 3.2 Gateway neu deployen ### 3.2 Gateway neu deployen
```bash ```bash
# Push to int branch triggers deployment # Push to respective branch triggers deployment
git push origin int git push origin main # für main
git push origin int # für int
``` ```
--- ---