jotbe
deleted branch feature/optional_install_of_ansible from jotbe/ansible-role-common
2021-03-27 14:31:47 +01:00
Makes installation of Ansible optional (default: no) and installs additional python libraries
jotbe
pushed to feature/optional_install_of_ansible at jotbe/ansible-role-common
2021-03-27 14:29:42 +01:00
Makes installation of Ansible optional (default: no) and installs additional python libraries
jotbe
pushed to feature/optional_install_of_ansible at jotbe/ansible-role-common
2021-03-27 14:27:07 +01:00
feature/sudoers_revamp
feature/sudoers_revamp
feature/latest-upstream-docker-compose
Good point! Yes, could be, but it makes sense to create an Ansible var to allow a config of that JVB_PORT
which is still more or less hardcoded in the env file.
feature/latest-upstream-docker-compose
This should define a service entity for traefik which allows e.g. for loadbalancing. I haven't tried the loadbalancing yet. On the other hand, that entrypoint video
is not further defined here. I am not sure whether other configuration is missing here.
Added install path and consolidated var usage.
I would even rename the variable to something more generic, compare my comment regarding the docker_user
. That path is used with different service names across the self-services. Maybe something like:
docker_user: deploy # Could be overwritten when including the role
service_name: jitsi # Usually no need to change that
# We could overwrite the service_path when including the role, if we e.g. want to install another service `jitsi_2` or `jitsi-dev`.
service_path: /home/{{ docker_user }}/{{ service_name }}
jotbe
pushed to feature/latest-upstream-docker-compose at jotbe/ansible-role-jitsi-docker
2020-12-13 00:58:24 +01:00
jotbe
pushed to feature/latest-upstream-docker-compose at jotbe/ansible-role-jitsi-docker
2020-12-13 00:52:46 +01:00