Configure prod server so that can serve web-client and web-client-classic

[ceciliazaragoza]

Currently, the web-client demo API setup can only access the local server. Configure the web-client API so that it can access the prod server. Ensure that the prod server can serve both web-client and web-client-classic at the same time.

[ceciliazaragoza]

I am configuring the deployed react app to be able to access the prod server. I think I may be running into a larger question of where the requests from the react app should originate from.

• The request from the react app to the server originates from https://dondi.github.io
• However, in prod, the requests originate from https://grnsight.lmucs.org

In web-client-classic, GRNsight is in an iframe at https://grnsight.lmucs.org within the page https://dondi.github.io. But the react app is currently directly being served at https://dondi.github.io.

I am going to put the app in an iframe so that I can begin simulating the same framework as prod. Which port should I configure the react app to serve at for https://grnsight.lmucs.org? Should it be 3000 or another port?

• I could also allow https://dondi.github.io to access the server, but that would stray from our current setup.

My draft PR can be viewed here: #1279

[dondi]

@ceciliazaragoza I can see two possibilities here:

• Can the config corsOrigin attribute be made to accept an array? That way we can do something like corsOrigin: ["//grnsight.lmucs.org", "//dondi.github.io"]
• We can make a brand new react config that is identical to beta except for corsOrigin. We would have to make a new clone of the GRNsight repo on our server and run that one with the react config

The first approach feels leaner if it’s doable. But if not, I think we can live with the second approach. It’s transitional anyway; once the React app takes over, this can become the standard configuration