Introduced small .env change and docker-compose.override.yml

[McFateM]

I've been doing extensive testing of ISLE v1.1 requiring frequent changes to docker-compose.yml. Lately I've started using the override feature of docker-compose and suggest adoption of this feature in ISLE going forward. The capabilities of this feature are documented at https://docs.docker.com/compose/extends/.

This PR added a very small addition to the existing .env file, and takes advantage of that addition by introducing a new docker-compose.override.yml file into the stack.

[bseeger]

Hi Mark, by putting the override file there, it automatically makes it be used, right? Are you suggesting that this be the canonical way to use ISLE? Will all users want the changes you've made to this file?

What I'm wondering is if we want it in there as an option, but not active unless people chose to make it active.

[McFateM]

Yes and no. Yes, if you name the file `docker-compose.override.yml` is is “automatically” included. You can, of course, select other names for this file, or have more than one, but the inclusion is no longer automatic, and frankly things get a little too complicated IMHO. No, I’m not suggesting that my override becomes a canonical copy. I’m just looking for us to "encourage" the use of a `docker-compose.override.yml` for customizations, and maybe we do that in documentation AND possibly by providing a simple example/template for folks to build on.

…

-Mark M. On Mar 29, 2019, at 12:59 PM, B. Seeger <[email protected]<mailto:[email protected]>> wrote: Hi Mark, by putting the override file there, it automatically makes it be used, right? Are you suggesting that this be the canonical way to use ISLE? Will all users want the changes you've made to this file? What I'm wondering is if we want it in there as an option, but not active unless people chose to make it active. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Islandora-2DCollaboration-2DGroup_ISLE_pull_214-23issuecomment-2D478093613&d=DwMFaQ&c=HUrdOLg_tCr0UMeDjWLBOM9lLDRpsndbROGxEKQRFzk&r=PQglHQe-EzyZqJOuOVcmU0OZ6bg-89msSPuqyNlQr28&m=4ZWUiJE_Lds9ywQaRYYzo3-mxlh2ok3Pedl0rJaic2s&s=QbBd6eRL70aRn9ecPfbIy56iixckhDiXZp-RVGtyEpo&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AIFIwfs0nU82UuTO-5FSD069VtnvlzxmH-2Dks5vblRngaJpZM4cQRUe&d=DwMFaQ&c=HUrdOLg_tCr0UMeDjWLBOM9lLDRpsndbROGxEKQRFzk&r=PQglHQe-EzyZqJOuOVcmU0OZ6bg-89msSPuqyNlQr28&m=4ZWUiJE_Lds9ywQaRYYzo3-mxlh2ok3Pedl0rJaic2s&s=WzQu04PkoUewrbucD8IyGXEHiLE6oE1OOQEWuyjndGQ&e=>.

[McFateM]

OK, I'd like to close this PR in favor of a little different approach that I think may be easier to manage and document. See Issue #216 for details.