correct entry script bug and allow config from env file

- A bug in `entry` caused the script to not change into the directory correctly.
This was corrected by marking the script as bash rather than sh.
- `install.sh` now stops a running service before updating
- `docker-compose.yml` now assigns a consistent container name for the app
- `docker-compose.yml` now uses environment variables or a `.env` file to
  assign container name and port mappings if available
- updated readme file with better instructions

root/var/signalytic/clientapps/streamline/streamline-emr/docker-compose.yml

@@ -2,8 +2,9 @@ version: '3.9'
 services:
   streamline-emr:
     image: registry.gitlab.com/signalytic/client-external/streamline/streamline-emr:2.0
+    container_name: ${CONTAINER_NAME:-streamline-emr}
     volumes:
         - '/var/signalytic/clientapps/streamline/streamline-emr/data:/var/lib/mysql'
     ports:
-      - '3000:80'
-      - '6607:3306'
+      - ${APP_PORTS:-3000:80}
+      - ${DB_PORTS:-6607:3306}

root/var/signalytic/clientapps/streamline/streamline-emr/entry

@@ -1,5 +1,17 @@
-#!/bin/sh
-cd "$(dirname "${BASH_SOURCE[0]}")"
+#!/bin/bash
+
+APPROOT="$(dirname "${BASH_SOURCE[0]}")"
+
+echo "entering app root: $APPROOT"
+cd $APPROOT
+
+echo "creating data folder (if necessary)"
 mkdir -p data
-docker compose up --force-recreate
+
+echo "starting app"
+docker compose up
+
+echo "cleaning up"
 docker compose down
+
+echo "done."