name: metapluginfullhash

# =============================================================================
# MetaPlugin · Full Hash — the `full-hash` enrichment plugin, as a standalone app.
#
# A MetaMesh enrichment plugin is a HEADLESS worker: it speaks the four-verb
# plugin HTTP contract (`/manifest`, `/health`, `/configure`, `/process`) and
# nothing else. There is no dashboard — the web UI on this tile is the plugin's
# own `/manifest`, which is how you confirm it is alive and what version it is.
#
# ⚠ NOTHING IN THE FAMILY CONSUMES IT BY URL YET — install it knowing that.
# MetaSort starts its own plugin containers from `plugins.yml` (`image:`) and
# has no URL slot. The feeder SDK has exactly three sidecar slots
# (`FILENAME_PARSER_URL`, `TMDB_PLUGIN_URL`, `OPENSUBTITLES_PLUGIN_URL`) and
# `full-hash` is not one of them. What this app gives you today is the plugin
# running and addressable at `http://metapluginfullhash-plugin:8080` for anything that
# speaks the four-verb plugin contract — your own caller, a probe, a future
# consumer. It is packaging ahead of the consumer, on purpose.
#
# ⚠ IT HOLDS NO CREDENTIALS. The caller POSTs `/configure` with its own key
# (TMDB token, OpenSubtitles account) before use. Two consumers sharing one
# instance are last-writer-wins on that config — same key, no problem; different
# keys, install a second copy.
#
# Everything is scoped under the `metapluginfullhash-*` prefix + the per-stack `metapluginfullhash`
# network + /DATA/AppData/metapluginfullhash/ data root, so it installs beside the other Meta* apps with zero
# collisions.
# =============================================================================

services:
  # ---------------------------------------------------------------------------
  # metapluginfullhash-plugin — the plugin. Listens on 8080; joined to `pcs` so any
  # consumer on the box can reach it by name. Default queue: background.
  # ---------------------------------------------------------------------------
  metapluginfullhash-plugin:
    image: ipcr-watch.nsl.sh/ipns/metadec.eth/metadec.eth/metamesh-plugin-fullhash:1.0.2
    cpu_shares: 30
    container_name: metapluginfullhash-plugin
    # 2 GB, swap disabled (memswap_limit == mem_limit) → OOM instead of
    # swap. Sized for whole-file hashing of large media over WebDAV; this
    # is the one plugin that genuinely needs it.
    mem_limit: 2g
    memswap_limit: 2g
    hostname: metapluginfullhash-plugin
    restart: unless-stopped
    user: "0:0"
    expose:
      - 8080
    environment:
      # Nothing to configure: this plugin takes its work from the /process
      # payload and writes back through the caller. No key, no WebDAV.
      TZ: "$TZ"
    volumes:
      # Plugin cache. Persisted so a recreate does not redo work that is
      # expensive to redo; safe to delete, it rebuilds.
      - ${DATA_ROOT:-/DATA}/AppData/metapluginfullhash/cache:/cache:rw
    networks:
      - pcs
networks:
  pcs:
    name: ${APP_NET:-pcs}
    external: true

x-casaos:
  architectures:
    - amd64
    - arm64
  author: Worph Team
  category: Developer
  developer: Aptero Team

  description:
    en_us: |
      **The `full-hash` enrichment plugin for MetaMesh, as its own app.**

      Hashes a whole file — high-performance parallel hashing with optimised I/O — and writes the SHA-256 CID that duplicate detection keys on.

      ⚠ **The expensive one.** It reads every byte of every file it is given,
      over WebDAV, on the background queue. The 2 GB limit and the 5-minute
      timeout are sized for large media files, not padding.

      **Headless.** It answers the plugin HTTP contract — `/manifest`, `/health`,
      `/configure`, `/process` — and has no dashboard; this tile opens its
      `/manifest`. Point a consumer at `http://metapluginfullhash-plugin:8080`.

      ⚠ **No MetaMesh app calls it by URL yet.** MetaSort starts its own plugin
      containers from `plugins.yml`, and the MetaFeeder SDK's sidecar slots cover
      only filename-parser, TMDB and OpenSubtitles — not `full-hash`. Installing this
      gives you the plugin running and addressable on the `pcs` network for
      anything that speaks the plugin contract; it does **not** add `full-hash` to
      MetaSort.
    fr_fr: |
      **Le plugin d'enrichissement `full-hash` de MetaMesh, en app autonome.**

      Hache un fichier entier — hachage parallèle haute performance — et écrit le CID SHA-256 sur lequel la détection de doublons s'appuie.

      **Sans interface.** Il répond au contrat HTTP des plugins — `/manifest`,
      `/health`, `/configure`, `/process` — et n'a pas de tableau de bord ; cette
      tuile ouvre son `/manifest`. Dirigez un consommateur vers
      `http://metapluginfullhash-plugin:8080`.

      **Ce n'est pas un plugin MetaSort** : MetaSort démarre ses propres
      conteneurs de plugins depuis `plugins.yml` et n'accepte pas d'URL.
  tagline:
    en_us: Whole-file SHA-256 hashing for MetaMesh (duplicate detection)
    fr_fr: Hachage SHA-256 de fichiers entiers pour MetaMesh (détection de doublons)

  title:
    en_us: MetaPlugin · Full Hash

  icon: https://gitea-watch.nsl.sh/metastar/MetaAppStore/raw/branch/main/Apps/MetaPluginFullHash/icon.png
  thumbnail: https://gitea-watch.nsl.sh/metastar/MetaAppStore/raw/branch/main/Apps/MetaPluginFullHash/thumbnail.png

  store_app_id: metapluginfullhash
  is_uncontrolled: false

  tips:
    before_install:
      en_us: |
        ⚠ **Read this first: nothing calls `full-hash` by URL yet.** MetaSort spawns
        its own plugin containers from `plugins.yml` (`image:`) and has no URL
        slot, and the MetaFeeder SDK's three sidecar slots are filename-parser,
        TMDB and OpenSubtitles only. Install this if you want `full-hash` running and
        addressable at `http://metapluginfullhash-plugin:8080` for your own caller — not
        expecting it to light up MetaSort or a MetaFeeder on its own.

        **No web UI:** a headless service. Its consumers reach it directly on the
        `pcs` network.

# Maison (Yundera dashboard) configuration. Read in preference to x-casaos.
# schema_version 2 is required for `folders`: an older Maison refuses the app
# outright rather than starting it without its directories.
x-compose-app:
  schema_version: 2
  # Created and chowned by Maison before any image is pulled, before any hook
  # runs and before the containers start — on the first boot and every one after.
  # Compose would otherwise create a missing bind source as a root-owned dir.
  folders:
    - path: /DATA/AppData/metapluginfullhash/cache
      user: $PUID
      group: $PGID