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.

Sign up for GitHub

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

Jump to bottom

use a different backend url when the frontend is built in production mode #57

Closed
GRarer opened this issue Feb 24, 2021 · 0 comments · Fixed by #80
Closed

use a different backend url when the frontend is built in production mode #57

GRarer opened this issue Feb 24, 2021 · 0 comments · Fixed by #80
Assignees
@GRarer
Labels
integration and deployment work related to building and deploying to the web
Milestone
Sprint 5

Comments

@GRarer
Copy link
Owner

GRarer commented Feb 24, 2021

in order to deploy the backend to a server, the frontend needs to be able to substitute in a non-localhost url when it is built in production mode. for most of our endpoints this could be handled by the API service, but there are also endpoints that the session service accesses without the api service
@GRarer GRarer added this to the Sprint 5 milestone Feb 24, 2021
@GRarer GRarer added the integration and deployment work related to building and deploying to the web label Feb 26, 2021
@GRarer GRarer mentioned this issue Mar 15, 2021
Closed
@GRarer GRarer self-assigned this Mar 15, 2021
@GRarer GRarer mentioned this issue Mar 15, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GRarer GRarer

Labels
integration and deployment work related to building and deploying to the web
Projects
None yet
Milestone
Sprint 5
Development

Successfully merging a pull request may close this issue.

connect production frontend to AWS backend GRarer/boop
1 participant
@GRarer