-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ: Third Party Apps & Configuration (Stakeholder)
Once you clone the repository to your local disk, you must add an .env file in each /frontend and /backend folder. Please remove these sensitive information from Github. Sensitive information is given to stakeholder. Select gitignore to avoid uploading access information onto the repository.
JWT_KEY=<<***********>>
RDS_HOSTNAME=<<***********>>
RDS_PORT=<<***********>>
RDS_USERNAME=admin
RDS_PASSWORD=<<***********>>
RDS_DATABASE=<<<<***********>>
LOCAL_API_KEY=<_your-ip-address_>:3000
REACT_NATIVE_PACKAGER_HOSTNAME=
Story: [#IssueNumber]: For As a Contractor, I would like to see my own views when I log in.
Task: Task Statement.
Steps:
- First step outlined: [#IssueNumber, SP]
- Second issue outlined: [#IssueNumber, SP]
[Total SP: X]
[Priority: Low, Medium High]
[Risk: Low, Medium, High]
A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Details on how to fork a repository can be found here.
-
Codacy Code Quality, Static Analysis and Coverage Tool: Codacy is an automated code analysis/quality tool that helps developers ship better software, faster. With Codacy, you get static analysis, cyclomatic complexity, duplication and code unit test coverage changes in every commit and pull request. Link to the Project Mender Codacy Dashboard can be found here.
-
Istanbul Javascript Code Coverage Tool Guide: Code coverage tells you when code you have written is being executed so you can decide if un-covered lines are superfluous (and can be removed) or require additional testing.
- CircleCI Orb Configuration with Codacy Coverage Guide: CircleCI automatically runs your build and test processes whenever you commit code, and then displays the build status in your GitHub branch.
You can also go directly to each of these status dashboards by clicking on the Repository badges on the front page.