9ded10f68e
Napta uses Auth0 M2M, not a static token: exchange client_id/secret for a cached JWT, then list non-archived projects via JSON:API (include client name). Falls back to fixtures when NAPTA_CLIENT_ID/SECRET are unset. Member resolution still stubbed.
29 lines
966 B
YAML
29 lines
966 B
YAML
services:
|
|
web:
|
|
build: .
|
|
# No host port binding: Coolify's proxy routes the domain to this service
|
|
# over the internal network (see docker_compose_domains). Host bindings
|
|
# would collide with Coolify's own :80 / other apps on the host.
|
|
expose:
|
|
- "80"
|
|
depends_on:
|
|
- api
|
|
|
|
api:
|
|
build: ./backend
|
|
environment:
|
|
- PORT=8000
|
|
- DB_PATH=/app/data/app.db
|
|
# Set these as env vars on the Coolify app to switch from demo fixtures
|
|
# to live data. Empty Napta creds -> the backend serves fixtures.
|
|
- NAPTA_CLIENT_ID=${NAPTA_CLIENT_ID:-}
|
|
- NAPTA_CLIENT_SECRET=${NAPTA_CLIENT_SECRET:-}
|
|
- NAPTA_BASE_URL=${NAPTA_BASE_URL:-https://app.napta.io/api/v1}
|
|
- SLACK_BOT_TOKEN=${SLACK_BOT_TOKEN:-}
|
|
volumes:
|
|
- ./data:/app/data
|
|
# Internal only — the web (nginx) service reaches it at http://api:8000 on
|
|
# the compose network. Not published to the host.
|
|
expose:
|
|
- "8000"
|