Manage Jitsi through Ansible using custom role #172

Open
stb wants to merge 5 commits from jitsi-docker-compose-role into main
Owner

A new role uses the recommended [Jitsi Docker Compose setup|(https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/). The inventory is updated to use the new role. The host has been manually cleaned and all old packages and config have been removed.

A new role uses the recommended [Jitsi Docker Compose setup|(https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/). The inventory is updated to use the new role. The host has been manually cleaned and all old packages and config have been removed.
We need this role to follow the recommended deployment approach from https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/

This role enables us to keep our config and customizations separate from releases of the Compose setup the Jitsi project publishs.
Use jitsi role to configure jitsi
All checks were successful
/ Ansible Lint (push) Successful in 3m47s
/ build (pull_request) Successful in 44s
/ Ansible Lint (pull_request) Successful in 3m45s
86e793c624
The host has been manually cleaned up (removed old packages and config) and this config has been deployed already.
You can view your changes at https://staging.infra-docs.hamburg.ccc.de/pr172/
Customize with our logos
All checks were successful
/ build (pull_request) Successful in 30s
/ Ansible Lint (push) Successful in 2m58s
/ Ansible Lint (pull_request) Successful in 3m15s
8bf5690275
lilly left a comment

Was there a reason that you did not use our existing docker-compose role?

Was there a reason that you did not use our existing docker-compose role?
Author
Owner

@lilly wrote in #172 (comment):

Was there a reason that you did not use our existing docker-compose role?

Yes, it would have required creating a complete docker compose setup by hand, instead of using the well-maintained one from upstream. The new role uses that setup directly, and only overrides env/settings through the mechanisms provided. The new role downloads a new version of the docker compose setup from the Github release, and renovate is used to automatically check for updates there.

@lilly wrote in https://git.hamburg.ccc.de/CCCHH/ansible-infra/pulls/172#issuecomment-7321: > Was there a reason that you did not use our existing docker-compose role? Yes, it would have required creating a complete docker compose setup by hand, instead of using the well-maintained one from upstream. The new role uses that setup directly, and only overrides env/settings through the mechanisms provided. The new role downloads a new version of the docker compose setup from the Github release, and renovate is used to automatically check for updates there.
Merge branch 'main' into jitsi-docker-compose-role
All checks were successful
/ build (pull_request) Successful in 30s
/ Ansible Lint (push) Successful in 5m9s
/ Ansible Lint (pull_request) Successful in 5m46s
816c7497fa
All checks were successful
/ build (pull_request) Successful in 30s
Required
Details
/ Ansible Lint (push) Successful in 5m9s
Required
Details
/ Ansible Lint (pull_request) Successful in 5m46s
Required
Details
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin jitsi-docker-compose-role:jitsi-docker-compose-role
git switch jitsi-docker-compose-role
Sign in to join this conversation.
No description provided.