Describe the bug
Initially, the frontend will not be able to send requests to the backend (tested through the login and register routes). This is because all requests are proxied to the port 4000, but the backend (both dev and production) are running on port 3000 by default.
This leads to all requests failing to be fulfilled.
To Reproduce
Steps to reproduce the behavior:
cd labellab-clientnpm installnpm start- New terminal window
cd labellab-servernpm installnpm start or npm run dev- Perform any request on the frontend and observe the error in the frontend console log.
Expected behavior
Requests are fulfilled by the backend.
Screenshots
Backend starting on port 3000
Proxy pointing to the wrong port
Desktop (please complete the following information):
- OS: Windows 10
- Browser: Chrome
- Version: 80
Additional context
Should be solved by updating the proxy value. I can make a pull request for this, given permission.
Describe the bug
Initially, the frontend will not be able to send requests to the backend (tested through the login and register routes). This is because all requests are proxied to the port 4000, but the backend (both dev and production) are running on port 3000 by default.
This leads to all requests failing to be fulfilled.
To Reproduce
Steps to reproduce the behavior:
cd labellab-clientnpm installnpm startcd labellab-servernpm installnpm startornpm run devExpected behavior
Requests are fulfilled by the backend.
Screenshots
Backend starting on port 3000
Proxy pointing to the wrong port
Desktop (please complete the following information):
Additional context
Should be solved by updating the proxy value. I can make a pull request for this, given permission.