groot
e0bf42bf32
mega-ci / static-release-gates (push) Failing after 11s
release-tag / release-image (push) Successful in 6m46s
mega-ci / go-quality (services/control) (push) Successful in 10m7s
mega-ci / go-quality (platform/neuroforge) (push) Successful in 10m20s
mega-ci / go-quality (services/agent) (push) Successful in 11m1s
mega-ci / go-quality (services/knowledge) (push) Successful in 11m13s
mega-ci / docker-build (push) Has been skipped
883 B
883 B
Distributed Deployment — v1.6.2
The distributed deployment is part of the canonical release, not a separate code fork.
deployments/master: authoritative NeuroForge Master, GLPI Agent, Knowledge, Control, optional Research, Prometheus and Grafana.deployments/cpu-subagent: remote CPU execution node for graph/relink work.deployments/gpu-subagent: remote GPU execution node plus Ollama for chat/embedding work.
All three roles ship with complete .env templates containing CHANGE_ME_... placeholders. The same real NEUROFORGE_WORKER_TOKEN must be configured on Master and both worker roles.
Recommended startup order: GPU subagent, CPU subagent, then Master. Keep the NeuroForge data volume authoritative on the Master only.
The v1.6.1 recovery/OOM fixes are included unchanged in v1.6.2. Do not delete the existing neuroforge-data volume when upgrading.