Renamed 'job_cache' as 'cache' since we use Redis also for messaging and logging + minor changes.

  variables:

    IMAGE_NAME: base

dockerize_job_cache:

dockerize_cache:

  <<: *docker-build-template

  variables:

    IMAGE_NAME: job_cache

    IMAGE_NAME: cache

dockerize_transfer_service:

  <<: *docker-build-template

- Client (container_name: client), is used to provide to the user some useful command line tools to interact with the backend

- Transfer service (container_name: transfer_service) is the core of the backend architecture

- Redis (container_name: job_cache), is used as a cache for job queues and as message broker to deliver messages containing requests from the user command line tools and from the VOSpace REST APIs

- Redis (container_name: cache), is used as a cache for job queues, as message broker to deliver messages containing requests from the user command line tools and from the VOSpace REST APIs and also for basic centralized logging

- File catalog (container_name: file_catalog), now available [here](https://www.ict.inaf.it/gitlab/vospace/vospace-file-catalog), is a posgresql database used to store information on VOSpace nodes, but also on storage locations, jobs and users.

```

2. Use *redis-cli* command to connect to Redis:

```

redis-cli -h job_cache

redis-cli -h cache

```

3. You can obtain some info about the jobs by searching them on the following queues:

   - for write operations the queues are *write_pending*, *write_ready* and *write_terminated*