Use configuration to determine what services to expose publicly

[dannylamb]

ISLE lets users choose what services to deploy with variables in the .env, but whether or not they're exposed publicly isn't configurable. If we take our current docker-compose.*.yml files, we can set these up to run off of config using the traefik.enable label.

For example, in docker-compose.activemq.yml, we could do

      - traefik.enable="${EXPOSE_ACTIVEMQ}"

and then we could set $EXPOSE_ACTIVEMQ=true to enable or $EXPOSE_ACTIVEMQ=false to disable the route using the .env file.

We'd need to do this for:

• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.activemq.yml
• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.blazegraph.yml
• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.cantaloupe.yml
• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.drupal.yml
• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.fcrepo.yml
• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.solr.yml
• https://github.com/Islandora-Devops/isle-dc/blob/development/docker-compose.traefik.yml

[noahwsmith]

Both #1665 and #1666 should be done first.

[joshdentremont]

I see a lot of the yml files have comments that say do not expose in production. As part of this change would it be worth changing the defaults to false, so that they need to be manually exposed in the .env? That way we could also include these comments in the .env and if someone wants to turn them on they have been warned.