Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NODE_ENV setting is ignored by dockerStart.sh of data-portal #25

Open
taoliu opened this issue Mar 20, 2019 · 0 comments
Open

NODE_ENV setting is ignored by dockerStart.sh of data-portal #25

taoliu opened this issue Mar 20, 2019 · 0 comments

Comments

@taoliu
Copy link

taoliu commented Mar 20, 2019

- NODE_ENV=dev

The above code will set the NODE_ENV to "dev" in docker-compose.yml, however, this setting is ignored later on by data-portal. When "waitForContainers.sh" is called:

command: ["bash", "/var/www/data-portal/waitForContainers.sh"]

The script invokes "dockerStart.sh" in data-portal:

bash ./dockerStart.sh

The dockerStart.sh will reset NODE_ENV as "production":

https://github.com/uc-cdis/data-portal/blob/c211f476f4ebacfe03b36bf471fb910e72aa81b4/dockerStart.sh#L8

export NODE_ENV=production

The consequence is that the NODE_ENV setting in compose-service is ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant