NUFI Docs

Developer setup

One landing page that maps each repo to its dev workflow.

Five repos in the NUFI org. Pick the one you need.

RepoPurposeDev guide
npuops-platformCompose stack — everything wired togetherLocal stack
nufi-chatStandalone chat deploymentnufi-chat
LibreChat (fork)Source of the chat imageLibreChat fork
nufichat-admin-panelAdmin panel SPAAdmin panel dev
nufi-consoleSelf-service developer consoleConsole dev

How they relate

       compose-stack glue                ─── npuops-platform (you usually run this)
            │
            ├──── pulls image ──── nufi-chat (also a standalone repo)
            │                          │
            │                          └── built from ──── LibreChat fork
            │
            ├──── pulls image ──── nufi-console
            └──── pulls image ──── nufichat-admin-panel (separate compose / proxy)

The general flow is:

  1. npuops-platform is the long-running stack you keep up (docker compose up -d) so every other repo has something to talk to (LiteLLM, Langfuse, MongoDB).
  2. You clone the specific repo you are working on as a sibling directory.
  3. You run that repo's dev server locally (with HMR) against the running platform stack.
  4. Once a change is ready, you tag the repo — CI builds a new image — and bump the tag in npuops-platform/docker-compose.yml.

The four sub-guides cover the dev-server command, the env vars, and the gotchas for each repo.

A note on Node vs Bun

  • LibreChat fork — Node 20.19+ / 22+ / 23+, npm.
  • Admin panel, nufi-console — Bun 1.3+.
  • nufi-docs (this site) — pnpm 10+.

All three coexist on the same machine; the package managers do not fight.

Local stack (npuops-platform)

Standing up the full compose stack as your dev backbone.

On this page

How they relateA note on Node vs Bun