186 production ready docker compose

[orangewolf]

Randy - this needs some feedback from you.

1) we seperated out the production docker-compose from the dev one. This means on your server you'd change your docker-compose commands to docker-compose -f docker-compose.production.yml. We often set an alias on the server for this so that dc='docker-compose -f docker-compose.production.yml'

2) we generally do not build the images on the production box, but instead build in CI and pull the images down. It looks like you probably have been building on the prod box. If you want to keep doing that, we can add support for building back in to the production docker-compose. Is that something you want?

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [4917448](https://dashboard.gitguardian.com/incidents/4917448?occurrence=90557051) | Company Email Password | e52b21db7617226161b75c5367f82ffb434a5b19 | .env.development | [View secret](https://github.com/scientist-softserv/louisville-hyku/commit/e52b21db7617226161b75c5367f82ffb434a5b19#diff-da4c41d59c967338247b2f0ea6d845ab05171f942fd9521b96d3304202185db9R30) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/detectors/generics/company_email_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[rkuehn-uofl]

Hey Rob, No, you can leave everything as is...the docker-compose.yml and docker-compose-production.yml files separate. We have several VMs running (a couple for testing and one that will be our production box). We can work with either setup. The problem we're having is getting fcrepo to start with the JAVA_OPTS settings using either of the dev or prod dc files. The settings do appear in the container, but fcrepo doesn't seem to be looking in the right place. Oh, I also didn't approve it because I left a password in the file on line #38. :\ Thanks!

[alishaevn]

git guardian is failing because of the SOLR_ADMIN_PASSWORD value in the env. that value is in other repo's as well though, so it's not a merge halting factor.

the tests are already failing on main, but lint won't even run.