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

Connect FrontEnd to BackEnd Correctly #119

Open
Jooms opened this issue Apr 11, 2023 · 1 comment
Open

Connect FrontEnd to BackEnd Correctly #119

Jooms opened this issue Apr 11, 2023 · 1 comment
Assignees
Labels
backend concerns backend/API presentation

Comments

@Jooms
Copy link
Contributor

Jooms commented Apr 11, 2023

From #101

  1. Set up environment variables for the frontend to point to the correct backend. (Localhost when dev, EnvVar when prod)
  2. Configure CORS correctly (from EnvVar) when deploying backend.

We should be able to use a runtime-injected value for what backend a frontend should be talking to, and what frontend a backend should listen to.

@Jooms Jooms changed the title Connect FrontEnd to BackEnd with Environment Variables Connect FrontEnd to BackEnd Correctly Apr 11, 2023
@hardikpatil hardikpatil added the backend concerns backend/API presentation label Apr 14, 2023
@prestonmasseyblake prestonmasseyblake self-assigned this May 2, 2023
@MMurtey
Copy link
Contributor

MMurtey commented May 8, 2023

See the branch register_backend_connect. This works in dev, anyway. @prestonmasseyblake, it turned out not to be a CORS issue (it's already set to be permissive), but the backend not explicitly "listening" on port 3000. On that branch, registration now correctly posts data to the database and returns a simple JSON response in the form {"status": true/false, "message": details about operation results}. See also #120

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

No branches or pull requests

4 participants