raven, flyingpigeon: undo outputpath dir change, only keep finch

Since finch will have the new pywps with the fix to create directory
paths, we will only keep the config changes for finch.

Once raven and flyingpigeon have the new pywps we can then do the same
for them.

birdhouse/config/flyingpigeon/wps.cfg.template

@@ -1,6 +1,6 @@
 [server]
-outputurl = https://${PAVICS_FQDN_PUBLIC}/wpsoutputs/flyingpigeon
-outputpath = /data/wpsoutputs/flyingpigeon
+outputurl = https://${PAVICS_FQDN_PUBLIC}/wpsoutputs
+outputpath = /data/wpsoutputs
 maxsingleinputsize = 2097152000.0
 
 [logging]

birdhouse/config/raven/wps.cfg.template

@@ -1,6 +1,6 @@
 [server]
-outputurl = https://${PAVICS_FQDN_PUBLIC}/wpsoutputs/raven
-outputpath = /data/wpsoutputs/raven
+outputurl = https://${PAVICS_FQDN_PUBLIC}/wpsoutputs
+outputpath = /data/wpsoutputs
 
 # default 3mb, fix "Broken pipe" between the proxy and the wps service
 maxrequestsize = 100mb

birdhouse/pavics-compose.sh

@@ -202,11 +202,6 @@ do
       docker exec ${postgres_id} /postgres-setup.sh
     fi
 
-    # because server.outputpath in wps.cfg do not create the dir
-    for bird in finch flyingpigeon raven; do
-      docker exec $bird mkdir -p /data/wpsoutputs/$bird/tmp /data/wpsoutputs/$bird/workdir
-    done
-
     for adir in ${EXTRA_CONF_DIRS}; do
       COMPONENT_POST_COMPOSE_UP="$adir/post-docker-compose-up"
       if [ -x "$COMPONENT_POST_COMPOSE_UP" ]; then