ProjectBuild a Permission-Aware Knowledge Hub as an MCP Server: the explanation · Module 19: Containers and the local stack · part 21 of 22
Part 21 · Module 19: Containers and the local stack

Module 19: Containers and the local stack

23 min read·
About 40 minutes · Needs: Module 4 (the high-level architecture), Module 8 (the embedding model), Module 18 (X-Forwarded-For and trusted proxies) · Code: server/Dockerfile, server/Dockerfile.dockerignore, server/docker-entrypoint.sh, console/Dockerfile, console/nginx.conf.template, docker-compose.yml, .env.example, Makefile

Where this fits

WHERE THIS FITS Wayfinder this module AI CLIENTS the model writes the answer CONSOLE React, nginx WAYFINDER SERVER Starlette, mcp 2.3 RETRIEVAL permission filter before ranking INDEXING fastembed DATA Postgres 17 OPERATIONS evals, Docker, Cloud Run Claude Code HTTP + OAuth Cursor HTTP + OAuth Claude Desktop stdio bridge or connector MCP Inspector debugging, quick OAuth Web console React: search, audit, connect nginx one URL: /mcp, OAuth, /api MCP layer tools, resources Elicitation confirm create_issue OAuth 2.1 auth server, PKCE Tokens, sessions wf_pat_, cookie Console API /api REST Audit log every call, redacted stdio bridge wayfinder-stdio Guards proxy secret, limits Access rules groups per team Hybrid search pgvector + full text Fusion, boosts RRF, freshness, ADRs Knowledge decisions, owners Indexer loader, chunker bge-small-en fastembed, CPU PostgreSQL pgvector, full text Seed company Tidewater Freight Evaluation retrieval, 0 leaks Containers Docker Compose Deploy Cloud Run, Cloud SQL CI/CD GitHub Actions, WIF
The parts this module packs and starts (blue, the embedding model amber): the containers, nginx as the front door, Postgres with pgvector, the baked-in model and the baked-in seed company.

Every earlier module described code. This one packs that code into containers so one command starts the whole system on a laptop: the database with pgvector, the server with its embedding model and the fictional company baked in, and nginx serving the console and proxying everything else. The same two images are what the cloud deploy in Module 20 runs.

The rest of this project is yours to keep

This project is bought on its own, once, and stays readable afterwards, including the parts added to it later.

Or open everything with a plan