wehub-resource-sync
132 lines
4.8 KiB
Markdown
132 lines
4.8 KiB
Markdown
# Multiple Instances
|
|
|
|
Run multiple nanobot instances simultaneously with separate configs and runtime data. Use `--config` as the main entrypoint. Optionally pass `--workspace` during `onboard` when you want to initialize or update the saved workspace for a specific instance.
|
|
|
|
## Quick Start
|
|
|
|
If you want each instance to have its own dedicated workspace from the start, pass both `--config` and `--workspace` during onboarding.
|
|
|
|
**Initialize instances:**
|
|
|
|
```bash
|
|
# Create separate instance configs and workspaces
|
|
nanobot onboard --config ~/.nanobot-telegram/config.json --workspace ~/.nanobot-telegram/workspace
|
|
nanobot onboard --config ~/.nanobot-discord/config.json --workspace ~/.nanobot-discord/workspace
|
|
nanobot onboard --config ~/.nanobot-feishu/config.json --workspace ~/.nanobot-feishu/workspace
|
|
```
|
|
|
|
**Configure each instance:**
|
|
|
|
Edit `~/.nanobot-telegram/config.json`, `~/.nanobot-discord/config.json`, etc. with different channel settings. The workspace you passed during `onboard` is saved into each config as that instance's default workspace.
|
|
|
|
**Run instances:**
|
|
|
|
```bash
|
|
# Check one instance before starting it
|
|
nanobot status --config ~/.nanobot-telegram/config.json
|
|
|
|
# Instance A - Telegram bot
|
|
nanobot gateway --config ~/.nanobot-telegram/config.json
|
|
|
|
# Instance B - Discord bot
|
|
nanobot gateway --config ~/.nanobot-discord/config.json
|
|
|
|
# Instance C - Feishu bot with custom port
|
|
nanobot gateway --config ~/.nanobot-feishu/config.json --port 18792
|
|
```
|
|
|
|
## Path Resolution
|
|
|
|
When using `--config`, nanobot derives its runtime data directory from the config file location. The workspace still comes from `agents.defaults.workspace` unless you override it with `--workspace`.
|
|
|
|
To open a CLI session against one of these instances locally:
|
|
|
|
```bash
|
|
nanobot agent -c ~/.nanobot-telegram/config.json -m "Hello from Telegram instance"
|
|
nanobot agent -c ~/.nanobot-discord/config.json -m "Hello from Discord instance"
|
|
|
|
# Open the browser workbench for a specific instance
|
|
nanobot webui -c ~/.nanobot-telegram/config.json
|
|
|
|
# Optional one-off workspace override
|
|
nanobot agent -c ~/.nanobot-telegram/config.json -w /tmp/nanobot-telegram-test
|
|
```
|
|
|
|
> `nanobot agent` starts a local CLI agent using the selected workspace/config. It does not attach to or proxy through an already running `nanobot gateway` process.
|
|
|
|
| Component | Resolved From | Example |
|
|
|-----------|---------------|---------|
|
|
| **Config** | `--config` path | `~/.nanobot-A/config.json` |
|
|
| **Workspace** | `--workspace` or config | `~/.nanobot-A/workspace/` |
|
|
| **Cron Jobs** | workspace directory | `~/.nanobot-A/workspace/cron/` |
|
|
| **Media / runtime state** | config directory | `~/.nanobot-A/media/` |
|
|
|
|
## How It Works
|
|
|
|
- `--config` selects which config file to load
|
|
- By default, the workspace comes from `agents.defaults.workspace` in that config
|
|
- If you pass `--workspace`, it overrides the workspace from the config file
|
|
|
|
## Minimal Setup
|
|
|
|
1. Copy your base config into a new instance directory.
|
|
2. Set a different `agents.defaults.workspace` for that instance.
|
|
3. Start the instance with `--config`.
|
|
|
|
Example config fragment:
|
|
|
|
```json
|
|
{
|
|
"agents": {
|
|
"defaults": {
|
|
"workspace": "~/.nanobot-telegram/workspace"
|
|
}
|
|
},
|
|
"channels": {
|
|
"telegram": {
|
|
"enabled": true,
|
|
"token": "YOUR_TELEGRAM_BOT_TOKEN"
|
|
}
|
|
},
|
|
"gateway": {
|
|
"host": "127.0.0.1",
|
|
"port": 18790
|
|
}
|
|
}
|
|
```
|
|
|
|
The copied base config can keep using the same `modelPresets` and `agents.defaults.modelPreset`. If this instance needs a different model, add another preset and set `agents.defaults.modelPreset` to that preset name.
|
|
|
|
Start separate instances:
|
|
|
|
```bash
|
|
nanobot status --config ~/.nanobot-telegram/config.json
|
|
nanobot gateway --config ~/.nanobot-telegram/config.json
|
|
nanobot gateway --config ~/.nanobot-discord/config.json
|
|
```
|
|
|
|
Each gateway instance also exposes a lightweight HTTP health endpoint on `gateway.host:gateway.port`. By default, the gateway binds to `127.0.0.1`, so the endpoint stays local unless you explicitly set `gateway.host` to a public or LAN-facing address.
|
|
|
|
- `GET /health` returns `{"status":"ok"}`
|
|
- Other paths return `404`
|
|
|
|
Override workspace for one-off runs when needed:
|
|
|
|
```bash
|
|
nanobot gateway --config ~/.nanobot-telegram/config.json --workspace /tmp/nanobot-telegram-test
|
|
```
|
|
|
|
## Common Use Cases
|
|
|
|
- Run separate bots for Telegram, Discord, Feishu, and other platforms
|
|
- Keep testing and production instances isolated
|
|
- Use different models or providers for different teams
|
|
- Serve multiple tenants with separate configs and runtime data
|
|
|
|
## Notes
|
|
|
|
- Each instance must use a different port if they run at the same time
|
|
- Use a different workspace per instance if you want isolated memory, sessions, and skills
|
|
- `--workspace` overrides the workspace defined in the config file
|
|
- Cron jobs are stored in the active workspace; runtime media/state is derived from the config directory
|