Fixes #1261: docker compose up --build doesn't see .env

[IsabellaDev]

Issue This PR Addresses

Closes #1261

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

This adds the command line COPY .env . right after the package.json file is copied for each service, and removes the command line COPY ./.env ./.env in the Front-end Builder context.
It solves the problem that the error "cannot find .env file" being thrown when doing the docker-compose up --build.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[c3ho]

Hi, can I get more context in the title of this PR? Fixed issue #1261 doesn't tell me much. There's no description and you didn't add Fixes #1261 either in Issue this PR addresses so it didn't automatically link the issue

[c3ho]

@raygervais do we also need the code in line 49?

COPY ./src/frontend ./src/frontend	COPY ./src/frontend ./src/frontend
COPY ./.git ./.git	COPY ./.git ./.git
COPY ./.env ./.env <--- this line

[raygervais]

From what I see, we don't need the second copy because the added line is for the base container, meaning each other container will inherit the .env file

[IsabellaDev]

Fixes #1261

[c3ho]

I mean here

[IsabellaDev]

I mean here

Oh, I'm so sorry that I didn't notice I can type in those places, should I modify it now?

[c3ho]

Yeah, if you have questions, look at another PR and try to edit their PR (without actually making changes) to understand how to write/format