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

137 lines
4.6 KiB
YAML

---
# nocheck: seaweedfs-playwright — the bucket write happens in the admin Media view (upload.provider=s3, vars/main.yml), but this role blocks BOTH authenticated personas (PERSONA_ADMINISTRATOR_BLOCKED / PERSONA_BIBER_BLOCKED = true in templates/playwright.env.j2), so no Playwright session can reach that view; see TODO.md
asset:
bond: 1
enabled: "{{ 'web-svc-asset' in group_names }}"
shared: "{{ 'web-svc-asset' in group_names }}"
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 }}"
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 }}"
postgres:
bond: 1
enabled: true # nocheck: dynamic-flag
shared: "{{ 'svc-db-postgres' in group_names }}"
# nocheck: playwright-service-flag self-provider
listmonk:
enabled: true
shared: true
bond: 1
modes:
compose:
enabled: true
swarm:
enabled: true
# nocheck: single-replica
replicas: 1
cpus: 1.0
mem_reservation: 256m
mem_limit: 1g
pids_limit: 1024
min_storage: 215MB
image: listmonk/listmonk
version: "v6.2.0"
backup:
no_stop_required: true
name: listmonk
ports:
internal:
http: 9000
local:
http: 8019
healthcheck:
flavor: wget
path: health
public_api_activated: false
run_after:
- web-app-matomo
- web-app-keycloak
- web-app-stalwart
- web-app-mailu
lifecycle: beta
# nocheck: playwright-service-flag — object store, no Playwright surface
minio:
enabled: false # nocheck: dynamic-flag
shared: false # nocheck: dynamic-flag
public: true
# nocheck: playwright-service-flag — object store, no Playwright surface
seaweedfs:
bond: 1
enabled: "{{ 'web-app-seaweedfs' in group_names }}"
shared: "{{ 'web-app-seaweedfs' in group_names }}"
public: true
css:
bond: 1
enabled: "{{ 'web-svc-css' in group_names }}"
shared: "{{ 'web-svc-css' in group_names }}"
# nocheck: dynamic-flag
hcaptcha:
enabled: "{{ HCAPTCHA_ENABLED | bool }}"
prometheus:
bond: 1
enabled: "{{ 'web-app-prometheus' in group_names }}"
shared: "{{ 'web-app-prometheus' in group_names }}"
# nocheck: playwright-service-flag internal adapter sidecar, covered by the role's MCP guest 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
listmonkmcp:
enabled: "{{ lookup('config', 'web-app-listmonk', '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: listmonkmcp
cpus: "0.25"
mem_reservation: 16m
mem_limit: 24m
pids_limit: 64
ports:
internal:
http: 8080
# 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: 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