react-express | Learn React through interactive examples | Learning library

I believe there are two things that need to be changed. One on your initialControler.js you are using export default in a node.js file, use module.exports module.exports vs. export default in Node.js and ES6

You should change all the imports in your node files.

You use export / export default in React and then import to pull in the files https://www.geeksforgeeks.org/reactjs-importing-exporting/

module.exports and require to pull in the files for Node What is the purpose of Node.js module.exports and how do you use it?

Second they moved the app.get into that renderReact.js file and then required it into their index.js file. However on your server.js file I don't see you importing in your initialController file.

From your example it looks like you should be doing something like this:

Server.js

As you say in the comment, you map a directory to /etc/nginx when you run the container.

When you map ./nginx:/etc/nginx, the volume mapping wins and 'hides' the files in the image.

As convert is an async function, and thus returns a promise, replace:

If I understood your question correctly. to redirect using react-router in javascript parts of code, you should use history object that is in the route component's props (if your component is not connected to Router directly, you can use withRouter HOC) instead of using component (it is JSX and only related to render part).

like: this.props.history.push('/route_name', { Email, Response })

you are also checking email message using double equals. you should change it to === (triple equals). also, try to find a better approach to finding out if the request was successful or not.

I found the solution to prevent my frontend service from exiting with 0. I had to add tty: true for it in my docker-compose.yml file. Also, to make the frontend-backend interaction work as expected in the app, I had to change my proxy command in my client's package.json to the following:

change your onreadystatechange method to this and it will work:

Did some more googling and someone suggested it was a network issue, so i fiddled with my VPN and it finally worked.

So, if you run into this, check that you have proper network connection working.

It seems to me that you didn't provide the full API URL to axios, if you haven't created baseURL for axios, just provide the full URL localhost:800/api/dogs:

Most streaming protocols require session affinity. Try setting up sticky sessions on your load balancer. Here's how to for classic ELB: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html

Unfortunately that also pins the other traffic as well, but better than 50% failure.