Manage Jitsi through Ansible using custom role #172
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
renovate
waiting on upstream
wontfix
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
CCCHH/ansible-infra!172
Loading…
Reference in a new issue
No description provided.
Delete branch "jitsi-docker-compose-role"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
You can view your changes at https://staging.infra-docs.hamburg.ccc.de/pr172/
Was there a reason that you did not use our existing docker-compose role?
@lilly wrote in #172 (comment):
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.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.