Files
conjurer/README.md
Michal Tuszowski ef6eb84921 Preserve backup_old_docker bot variant at root (for comparison)
Snapshot of the dockerisation-era bot code laid out at the repository
root so it can be diffed directly against the working-copy baseline
(restructure/working-copy-root) to see how the variant differed:

- thin_client.py asyncio entrypoint (vs working_copy bot.py)
- constants.py env-var/credential refactor, communication auth, etc.
- extra gpt_interface/ service, sync.py, watch_script_params.py
- conanjurer_* modules absent in this variant

Docker infrastructure (docker/, docker-compose.yml, .dockerignore)
intentionally omitted - this branch is for code comparison only and is
not intended to be merged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-28 22:55:53 +02:00

908 B

conjurer

Discord.py bot for fun, sex and BDSM

Docker quick start

Docker definitions live at the repository root and let you run the Discord bot (thin_client.py), the musician file service, and the librarian search worker as separate containers.

  1. Prepare configuration
    • Edit the environment files under docker/env/*.env and replace the placeholders (replace-me, shared-secret, etc.) with your real tokens. Keep CONJURER_API_KEY identical across all services.
  2. Create host directories listed in docker-compose.yml (for example docker/volumes/bot/config, docker/volumes/musician/data, …) and populate them with the required JSON settings or media assets.
  3. Launch the stack
    docker compose up --build
    

Logs for each container are mounted under docker/volumes/* so you can diff the runtime JSON and log files in git if needed.