#281 Implemented Dockerfile and deployed the backend on aws #308
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alitpc25
changed the title
|
I switched the deployment from render to AWS since it is more reliable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dockerfile is created, image pushed to dockerhub and the backend is deployed on render.com. API Documentation is on https://resq.onrender.com/resq/api/v1/swagger-ui/index.html. Endpoints except /auth is authenticated. So, to send a request, first /auth/signin and take jwt token. Then, click the Authorize button in the top of the swagger page, paste the jwt token that was given after signin. Now, you are authorized to send requests via API Documentation. Also, you need to add header value to X-Selected-Role.