Run project on your local machine
This will create a node_modules folder containing installed packages.
npm i
This will copy and paste .env.example to the directory and rename to .env.
Ask for the values of .env file server
cp .env.example .env
npm run dev
Server will run on localhost on port 8002:
http://localhost:8002
Run project on your local machine
This will create a node_modules folder containing installed packages.
npm i
This will copy and paste .env.example to the directory and rename to .env.
Ask for the values of .env file server
cp .env.example .env
npm start
Server will run on localhost on port 3000:
http://localhost:3000
Branch naming guidelines:
-
feature/feature-name- For code that adds a feature. -
fix/fix-name- For code that needs fixing from an existing feature. -
adjustment/adjustment-name- For code that needs changes to an existing feature.
Commit according to codes' purpose. If your adding a new feature, make sure to use proper commit message, e.g: [Feature][Jona] Create middleware
Commit messages format:
[Commit type][dev-name] message
Commit Types:
Feature- For commits that adds a feature.Fix- For commits that has fixes from an existing feature.Adjustments- For commits that has changes to an existing feature.
Make sure your branch is in sync with the dev branch. To do so, try to pull from the dev branch more often to avoid code conflicts. Check your code, if no conflicts found, you're good to go.
When ready, create a Pull Request from your branch to the dev branch.
Good Job! Keep it up!! 🥳😎