Files
remote-mcp-manager/.env.example
Dasemu ccb7fcd842 feat: enforce per-container memory/CPU limits
CONTAINER_MEMORY_MB and CONTAINER_CPUS (defaults 512/1) are now applied
to every installed MCP container's HostConfig instead of leaving them
unbounded.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-08 03:12:44 +02:00

31 lines
1.2 KiB
Plaintext

# Port the manager's own HTTP server listens on (the operator's own nginx proxies to this)
PORT=3000
# Path to the Docker/Podman-API-compatible socket.
# Production (Docker): /var/run/docker.sock
# Local dev (rootless Podman): /run/user/<uid>/podman/podman.sock
DOCKER_SOCKET_PATH=/var/run/docker.sock
# Name of the shared container network joining the manager and every installed MCP container
MCP_NETWORK_NAME=mcp-net
# Where the manager stores its SQLite DB, cloned repos and build logs
DATA_DIR=./data
# Public base URL used to build the authenticated MCP links shown in the UI, e.g. https://mcp.example.com
PUBLIC_BASE_URL=http://localhost:3000
# Password for the single admin/operator account that can use the panel
ADMIN_PASSWORD=change-me
# Random secret used to sign the admin session cookie
SESSION_SECRET=change-me-too
# Random string (min 32 chars) used to derive the AES-256-GCM key that encrypts
# installation env vars and bearer tokens at rest
MASTER_KEY=change-me-to-a-random-string-of-at-least-32-characters
# Resource caps applied to every installed MCP container (same limit for all, no per-installation override in V1)
CONTAINER_MEMORY_MB=512
CONTAINER_CPUS=1