cqrenet/matrix-docker-ansible-deploy
6
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-09-23 16:20:11 +00:00
Code Issues Wiki Activity

Reword the Molecule scenario comments

Browse Source 
They were hard-wrapped at 80 characters, broke mid-parenthesis, and spent lines
restating what the code below them does.

Rewrapped at natural boundaries instead, with the narration dropped and only the
reasons, gotchas and surprises kept. Section dividers stay - they delineate long
plays rather than narrate them.

Comments only; no scenario behaviour changes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT
This commit is contained in:
Slavi Pantaleev
2026-08-27 18:02:53 +03:00
co-authored by Claude Opus 5
parent e2d3be504e
commit c447e1528b
32 changed files with 458 additions and 641 deletions
Download Patch File Download Diff File Expand all files Collapse all files
roles/custom/matrix-bot-baibot/molecule/default/prepare.yml
+6 -9
View File
@@ -31,9 +31,8 @@
docker_daemon_options:
storage-driver: fuse-overlayfs
# The role's file tasks set owner/group by name, and Ansible resolves those
# through the passwd database - so they have to exist before it runs. In a
# real deployment `matrix-base` creates them.
# The role's file tasks set owner/group by name, which Ansible resolves through the
# passwd database, so they have to exist first. `matrix-base` creates them for real.
- name: Ensure the matrix group exists
ansible.builtin.group:
name: "{{ matrix_group_name }}"
@@ -70,13 +69,11 @@
- matrix_bot_baibot_molecule_network.rc != 0
- "'already exists' not in matrix_bot_baibot_molecule_network.stderr"
# baibot logs in and then syncs forever; with no homeserver answering it
# never gets past login and the unit crash-loops. The shared stub is enough
# - see molecule-shared/homeserver-stub.py for what it is not.
# baibot logs in and then syncs forever; with no homeserver answering it never gets past
# login. The shared stub is enough - see molecule-shared/homeserver-stub.py for what it is not.
#
# It is told to claim the bot's own MXID, because the bot resolves who it is
# from what the homeserver hands back at login, and everything it does
# afterwards (its profile, its own-message filtering) hangs off that.
# Told to claim the bot's own MXID, because the bot resolves who it is from what the
# homeserver hands back at login, and its profile and own-message filtering hang off that.
- name: Ensure the homeserver stub is running
ansible.builtin.include_tasks:
file: "{{ lookup('env', 'MOLECULE_PROJECT_DIRECTORY') }}/../../../molecule-shared/tasks/homeserver-stub.yml"