This repository was archived by the owner on Sep 20, 2021. It is now read-only.
[WIP] Fix config so we can run in production mode#158
Open
dsamojlenko wants to merge 3 commits into
Open
Conversation
Member
|
I want to hold off on this until we get the app running in the cloud environment. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This fixes some config defaults so we can run the service in production mode.
Basically just had to configure the allowedOrigins for web sockets - we're not using web sockets at the moment, so this doesn't really matter... just set it to the BASE_URL from the environment.
With this change, I was able to run
npm install --productionand thennpm run startwhich brings the service up in production mode. I then ran the cypress tests, and everything is green.I also updated the Dockerfile to build and run in production.