When trying to run these projects on your own local environment, you need to navigate to each folder and install dependencies. To much to push and .env should probly not be added as files to repo, but this is the simplist workaround i could do.
For example:
cd backend
npm install
For backend (Run this first, its used as a proxy for frontend on port 3000):
cd backend
npm install
For frontend:
cd frontend
npm install
For frontend2:
cd frontend2
npm install
ALTERNATIVELY for backend You can use the docker file to run the backend. Will need to create .env file however, an example file has been provided. If you want to use myne, message me for IP whitelisting For frontend2:
cd backend
docker-compose up --build
Add .env file (frontend2):
You can use your own MongoDB cluster, as your IP will not be whitelisted.
Contact me at moolmans20013@gmail.com
or st10219213@vcconnect.edu.za
to have your IP added to the whitelist if needed.
I check the first email daily, but the latter not as frequently.
Furthermore, the unit tests run on a self-hosted machine, so they will only execute if my machine is active while running my workflow runner.
- CircleCI & SonarCube integration
- React Bootstrap
- Loading screens & animations
- CAPTCHA verifications
- Unit tests with preconfigured account
- SonarCube quality profile rules (JavaScript) for detecting code smells and hardcoded secrets
- Search option for payments in the employee portal
- SSL on backend and frontend, with salted and encrypted passwords
- Security tools: HSTS, Helmet, Validator, bcrypt, csurf, fs, ExpressBrute (Backend)