Recnet-api backend service initilization #151
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
fix: shuffle users in search page and all-users page
joannechen1223
force-pushed
the
init-backend
branch
from
a610ace to
e5aa943
Compare
joannechen1223
force-pushed
the
init-backend
branch
from
483a585 to
ec805f6
Compare
joannechen1223
force-pushed
the
init-backend
branch
from
ec805f6 to
374a472
Compare
swh00tw
approved these changes
Feb 25, 2024
There was a problem hiding this comment.
If we want to separate different prettier configs for different projects, I would suggest you move the .prettierrc config file to the root of recnet-api project.
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Description
Create a project
recnet-apias a backend service for recnet. The project is built by NestJS under nx. In this initial PR, I created aGET /healthendpoint for testing purpose.The code should be auto-deployed to AWS Elastic Beanstalk through the Codepipe line once merged to the master branch.
Related Issue
Create Nestjs backend and deploy to AWS
Notes
Dev Flow and CI
After discussing with @swh00tw , we decided to maintain a
recnet-api-devbranch for merging dev environment. Once a new feature PR is merged, it will automatically deploy to our dev environment. If everything is good to go, I will create another PR to mergerecnet-api-devbranch to merge tomaster.Code build issue investigation
TL, DR
pnpminstalls node_modules with symlinks, so we'll need to addenable-symlinkin the build spec.AWS deployment issue
TODO