What do we want to do?
Let's add a new docker compose file to the Lupo project called docker-compose.dev.yml. We can then use this docker compose file to run Lupo locally and access the containerise API from Levriero (also running in a container).

Why do we want to do it?
The idea is to have Lupo and Levriero (and any other containers, if you want) running on the same network. This will allow these containers to communicate with one another.

Why a new docker compose file?
We can provide the Lupo API with a container name. Having a container name will allow us to much more easily refer to the API in other containers.

Why docker-compose.dev.yml?
There is already a docker-compose.local.yml and I don't want to mess with anything people are already using. I think the naming convention works well since this should only be used for/in development.