Files
computer-playbook/roles/web-app-mattermost/meta/services.yml

164 lines
5.7 KiB
YAML

---
sso:
bond: 1
enabled: "{{ 'web-app-keycloak' in group_names }}"
shared: "{{ 'web-app-keycloak' in group_names }}"
flavor: oidc
logout:
bond: 1
enabled: "{{ 'web-svc-logout' in group_names }}"
shared: "{{ 'web-svc-logout' in group_names }}"
# nocheck: dynamic-flag
ldap:
enabled: false # nocheck: dynamic-flag
dashboard:
bond: 1
enabled: "{{ 'web-app-dashboard' in group_names }}"
shared: "{{ 'web-app-dashboard' in group_names }}"
matomo:
bond: 1
enabled: "{{ 'web-app-matomo' in group_names }}"
shared: "{{ 'web-app-matomo' in group_names }}"
email:
bond: 1
enabled: "{{ MAIL_PROVIDER in group_names }}"
shared: "{{ MAIL_PROVIDER in group_names }}"
# nocheck: playwright-service-flag — DB engine, covered by role-local integration tests
postgres:
bond: 1
enabled: true # nocheck: dynamic-flag
shared: "{{ 'svc-db-postgres' in group_names }}"
# nocheck: playwright-service-flag: shared provider entity; the app itself is covered by this role's own Playwright spec
mattermost:
healthcheck:
test: ["CMD", "/mattermost/bin/mmctl", "--local", "system", "status"]
# nocheck: healthcheck-timing-override mmctl spawns a binary and talks to the local socket, so it does not belong on a 30s steady-state loop
interval: 1m
# nocheck: healthcheck-timing-override spawning that binary does not finish inside the 5s default
timeout: 10s
modes:
compose:
enabled: true
swarm:
enabled: true
bond: 1
enabled: true # nocheck: dynamic-flag
shared: true
user_access_token_enabled: "{{ 'web-app-nextcloud' in group_names }}"
image: mattermost/mattermost-team-edition
version: 12.0.1
min_storage: 659MB
backup:
no_stop_required: true
name: mattermost
cpus: "1.0"
mem_reservation: 512m
mem_limit: 1g
pids_limit: 512
ports:
local:
http: 8065
internal:
http: 8065
run_after:
- web-app-keycloak
- web-app-stalwart
- web-app-mailu
lifecycle: beta
# nocheck: dynamic-flag
# nocheck: playwright-service-flag — DB engine, covered by role-local integration tests
redis:
backup:
disabled: true
enabled: false # nocheck: dynamic-flag
shared: "{{ 'svc-db-redis' in group_names }}"
# nocheck: playwright-service-flag — object store, no Playwright surface
minio:
enabled: false # nocheck: dynamic-flag
shared: false # nocheck: dynamic-flag
seaweedfs:
bond: 1
enabled: "{{ 'web-app-seaweedfs' in group_names }}"
shared: "{{ 'web-app-seaweedfs' in group_names }}"
# nocheck: playwright-service-flag — css consumer, no Playwright surface (provider: web-svc-css)
css:
bond: 1
enabled: "{{ 'web-svc-css' in group_names }}"
shared: "{{ 'web-svc-css' in group_names }}"
# nocheck: dynamic-flag
# nocheck: playwright-service-flag — canonical:cdn alias of static-asset provider
javascript:
bond: 1
enabled: true # nocheck: dynamic-flag
shared: true
# nocheck: native-metrics — fragment ships prepared; operator flips `native_metrics.enabled` to opt in
prometheus:
bond: 1
enabled: "{{ 'web-app-prometheus' in group_names }}"
shared: "{{ 'web-app-prometheus' in group_names }}"
native_metrics:
enabled: false
port: 8067
communication:
channel: true
# nocheck: playwright-service-flag
# nocheck: variants-coverage — sso-variant-tor requires the onion on in every variant, so the false polarity has no variant left to live in
tor:
bond: 0.5
enabled: "{{ 'svc-net-tor' in group_names }}"
shared: true # nocheck: dynamic-flag
# nocheck: dynamic-flag
# nocheck: playwright-service-flag, dynamic-flag infrastructure backup consumer
container_backup: # nocheck: bond-baseline backup host joins outside the variant topology
bond: 1
enabled: "{{ 'svc-bkp-volume-2-local' in group_names }}"
shared: true
# nocheck: dynamic-flag - the gateway is a single shared instance, never deployed per consumer
litellm:
bond: 0.5
enabled: "{{ LITELLM_USABLE }}"
shared: true
# nocheck: playwright-service-flag internal adapter sidecar, covered by the role's MCP spec
# nocheck: dockerfile-custom the Dockerfile is owned by svc-ai-mcp-adapter and staged per instance, so every adapter-backed provider shares one audited build
# nocheck: dynamic-flag the sidecar tracks this role's own mcp flag, not another role's presence; a group_names expression would decide its exposure from an unrelated deployment
mattermostmcp:
enabled: "{{ lookup('config', 'web-app-mattermost', 'mcp.enabled') | bool }}"
shared: false
image: python
# nocheck: docker-version base of the self-built stdlib adapter, not the served application
version: "3.13.15-slim"
custom: true
name: mattermostmcp
cpus: "0.25"
mem_reservation: 16m
mem_limit: 24m
pids_limit: 64
healthcheck:
flavor: http_status
path: health
ports:
internal:
http: 8080
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
openwebui:
bond: 0.5
enabled: "{{ 'web-app-openwebui' in group_names }}"
shared: "{{ 'web-app-openwebui' in group_names }}"
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
hermes:
bond: 0.5
enabled: "{{ 'web-app-hermes' in group_names }}"
shared: "{{ 'web-app-hermes' in group_names }}"
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
openclaw:
bond: 0.5
enabled: "{{ 'web-app-openclaw' in group_names }}"
shared: "{{ 'web-app-openclaw' in group_names }}"
# nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate
# nocheck: dynamic-flag the entry refuses this client, so the link is off on every host and no group_names gate can decide it
flowise:
enabled: false
shared: false
mcp_consumer: false