From a2d29a91d7fefe5062b28f331c1a2bf091d8276c Mon Sep 17 00:00:00 2001
From: Andrei Ismail <iandrei@gmail.com>
Date: Sun, 12 Jul 2015 16:35:39 +0300
Subject: [PATCH] #310 Mounting the existing code as an external volume

This was the only way of ensuring the code was fresh inside the docker
container. However, this comes with the challenge of actually compiling
code after the volume has been mounted, but before starting the daemon.
---
 scenarios/1backend/docker-compose.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scenarios/1backend/docker-compose.yml b/scenarios/1backend/docker-compose.yml
index 52c3528e6..e6af8abac 100644
--- a/scenarios/1backend/docker-compose.yml
+++ b/scenarios/1backend/docker-compose.yml
@@ -9,6 +9,8 @@ proxysql:
     - "6033:6033"
     # gdbserver
     - "2345:2345"
+  volumes:
+    - /tmp/proxysql-tests:/opt/proxysql
   privileged: true
 
 backend1hostgroup0: