Compare commits

..

2 commits

Author SHA1 Message Date
5c3d772010 Update submodules: fix embed-ui feature and deployment
Some checks failed
BotServer CI / build (push) Failing after 15s
- botui: Fixed rust-embed folder path for proper UI file embedding
- botserver: Removed Kubernetes deployment, added embed-ui documentation
- README: Updated with embed-ui feature explanation and deployment options
- Production deployments can now use single binary with embedded UI
2026-02-06 09:27:14 -03:00
164a0972a4 Update botserver submodule: Add embed-ui to default features
Production binaries should embed UI assets by default to avoid
requiring external ui/suite folder in deployment.

Note: botserver changes pushed to github, pragmatismo push pending
due to network issues.
2026-02-05 22:53:09 -03:00
3 changed files with 45 additions and 2 deletions

View file

@ -338,6 +338,49 @@ All infrastructure services (PostgreSQL, Vault, Redis, Qdrant, MinIO, etc.) are
**Do NOT install or reference global PostgreSQL, Redis, or other services.** When botserver starts, it automatically launches all required stack services. If you encounter service errors, check the individual service logs in `./botserver-stack/logs/[service]/` directories. **Do NOT install or reference global PostgreSQL, Redis, or other services.** When botserver starts, it automatically launches all required stack services. If you encounter service errors, check the individual service logs in `./botserver-stack/logs/[service]/` directories.
### UI File Deployment - Production Options
**Option 1: Embedded UI (Recommended for Production)**
The `embed-ui` feature compiles UI files directly into the botui binary, eliminating the need for separate file deployment:
```bash
# Build with embedded UI files
cargo build --release -p botui --features embed-ui
# The binary now contains all UI files - no additional deployment needed!
# The botui binary is self-contained and production-ready
```
**Benefits of embed-ui:**
- ✅ Single binary deployment (no separate UI files)
- ✅ Faster startup (no filesystem access)
- ✅ Smaller attack surface
- ✅ Simpler deployment process
**Option 2: Filesystem Deployment (Development Only)**
For development, UI files are served from the filesystem:
```bash
# UI files must exist at botui/ui/suite/
# This is automatically available in development builds
```
**Option 3: Manual File Deployment (Legacy)**
If you need to deploy UI files separately (not recommended):
```bash
# Deploy UI files to production location
./botserver/deploy/deploy-ui.sh /opt/gbo
# Verify deployment
ls -la /opt/gbo/bin/ui/suite/index.html
```
See `botserver/deploy/README.md` for deployment scripts.
### Start Both Servers (Automated) ### Start Both Servers (Automated)
```bash ```bash
# Use restart script (RECOMMENDED) # Use restart script (RECOMMENDED)

@ -1 +1 @@
Subproject commit 5cedd9c3792fc97c7a75fb63997db2838752ce61 Subproject commit e8a400d86dcb91267f6de519c661689fed7d5e14

2
botui

@ -1 +1 @@
Subproject commit cdf8bea155ed1acf375414612be65d04459b6a5d Subproject commit a1a30adb2c1bb7c0a6f821ea395e81a40982c222