volumes.yml

# nocheck: backup-service-flag both volumes exist only because the image declares them as VOLUME; the settings file is rendered by this role on every deploy and the cache is derived, so a restore would return nothing the deploy does not rebuild
---
searxng_settings:
  type: config
  source: "{{ [ lookup('container', 'svc-ai-searxng', 'directories.config'), 'settings.yml' ] | path_join }}"
  mode: "0444"
  mounts:
    - service: searxng
      target: /etc/searxng/settings.yml
searxng_config:
  type: volume
  backup: false
  # nocheck: nfs-false-data-loss  Reason: holds the image's own /etc/searxng copy, which docker seeds per node on first start; the deployment's settings.yml is bind-mounted over it, so nothing a replica writes here has to reach another replica
  nfs: false
  mounts:
    - service: searxng
      target: /etc/searxng
searxng_cache:
  type: volume
  backup: false
  # nocheck: nfs-false-data-loss  Reason: derived search cache, rebuilt from the upstream engines on demand; shared over NFS every replica would write the same keys into one tree for no gain
  nfs: false
  mounts:
    - service: searxng
      target: /var/cache/searxng