Files
ma_proposal_bot/.env.example
T
uhlwoogiandClaude Opus 5.5 a51d5825ce Publish on host loopback for NPMplus with host networking
NPMplus runs with network_mode: host, so it cannot reach the container by
name on a shared Docker network. Publish the app on 127.0.0.1:4181 instead
and drop the NPM_NETWORK setting.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02 22:11:06 +00:00

21 lines
1.1 KiB
Bash

# Stack settings. In Portainer, enter these under the stack's "Environment variables".
# For the docker compose CLI, copy this file to .env next to compose.yaml. Never commit the completed file.
# Host port the app listens on, bound to loopback so only NPMplus (host networking) can reach it.
# Change PROPOSAL_BOT_PORT if 4181 is already taken on the host.
PROPOSAL_BOT_BIND=127.0.0.1
PROPOSAL_BOT_PORT=4181
# Absolute host folders. The data folder must be writable by UID 1000.
PROPOSAL_BOT_DATA_HOST_PATH=/opt/proposal-bot/data
PROPOSAL_BOT_PROJECT_IMAGES_HOST_PATH=/opt/proposal-bot/Project Images
# Microsoft Entra sign-in. The redirect URI must be the HTTPS address NPM serves and must match the app registration exactly.
# PROPOSAL_BOT_AUTH_REQUIRED=false turns sign-in off: anyone who can reach the site can read and edit every project.
PROPOSAL_BOT_AUTH_REQUIRED=true
MICROSOFT_TENANT_ID=
MICROSOFT_CLIENT_ID=
MICROSOFT_CLIENT_SECRET=
MICROSOFT_REDIRECT_URI=https://proposals.example.com/auth/microsoft/callback
PROPOSAL_BOT_ALLOWED_EMAILS=person.one@example.com,person.two@example.com