eMJPM
Fiche technique du projet
Fiche technique du projet
Getting started
Dependencies
Install all the packages
yarn
This will trigger some build on the postinstall script:
husky install
lerna link
Development
run docker-compose services db, hasura, maildev, api
launch hasura console
run react-scripts start
yarn dev
Logs containers
yarn dev:server:log
Stop
to stop current react dev console:
press CTRL+C in current terminal
to stop current containers:
docker-compose down
Cleaning
to remove installed packages
rm -rf node_modules
rm -rf packages/app/node_modules
rm -rf packages/api/node_modules
to remove db
docker volume rm emjpm_emjpm-pgdata
Test production build
this work without any previous install
yarn dev:prod
Test
Fonctionnement des tests
Release policy
Semantic releases
yarn release
Deployment policy
see documentation details
Branch name
You need to name your branch with the commit lint convention
branch name template:
type/***-***
Type
Must be one of the following:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
as a reference see https://github.com/conventional-changelog/commitlint/tree/master/@commitlint/config-angular