LF-4722b Fix start:prod path to match container structure #3683
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is the follow-up to the PR and the solution was tested live (successfully) during tech daily Feb 6
When merging that PR we saw that the
/dist
folder was successfully built within the container image. The issue was thattsc
copies the directory structure of its source, and in the Docker image the path has been set up as/app/src/server.js
instead ofapi/src/server.js
. This PR just changes thestart:prod
script path to match this.As a side effect you cannot use
npm run start:prod
locally after this change but as it was meant to be used in hosted container I don't see this as an issue.@Duncan-Brain I did not delete the
npm run start
script here because it is used by the Cypress tests.Jira link: https://lite-farm.atlassian.net/browse/LF-4722
Type of change
How Has This Been Tested?
We have already tested the change on the droplet directly and it worked to get the backend container up and running again.
Checklist: