GeneralBots/generalbots
1
0
Fork 0
Code Activity Actions 5

docs: standardize service names and ports to botserver:5858 and botui:5859

Browse source
This commit is contained in:
Rodrigo Rodriguez 2026-04-30 19:22:46 -03:00
parent 18ce9cb317
commit 675d88db2a
2 changed files with 17 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
AGENTS.md
View file

@ -5,11 +5,11 @@
- **❌ NEVER include sensitive data (IPs, tokens, passwords, keys) in AGENTS.md or any documentation** - **❌ NEVER include sensitive data (IPs, tokens, passwords, keys) in AGENTS.md or any documentation**
- **❌ NEVER use `scp`, direct SSH binary copy, or manual deployment to system container** - **❌ NEVER use `scp`, direct SSH binary copy, or manual deployment to system container**
- **✅ ALWAYS push to ALM → CI builds on alm-ci → CI deploys to system container automatically** - **✅ ALWAYS push to ALM → CI builds on alm-ci → CI deploys to system container automatically**
8080 is server 3000 is client ui 5858 is server 5859 is client ui
if you are in trouble with some tool, please go to the ofiical website to get proper install or instructions if you are in trouble with some tool, please go to the ofiical website to get proper install or instructions
To test web is http://localhost:3000 (botui!) To test web is http://localhost:5859 (botui!)
Use apenas a lingua culta ao falar . Use apenas a lingua culta ao falar .
test login here http://localhost:3000/suite/auth/login.html test login here http://localhost:5859/suite/auth/login.html
> **⚠️ CRITICAL SECURITY WARNING** > **⚠️ CRITICAL SECURITY WARNING**
I AM IN DEV ENV, but sometimes, pasting from PROD, do not treat my env as prod! Just fix, to me and push to CI. So I can test in PROD, for a while. I AM IN DEV ENV, but sometimes, pasting from PROD, do not treat my env as prod! Just fix, to me and push to CI. So I can test in PROD, for a while.
>Use Playwrigth MCP to start localhost:3000/<bot> now. >Use Playwrigth MCP to start localhost:3000/<bot> now.
@ -39,8 +39,8 @@ See botserver/src/drive/local_file_monitor.rs to see how bots are loaded from Mi
| Crate | Purpose | Port | Tech Stack | | Crate | Purpose | Port | Tech Stack |
|-------|---------|------|------------| |-------|---------|------|------------|
| **botserver** | Main API server, business logic | 8080 | Axum, Diesel, Rhai BASIC | | **botserver** | Main API server, business logic | 5858 | Axum, Diesel, Rhai BASIC |
| **botui** | Web UI server (dev) + proxy | 3000 | Axum, HTML/HTMX/CSS | | **botui** | Web UI server (dev) + proxy | 5859 | Axum, HTML/HTMX/CSS |
| **botapp** | Desktop app wrapper | - | Tauri 2 | | **botapp** | Desktop app wrapper | - | Tauri 2 |
| **botlib** | Shared library | - | Core types, errors | | **botlib** | Shared library | - | Core types, errors |
| **botbook** | Documentation | - | mdBook | | **botbook** | Documentation | - | mdBook |
@ -492,8 +492,8 @@ tail -f botserver.log botui.log
After reset completes, verify: After reset completes, verify:
- ✅ PostgreSQL running (port 5432) - ✅ PostgreSQL running (port 5432)
- ✅ Valkey cache running (port 6379) - ✅ Valkey cache running (port 6379)
- ✅ BotServer listening on port 8080 - ✅ BotServer listening on port 5858
- ✅ BotUI listening on port 3000 - ✅ BotUI listening on port 5859
- ✅ No errors in botserver.log - ✅ No errors in botserver.log
--- ---

20
INFRA.md
View file

@ -24,8 +24,8 @@ URL pattern: chat.{stage.}domain.com/botname for bot access.
### Critical Environment Details ### Critical Environment Details
- BotServer internal port varies by environment (check .env `PORT=`, typically 5858 on stage, 8080 on prod) - BotServer internal port varies by environment (check .env `PORT=`, typically 5858)
- BotUI must have `BOTSERVER_URL=http://localhost:{PORT}` matching botserver's PORT in its service Environment - BotUI must have `BOTSERVER_URL=http://localhost:5858` matching botserver's PORT in its service Environment
- Cache (Valkey) runs in the `cache` container — botserver reads host/port from Vault `secret/gbo/cache` - Cache (Valkey) runs in the `cache` container — botserver reads host/port from Vault `secret/gbo/cache`
- Vault `secret/gbo/cache` contains: host (cache container IP), port (6379), password - Vault `secret/gbo/cache` contains: host (cache container IP), port (6379), password
- NEVER put CACHE_URL/REDIS_URL in .env — all non-VAULT env vars are forbidden in production - NEVER put CACHE_URL/REDIS_URL in .env — all non-VAULT env vars are forbidden in production
@ -63,14 +63,14 @@ Externally, services are exposed via reverse proxy (Caddy). Internally, containe
| Service | External URL | Internal Address | | Service | External URL | Internal Address |
|---------|--------------|------------------| |---------|--------------|------------------|
| BotServer | `https://<system-domain>` | `http://<system-ip>:8080` | | BotServer | `https://<system-domain>` | `http://<system-ip>:5858` |
| BotUI | `https://<chat-domain>` | `http://<system-ip>:3000` | | BotUI | `https://<chat-domain>` | `http://<system-ip>:5859` |
| Zitadel | `https://<login-domain>` | `http://<directory-ip>:8080` | | Zitadel | `https://<login-domain>` | `http://<directory-ip>:8080` |
| Forgejo | `https://<alm-domain>` | `http://<alm-ip>:4747` | | Forgejo | `https://<alm-domain>` | `http://<alm-ip>:4747` |
| Webmail | `https://<webmail-domain>` | `http://<webmail-ip>:80` | | Webmail | `https://<webmail-domain>` | `http://<webmail-ip>:80` |
| Roundcube | `https://<roundcube-domain>` | `http://<webmail-ip>:80` | | Roundcube | `https://<roundcube-domain>` | `http://<webmail-ip>:80` |
**Note:** BotUI's `BOTSERVER_URL` must be `http://<system-ip>:8080` internally, NOT the external HTTPS URL. **Note:** BotUI's `BOTSERVER_URL` must be `http://<system-ip>:5858` internally, NOT the external HTTPS URL.
--- ---
@ -86,7 +86,7 @@ sudo incus list
# 2. Service health - all should show "active (running)" # 2. Service health - all should show "active (running)"
sudo incus exec system -- systemctl is-active botserver sudo incus exec system -- systemctl is-active botserver
sudo incus exec system -- systemctl is-active ui sudo incus exec system -- systemctl is-active botui
sudo incus exec directory -- systemctl is-active directory 2>/dev/null || echo "Directory check failed" sudo incus exec directory -- systemctl is-active directory 2>/dev/null || echo "Directory check failed"
sudo incus exec drive -- pgrep -f minio > /dev/null && echo "MinIO OK" || echo "MinIO DOWN" sudo incus exec drive -- pgrep -f minio > /dev/null && echo "MinIO OK" || echo "MinIO DOWN"
sudo incus exec tables -- pgrep -f postgres > /dev/null && echo "PostgreSQL OK" || echo "PostgreSQL DOWN" sudo incus exec tables -- pgrep -f postgres > /dev/null && echo "PostgreSQL OK" || echo "PostgreSQL DOWN"
@ -140,7 +140,7 @@ echo "Containers:"
sudo incus list -c n4,s | grep -E "(system|tables|vault|directory|drive|cache|llm|vector_db|alm-ci)" | awk '{print $1 ": " $3 " " $4}' sudo incus list -c n4,s | grep -E "(system|tables|vault|directory|drive|cache|llm|vector_db|alm-ci)" | awk '{print $1 ": " $3 " " $4}'
echo "" echo ""
echo "Services:" echo "Services:"
for svc in botserver ui; do for svc in botserver botui; do
sudo incus exec system -- systemctl is-active $svc 2>/dev/null && echo " $svc: ACTIVE" || echo " $svc: DOWN" sudo incus exec system -- systemctl is-active $svc 2>/dev/null && echo " $svc: ACTIVE" || echo " $svc: DOWN"
done done
echo "" echo ""
@ -311,14 +311,14 @@ sudo incus exec system -- ldd /opt/gbo/bin/botserver | grep "not found"
1. **If systemd failed:** 1. **If systemd failed:**
```bash ```bash
sudo incus exec system -- systemctl restart botserver sudo incus exec system -- systemctl restart botserver
sudo incus exec system -- systemctl restart ui sudo incus exec system -- systemctl restart botui
``` ```
2. **If GLIBC mismatch:** Binary compiled with wrong glibc. Must rebuild inside system container (Debian 12, glibc 2.36). 2. **If GLIBC mismatch:** Binary compiled with wrong glibc. Must rebuild inside system container (Debian 12, glibc 2.36).
3. **If port conflict:** 3. **If port conflict:**
```bash ```bash
sudo incus exec system -- lsof -i :8080 sudo incus exec system -- lsof -i :5858
sudo incus exec system -- killall botserver sudo incus exec system -- killall botserver
sudo incus exec system -- systemctl start botserver sudo incus exec system -- systemctl start botserver
``` ```
@ -678,7 +678,7 @@ sudo incus exec proxy -- systemctl restart proxy
**botserver won't start:** Run `sudo incus exec system -- ldd /opt/gbo/bin/botserver | grep "not found"` to check for missing libraries. Run `sudo incus exec system -- timeout 10 /opt/gbo/bin/botserver 2>&1` to see startup errors. Confirm `/opt/gbo/work/` exists and is accessible. **botserver won't start:** Run `sudo incus exec system -- ldd /opt/gbo/bin/botserver | grep "not found"` to check for missing libraries. Run `sudo incus exec system -- timeout 10 /opt/gbo/bin/botserver 2>&1` to see startup errors. Confirm `/opt/gbo/work/` exists and is accessible.
**botui can't reach botserver:** Check that the `ui.service` systemd file has `BOTSERVER_URL=http://localhost:5858` — not the external HTTPS URL. Fix with `sed -i 's|BOTSERVER_URL=.*|BOTSERVER_URL=http://localhost:5858|'` on the service file, then `systemctl daemon-reload` and `systemctl restart ui`. **botui can't reach botserver:** Check that the `botui.service` systemd file has `BOTSERVER_URL=http://localhost:5858` — not the external HTTPS URL. Fix with `sed -i 's|BOTSERVER_URL=.*|BOTSERVER_URL=http://localhost:5858|'` on the service file, then `systemctl daemon-reload` and `systemctl restart botui`.
**Suggestions not showing:** Confirm bot `.bas` files exist in MinIO Drive under `{bot}.gbai/{bot}.gbdialog/`. Check logs for compilation errors. Clear the AST cache in `/opt/gbo/work/` and restart botserver. **Suggestions not showing:** Confirm bot `.bas` files exist in MinIO Drive under `{bot}.gbai/{bot}.gbdialog/`. Check logs for compilation errors. Clear the AST cache in `/opt/gbo/work/` and restart botserver.