Initial incubator resources for container build

[tylerthome]

Completes some items from #627

What changes did you make?

• add Dockerfile definitions for base and app container images to .incubator directory
• add auxiliary files (e.g. nginx config, entrypoint bash script) to .incubator directory

  Rationale behind the changes?

• prepare for GitHub Action deployment to incubator ECR and ECS

  Testing done for these changes

• deployment to ECR

  What did you learn or can share that is new?(optional)

• Dockerized nginx customization for server blocks (without TLS), in contrast to existing EC2 configuration

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

N/A

[tylerthome]

gunicorn is not a dependency anymore and I can't see where it's being installed. You might be able to get away with running the fastapi run app/main.py --port 8000 command instead.

Good call @paulespinosa - I made this change as you suggested. It's using a virtual env there now because there was an issue running either of the fastapi and uvicorn commands as such in the entrypoint.sh. They could run with poetry run but this caused module references to fail while resolving from import paths. This approach worked as expected in the incubator deployment currently running at https://qa.homeunite.us, but open to any alternative approaches if this looks familiar to anyone.

[paulespinosa]

gunicorn is not a dependency anymore and I can't see where it's being installed. You might be able to get away with running the fastapi run app/main.py --port 8000 command instead.

Good call @paulespinosa - I made this change as you suggested. It's using a virtual env there now because there was an issue running either of the fastapi and uvicorn commands as such in the entrypoint.sh. They could run with poetry run but this caused module references to fail while resolving from import paths. This approach worked as expected in the incubator deployment currently running at https://qa.homeunite.us, but open to any alternative approaches if this looks familiar to anyone.

It looks good. Nothing off the top of my head can think of doing it any other way. Nice work!