Use Fig to start your cluster, then interactively your containers as needed. As you modify stuff, the services emit logging messages, which you can see in the second terminal.
here's the code for the second terminal. It uses Fig to get logs for all the containers. When the config is changes and the cluster is restarted, this command loops again to reconnect and get all the new log messages. In this way you can just do you work and this terminal will always have the latest logs.
Watch Docker cluster logs, even after restart
for ((;;)) ; do fig logs ; done
tl;dr: infinite loops ftw