SILVER/NODEDC_TASKMANAGER
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix: connect tasker backend to ai workspace network

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-06-09 15:48:11 +03:00
parent fcd014e26d
commit 8b1e356494
5 changed files with 36 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs_prod/NODEDC_TASKER_DEPLOY_MODEL.md
+13
View File
@@ -32,6 +32,19 @@ Backend integration:
- `PLANE_NODEDC_WORKSPACE_POLICY_URL`
- `PLANE_NODEDC_ACCESS_CHECK_URL`
- `PLANE_NODEDC_ACCESS_TOKEN`
- `NODEDC_ENGINE_DOCKER_NETWORK`
- `PLANE_NODEDC_AI_WORKSPACE_ASSISTANT_URL`
- `PLANE_NODEDC_AI_WORKSPACE_ASSISTANT_TOKEN`
AI Workspace Console uses the shared Platform `ai-workspace-assistant` service. Tasker does not connect to AI Workspace Hub directly. The Tasker backend containers must be attached to the same Docker network as Platform/Engine through `NODEDC_ENGINE_DOCKER_NETWORK`; on NAS this is currently `nodedc-demo_default`, while local development uses `nodedc-platform_default`.
Use the internal service URL on that shared network:
```env
PLANE_NODEDC_AI_WORKSPACE_ASSISTANT_URL=http://ai-workspace-assistant:18082
```
The Assistant generates Codex worker installers with the public Hub endpoint `wss://ai-hub.nodedc.ru/api/ai-workspace/hub`. Do not point Tasker directly at the Hub and do not expose Assistant as a public Nginx/DSM route.
Production secrets remain in NAS env files or a secret store. They must not be committed.