Jrnl Architecture¶

Compose 🐳¶

flowchart LR
    none["dsk-jrnl declares no service"]

Swarm 🐝¶

flowchart LR
    none["dsk-jrnl declares no service"]

Volumes¶

flowchart LR
    none["dsk-jrnl declares no volume"]

Condition	Effect
swarm, `storage.backend: nfs`, no `nfs: false`, role not pinned	shared over NFS
any one of those missing	node-local

All four conditions must hold, so pinning a role takes every one of its volumes node-local. Only the role’s primary entry counts as pinned here: a placement on any other service pins that service alone and leaves the backing of every volume unchanged. The chain is drawn rather than its result, because that coupling is what makes a placement change move data without saying so.

Dependencies¶

flowchart LR
    subgraph deps [Dependencies]
        dep_dsk_base["dsk-base 💻"]
        dep_web_app_docs["web-app-docs 🐳🐝"]
    end
    subgraph role [dsk-jrnl 💻]
        svc_desktop_base["desktop-base"]
        svc_jrnl["jrnl"]
        svc_docs["docs"]
    end
    dep_dsk_base -- "1:1" --> svc_desktop_base
    dep_web_app_docs -. "0..1" .-> svc_docs

Symbol	Meaning
`1:1` solid	fixed relationship
`0..1` dashed	conditional, enabled only in matching deployments
`0..0` red	declared but turned off in this role
💻	deploys to the host
🐳	deploys under compose
🐝	deploys under swarm
❌	service explicitly turned off
⚙️	Ansible role dependency from `meta/main.yml`

Every dependency and dependent is listed; the graph is not truncated.