# jive5ab — Deployment

## Docker Image

| Property | Value |
|---|---|
| Image name | `jive5ab` |
| Ansible build role | `roles/jive5ab/` |
| Registry | `gitlab-registry.mpcdf.mpg.de/mpifr-bdg/edd/dbbc` |

The image installs the `jive5ab` binary from the MPIFR Aptly repository.

## Ansible Deployment

The service is deployed via the `jive5ab` role:

```bash
ansible-playbook provision.yml --tags jive5ab
```

The role starts the container via `EDD.core.common` with:

```yaml
image_name: jive5ab
default_container_name: edd_jive5ab
container_cmd: "jive5ab --port={{ jive5ab_port }} --message-level 3"
register_as_pipeline: False
launch_on_deploy: True
restart_policy: "on-failure"
volumes:
  - "{{ jive5ab_recording_path }}:/data/"   # only if jive5ab_recording_path is defined
```

## Key Ansible Variables

Defined in `roles/jive5ab/defaults/main.yml`:

| Variable | Default | Description |
|---|---|---|
| `jive5ab_port` | 2620 | MK5 control port |
| `jive5ab_recording_path` | _(undefined)_ | Host path mounted at `/data/` for recordings |

If `jive5ab_recording_path` is not defined, no volume is mounted and recordings stay
inside the container (lost on container removal).