signalytic/streamline-emr
1
0
Fork 0
mirror of https://gitlab.com/signalytic/client-external/streamline/streamline-emr.git synced 2026-09-11 10:41:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

updates to docker-compose.yml and documentation to allow runtime configuration

Browse Source 
Further configuration options are made available to support running multiple
instances of the app on the same machine, including the use of docker sibling
containers. `README.md` and `template.env` are updated accordingly.

The database port is no longer exposed as this is not required to access and
manage the app at this time.
This commit is contained in:
alec.turner
2024-03-01 11:05:50 -08:00
parent 1a4756fda0
commit 7c528766b0
3 changed files with 14 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -3
View File
@@ -33,8 +33,13 @@ In a docker environment, the application must be started manually. This is done
/var/signalytic/clientapps/streamline/streamline-emr/entry
```
If multiple instances are run from the same machine, additional configuration may be required to differentiate the instances. This is generally the case when using the "sibling container" method for running docker from within a docker container. See the `Configuration` section for more details.
## Configuration
Certain configuration options can be adjusted by setting environment variables or by defining these variables in a `.env` file stored in the same directory as the `docker-compose.yml` file. These variables are:
`APP_PORTS`: port mapping for the web app server (default: `3000:80`)
`DB_PORTS`: port mapping for the database server (default: `6607:3306`)
`CONTAINER_NAME`: name of the application container (default: `streamline-emr`)
`APP_PORT`: port mapping for the web app server (default: `3000`)
`CONTAINER_NAME`: name of the application container (default: `streamline-emr`)
`DATA_DIR`: directory to be mounted for peristent data (default: `/var/signalytic/clientapps/streamline/streamline-emr/data`)
`COMPOSE_PROJECT_NAME`: assign the project name associate with the compose file - this avoids conflicts when the "same" compose file is used to manage multiple instances (e.g. when using docker sibling containers)
Important note when using "sibling containers": the sibling container method uses the host docker socket to provide containers with access to docker. As a result, port mappings and volumne mount points all refer to the host system rather than the container from which the docker command originates.