- Use the present tense ("Add feature" not "Added feature")
 - Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
 - Limit the first line to 72 characters or less
 - Reference issues and pull requests liberally after the first line
 - When only changing documentation, include 
[ci skip]in the commit title - Consider starting the commit message with an applicable emoji
 
In this interview, we will discuss the implementation of a self-management exercise tracker that helps individuals with chronic conditions and disabilities engaged with daily exercise, monitored by health coaches.
The system consists of three main components:
- a Mobile Health app that allows individuals (primary users) to record the type of exercise, the duration, and location over a day.
 - a RESTful backend that is connected to a database. This backend sends, receives and stores the data for all individuals (users).
 - a Web Portal for health coaches. This portal displays reports and analysis of the exercise records collected from the app for a group of individuals with chronic conditions and disabilities.
 
In this learning session, you are going to implement a clinical app which helps clinicians monitor participants with the Raynaud Symptom (a disease with a condition in which some areas of the body feel numb and cool in certain circumstances).
The Mobile App is used to record when, where and how severe a Raynaud attack happens on their body. Since we can have many different patients, we need an identification to distinguish them. So the first feature is create an identification for each patient. The second feature is: for the Raynauds record, we want to record when, where and how serve when it happens. Also, we want to allow user to modify the record they already input just in case that they input it wrongly for the first time. The third feature is we hope the app could provide a last-seven-day report of Raynauds records on the patient. More details is shown below.
- An identification for the participant (app user)
 - Ask the participant to input the usern
 
| # Backup | |
| docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql | |
| # Restore | |
| cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE | |
| This is intended as a quick reference and showcase. For more complete info, see [John Gruber's original spec](http://daringfireball.net/projects/markdown/) and the [Github-flavored Markdown info page](http://github.github.com/github-flavored-markdown/). | |
| This cheatsheet is specifically *Markdown Here's* version of Github-flavored Markdown. This differs slightly in styling and syntax from what Github uses, so what you see below might vary a little from what you get in a *Markdown Here* email, but it should be pretty close. | |
| You can play around with Markdown on our [live demo page](http://www.markdown-here.com/livedemo.html). | |
| ##### Table of Contents | |
| [Headers](#headers) | |
| [Emphasis](#emphasis) | |
| [Lists](#lists) | 
In this interview, we will discuss the implementation of a clinic system that helps clinicians monitor a group of participants with Raynauds. Raynauds is a condition where certain areas of the body feel numb and cool in specific circumstances.
The system consists of three main components:
- a Mobile Health app that allows participants to record when and where their Raynauds attacks occur.
 - a RESTful backend that is connected to a database. This backend sends, receives and stores the data for all participants.
 - a Web Portal for clinicians. This portal displays reports and analysis of the Raynauds records collected from the app.
 
