sendnrw/glpi-neuroforge-mega
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
9a4370e4df124780a9181fbe7499729f2dcaaf1a
glpi-neuroforge-mega/deployments/README.md
T
groot 9a4370e4df
release-tag / release-image (push) Successful in 6m50s
Details
v1.6.0
2026-09-02 10:26:50 +02:00

908 B
Raw Blame History

Distributed Deployment Kits (v1.6.0)

This directory contains three independent deployment kits:

  • master/ - authoritative NeuroForge Master plus Agent, Knowledge, Control, optional SearXNG and optional Prometheus/Grafana.
  • cpu-subagent/ - CPU worker for vector.relink / graph convergence.
  • gpu-subagent/ - GPU worker plus local Ollama for model.chat and model.embed.

The generated NEUROFORGE_WORKER_TOKEN is identical in all three .env files. Replace the RFC 5737 example IP addresses (192.0.2.x) with real reachable addresses before starting.

Recommended order:

  1. GPU subagent: docker compose --profile monitoring up -d
  2. CPU subagent: docker compose --profile monitoring up -d
  3. Master: fill GLPI credentials, then docker compose --profile research --profile monitoring up -d

Only the Master holds authoritative NeuroForge state. Workers are disposable execution nodes.

Reference in New Issue View Git Blame Copy Permalink