SkepticalWaves

Taking a look at the existing command, something like this ``` matrix_synapse_rust_synapse_auto_compress_state_command: >- {{ matrix_host_command_docker }} run --rm --name matrix_synapse_rust_synapse_auto_compress_state --user={{ matrix_user_uid }}:{{ matrix_user_gid }} --cap-drop=ALL --network={{ matrix_docker_network }} --mount...

Another one with ordering issues, https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1253

Another service start order issue, etherpad has permission issues in the current ordering, which requires its service be restarted before any pads will load.

> Can you elaborate? On a `--tags=setup-all,start`, everything starts up without any obvious errors on the systemd side, however, attempting to access an embedded etherpad within a channel gets an...

Since you're polling, I suggest a secondary poll of the arch people are running.

That's a big list of failures. :-/ Will see how much effort it is to clean these up.

The container which does the backups has some documentation on how to restore: https://github.com/prodrigestivill/docker-postgres-backup-local#restore-examples

> Do you think those reported numbers should always relate to the queried repository? Yes, that is what I expected. > I personally find it much more useful to know...

I'm not wedded to any particular way to display, the circles and arrows both sound reasonable, I'd just like it to be more clear what the relationship is for the...

I'm fine with the solutions presented, but I'd also like it to be made clear where the which results displayed are a higher order forks.