kawa
582cc54189
Let deployments set a single App__Domain (e.g. sptb.example.com) instead of spelling out the full ClientConnect__RedirectUri. The SharePoint-connect callback is derived as <domain>/connect/callback; an explicit RedirectUri still wins for back-compat. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
33 lines
992 B
YAML
33 lines
992 B
YAML
services:
|
|
sptb-web:
|
|
build:
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
image: sptb-web:latest
|
|
container_name: sptb-web
|
|
ports:
|
|
- "8080:8080"
|
|
volumes:
|
|
- sptb-data:/data
|
|
environment:
|
|
- ASPNETCORE_ENVIRONMENT=Production
|
|
- DataFolder=/data
|
|
# Public domain the app is reached at (e.g. sptb.example.com). The SharePoint-connect
|
|
# redirect URI (<domain>/connect/callback) is derived from it. Set your OIDC values
|
|
# here too, or pass an env file.
|
|
- App__Domain=${App__Domain:-}
|
|
restart: unless-stopped
|
|
healthcheck:
|
|
# /account/login is anonymous and returns 200 (the app root now 302-redirects
|
|
# unauthenticated users, which would read as unhealthy). curl is installed in
|
|
# the image; -f fails on >=400.
|
|
test: ["CMD", "curl", "-fsS", "http://localhost:8080/account/login"]
|
|
interval: 30s
|
|
timeout: 10s
|
|
retries: 3
|
|
start_period: 30s
|
|
|
|
volumes:
|
|
sptb-data:
|
|
driver: local
|