One option is to set an environment variable (perhaps one is even already available) which can then be referenced during build using variable expansion as shown in the article. Another option would be to configure openshift to run different commands for each environment. I have not used openshift and don’t know how to do this.
Are you trying to set
qa? The value of
NODE_ENV is set for you based on how create-react-app is run. For example,
npm start will result in a value of
NODE_ENV. Out of the box, create-react-app supports three environments (see the Built-in support section of the article). If you want an additional environment use a variable name other than
NODE_ENV and follow the steps in the article.
Yes, because create-react-app produces a static bundle of files, the values of the configuration will be part of that bundle, but only those values for the current environment. For example, the values use in the development environment would not be included in a production build.
I understand your point, and I agree that Bitcoin’s network effect is a powerful backer that is unlikely to suddenly evaporate. The best evidence of this is the continued increase in value of Bitcoin, despite many boom/bust cycles and competing chains.
I don’t recommend this method—it doesn’t have any advantage over the method described in this article (especially with the recent update on react-app-env), but does have the disadvantage of unexpectedly/accidentally overwriting a file with uncommitted changes.