test/compose.yaml

# Local testing environment: two Prosody servers plus riddim.

#

#   docker compose up --build prosody remotemuc riddim

#   docker compose run --build --rm tester       # sends -ping to the bot, expects a reply

#   docker compose run --build --rm muc-tester   # same, via the MUC on remotemuc

#

# "prosody" is the bot's own server; "remotemuc" is a federated server whose

# MUC service (muc.remotemuc) the bot also joins. Killing and recreating

# remotemuc simulates a silent MUC disconnect (see `just muc-test`).

#

# The verse build context should point at a local checkout of the Verse

# repository (its upstream hosting is currently offline); override with

# e.g. VERSE_REPO=../../verse if yours lives elsewhere.

services:

  prosody:

    build: ./prosody

    environment:

      PROSODY_HOST: prosody

      PROSODY_USERS: "riddim:riddimpass tester:testerpass"

  remotemuc:

    build: ./prosody

    environment:

      PROSODY_HOST: remotemuc

    volumes:

      - ./prosody/remotemuc.cfg.lua:/etc/prosody/prosody.cfg.lua:ro

    networks:

      default:

        aliases:

          - muc.remotemuc

  riddim:

    build:

      context: ..

      additional_contexts:

        verse: ${VERSE_REPO:-../../verse}

    volumes:

      - ./config.lua:/etc/riddim/config.lua:ro

    depends_on:

      - prosody

      - remotemuc

    restart: on-failure

  tester:

    build:

      context: ..

      additional_contexts:

        verse: ${VERSE_REPO:-../../verse}

    entrypoint: ["/usr/bin/lua5.4", "/test/tester.lua"]

    working_dir: /opt/riddim

    volumes:

      - ./tester.lua:/test/tester.lua:ro

    depends_on:

      - riddim

    profiles: ["test"]

  muc-tester:

    build:

      context: ..

      additional_contexts:

        verse: ${VERSE_REPO:-../../verse}

    entrypoint: ["/usr/bin/lua5.4", "/test/muc_tester.lua"]

    working_dir: /opt/riddim

    volumes:

      - ./muc_tester.lua:/test/muc_tester.lua:ro

    depends_on:

      - riddim

    profiles: ["test"]