From 676d0bf21f3c263ffea0ce3cc1c4c2f3365c0d4b Mon Sep 17 00:00:00 2001
From: Atul Varma <varmaa@gmail.com>
Date: Thu, 3 Sep 2020 07:36:29 -0400
Subject: [PATCH] Fix location of data volume on nycpad_normalizer

The `docker-compose.yml` mounts the data volume on `/data`, but the actual container writes its data (which is later retrieved by the `nycpad` container for importing) to `/usr/local/src/scripts/data`.  This changes the location of the mount to match where data is written, so that everything works as expected when `pelias import nycpad` is run.
---
 docker-compose.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 1f84dc3..c5e4a15 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -53,7 +53,7 @@ services:
       context: "http://github.com/nycplanning/labs-geosearch-pad-normalize.git"
     container_name: pelias_nycpad_normalizer
     volumes:
-      - "${DATA_DIR}:/data"
+      - "${DATA_DIR}:/usr/local/src/scripts/data"
 
   # The ES backend
   elasticsearch: