Developed by [Thales Group CERT](https://github.com/thalesgroup-cert).

---
# Install Watcher

## Prerequisites
- [Install docker](https://docs.docker.com/install/)

## Launch watcher
- Grab the `docker-compose.yml`, `.env` files and `Searx` directory (keep the directory structure).
- According to your existing infrastructure you may need to configure **Watcher settings** using the `.env` file ([Static configuration](#static-configuration)). 
- `docker compose up`

This should run Docker containers.

Please wait until you see:

    watcher          | db_watcher is up, starting Watcher.
    watcher          | Performing system checks...
    watcher          | 
    watcher          | System check identified no issues (0 silenced).
    watcher          | January 08, 2025 - 11:43:02
    watcher          | Django version 5.0.10, using settings 'watcher.settings'
    watcher          | Starting development server at http://0.0.0.0:9002/
    watcher          | Quit the server with CONTROL-C.

- Try to access Watcher on http://0.0.0.0:9002 or http://yourserverip:9002.
- `CONTROL-C`
- `docker compose down` to stop all containers.

### Migrate
Updates the state of the database in accordance with all current models and migrations. Migrations, their relationships 
with applications...

    docker compose down
    docker compose run watcher bash
    python manage.py migrate
    
### Create admin user
You will need to create the first superuser to access the `/admin` page.

    docker compose down
    docker compose run watcher bash
    python manage.py createsuperuser

### Populate your database
Populate your database with hundred of banned words and RSS sources related to Cyber Security.

Use `populate_db` script:

    docker compose down
    docker compose run watcher bash
    python manage.py populate_db

### Good to know
The first time you run Watcher, you will not have any new threats on the homepage, this is normal.

You just have to wait for Watcher to crawl the Internet. This will happen every 30 minutes.

## Static configuration
Most of the settings can be modified from the `/admin` page.

There are other settings located in the `.env` file that you can configure. 

### Production Settings [Important]

In production please put DJANGO_DEBUG environment variable to **False** in the `.env` file:

    DJANGO_DEBUG=False
    
Also, the **Django secret key** must be a **large random value** and it must be kept secret.
There is one by default but consider to change it in the `.env` file:

    DJANGO_SECRET_KEY=[large random value]
    
Time Zone settings in the `.env` file:

    # Time Zone
    TZ=Europe/Paris

If you have modified some of these parameters, don't forget to restart all containers:

    docker compose down
    docker compose up

### Access Watcher remotely within your server instance
In case of **"Bad Request" Error** when accessing Watcher web interface, fill `ALLOWED_HOST` variable (in `.env` file) with your Watcher Server Instance **IP** / or your **FQDN**.

It is limited to a **single IP address** / **single FQDN**. 

Please use this syntax: 

    ALLOWED_HOST=X.X.X.X or ALLOWED_HOST=mywebsite.com
    
Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up
 
### MISP Settings
If you want to use **MISP export**, please fill the **IP** of your MISP instance and an **API key**.

In the `.env` file:

    # MISP Setup
    MISP_URL=
    MISP_VERIFY_SSL=False
    MISP_KEY=
 
Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up
 
### LDAP Settings
You can configure an LDAP authentication within Watcher:

In the `.env` file:

    # LDAP Setup
    AUTH_LDAP_SERVER_URI=
    AUTH_LDAP_BIND_DN=
    AUTH_LDAP_BIND_PASSWORD=
    AUTH_LDAP_BASE_DN=
    AUTH_LDAP_FILTER=(uid=%(user)s)
 
Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up

## Troubleshooting
### Remove the database

You may want to **reset** your database entirely, in case of troubleshooting or other. To do this, you need to remove the database stored in your host system and restart the instance:

    docker compose down
    docker volume rm watcher-project_db_data
    docker volume rm watcher-project_db_log

Now, you can rebuild the image and the parameters will be taken into account:

    docker compose up

Don't forget to [migrate](#migrate).

### Useful commands

Use `docker compose up -d` if you want to run it in background.

Run interactive shell session on the Watcher container:

    docker compose run watcher bash

# Use Watcher
## User enrollment 
To create a simple user, staff user or admin user:

Connect to the `/admin` page:

   - Click on **Users**.
   - Click on **ADD USER**.
   - Enter the **Username** and **Password** and Click on **SAVE**.
   - Choose the permissions:
        * **Active** → Is the default one, site access for users
        * **Staff status** → Designates whether the user can log into this admin site.
        * **Superuser status** → Designates that this user has all permissions without explicitly assigning them.
   - You may enter an **Email address** for email notifications.
   - Click on **SAVE**.
 
## Subscribe to notifications

Receive notifications via different channels when subscribing to a topic.

To add a subscriber, follow these steps:

1. Go to the `/admin` page.
2. Click on **Subscribers**.
3. Click on **ADD SUBSCRIBER**.
4. Select the **USER**.
5. Choose your preferred notification channel from the following options:
   - **EMAIL**
   - **THEHIVE**
   - **SLACK**
   - **CITADEL**

Make sure to configure the necessary settings for each channel in your `.env` file.

### Configure your Email notifications

To configure Email, you need the following variables, in the `.env` file:

    # DJANGO EMAIL Configuration
    SMTP_SERVER=
    EMAIL_PORT=25
    EMAIL_USE_TLS=False
    EMAIL_USE_SSL=False
    EMAIL_HOST_USER=
    EMAIL_HOST_PASSWORD=
    EMAIL_FROM=

Follow these steps to get the required information:

1. Choose your email provider (example: Gmail, Outlook...).
2. Go to the email provider’s settings and generate the **SMTP configuration**:
   - For **Gmail**, detailed instructions can be found in [Google's SMTP documentation](https://support.google.com/a/answer/176600?hl=en).
   - For **Outlook**, you can refer to the [Outlook SMTP documentation](https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for more information.
3. Follow the instructions to retrieve the SMTP server, email port, and other necessary credentials.
4. Save these values in your `.env` file.
   - `SMTP_SERVER`
   - `EMAIL_PORT`
   - `EMAIL_USE_TLS`
   - `EMAIL_USE_SSL` 
   - `EMAIL_HOST_USER` 
   - `EMAIL_HOST_PASSWORD` 
   - `EMAIL_FROM` 

Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up

### Configure your TheHive notifications

To configure TheHive, you need the following variables, in the `.env` file:

    # THE HIVE Setup
    THE_HIVE_URL=
    THE_HIVE_VERIFY_SSL=False
    THE_HIVE_KEY=
    # Ensure the custom field referenced here is CREATED IN THEHIVE. Otherwise, Alert exports to TheHive will be impacted
    THE_HIVE_CUSTOM_FIELD=watcher-id
    THE_HIVE_EMAIL_SENDER=watcher@watcher.com

Follow these steps to get the required information:

1. Go to your TheHive instance’s API section (typically located at `/account/api`).
2. Copy the API Key from this page and save it as `THEHIVE_API_TOKEN` in your `.env` file.


3. Also, you need to set the URL of your TheHive instance as `THEHIVE_URL` in your `.env` file.
4. For proper integration, Watcher uses a custom field in TheHive for its ticketing system. By default, this field is named **watcher-id** and should be set as `THE_HIVE_CUSTOM_FIELD` in your .env file.

    # Note: Ensure the custom field referenced here is CREATED IN THEHIVE. Otherwise, Alert exports to TheHive will be impacted

   You can modify the name of this custom field in your .env file to match your specific TheHive instance setup.

5. The **second custom** field is used to track the email sender and is defined as `THE_HIVE_EMAIL_SENDER`. By default, this is set to watcher@watcher.com. You can update this value in your .env file as needed.

Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up

### Configure your Slack notifications

To configure Slack, you need the following variables, in the `.env` file:

    # SLACK Setup
    SLACK_API_TOKEN=
    SLACK_CHANNEL=

Follow these steps to get the required information:

1. Go to the [Slack API page](https://api.slack.com/apps).
2. Click on **Create New App**.
3. Choose **From scratch**.
4. Once your app is created, go to **OAuth & Permissions**.
5. Under **OAuth Scopes**, ensure you add the required permission:
   - `chat:write` (This allows your app to send messages to channels).
6. On **OAuth Tokens**, click on **Install App** to install the app to your workspace.
7. After installation, you will be provided with an **OAuth Access Token**. Copy this token and save it as `SLACK_API_TOKEN` in your `.env` file.
8. Lastly, create the channel in Slack if you haven’t already and save its name as `SLACK_CHANNEL` in the `.env` file.

Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up

### Configure your Citadel notifications

To configure Citadel, you need the following variables, in the `.env` file:

    # CITADEL Setup
    CITADEL_API_TOKEN=
    CITADEL_CHANNEL=
    CITADEL_URL=

Follow these steps to get the required information:

1. If you don't have an account, go to this link to create one: Citadel Team Documentation.
2. Create a **New Room**.
3. Retrieve the `CITADEL_ROOM_ID` from the room's settings. Copy the room's link, then extract the ID after `/#/room/` and add it to your .env file.
4. Next, visit this link: [Citadel Team Website](https://cds.thalesgroup.com/en/ercom/citadel) to request your `CITADEL_API_TOKEN`. This token will allow you to send automatic notifications.
5. For the `CITADEL_URL` variable, if you're using a public instance, the URL should be: [https://join.citadel.team/](https://join.citadel.team/). Otherwise, enter your customized instance URL.

Now, you can restart your instance and the parameters will be taken into account:

    docker compose down
    docker compose up

## Add your RSS source to Threats Detection
As you know this feature allow the detection of emerging vulnerabilities, malwares using social networks & other RSS sources (www.cert.ssi.gouv.fr, www.cert.europa.eu, www.us-cert.gov, www.cyber.gov.au...).

Watcher currently provides hundreds of RSS cybersecurity sources ([Populate default RSS sources](#populate-your-database)).

However, you can add your RSS Cybersecurity source to your Watcher instance:

- First, make sure you have a URL leading to an RSS file (Atom 1.0, Atom 0.3, RSS 2.0, RSS 2.0 with Namespaces, RSS 1.0). 
- Your RSS file must be composed of several articles.
- Please consider the use of https over http. 

Connect to the `/admin` page:

- Click on **Sources** in **THREATS_WATCHER** part.
- Click on **ADD SOURCE**.
- Fill **Url** text input.
- Click on **SAVE**.


## API Key Creation & Management

Connect to the `/admin` page:

- Click on **API Keys** in **Accounts** part.
- Click on **ADD API KEY**.
- Select the **expiration** date.
- Click on **SAVE**.


You must pass your API keys via the Authorization header. It should be formatted as follows: **`Authorization: Token <API_KEY>`** where **<API_KEY>** refers to the full generated API key.


Below, you will find our 4 modules with their API functions:

<details>

<summary>Threats Watcher</summary>  <br>

`^api/threats_watcher/trendyword/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of trending words monitored by the application.
  - **POST:** Adds a new trending word to the monitored list.
  - **PATCH:** Updates an existing trending word in the monitored list.
  - **DELETE:** Removes a trending word from the monitored list.
- **Usage:** Used to get, add, update, or delete currently monitored trending keywords.

`^api/threats_watcher/bannedword/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of banned words monitored by the application.
  - **POST:** Adds a new banned word to the monitored list.
  - **PATCH:** Updates an existing banned word in the monitored list.
  - **DELETE:** Removes a banned word from the monitored list.
- **Usage:** Used to get, add, update, or delete currently monitored banned keywords.

</details> <br>

<details>

<summary>Data Leak</summary> <br>

`^api/data_leak/keyword/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of keywords monitored for data leaks.
  - **POST:** Adds a new keyword to the monitored list for data leaks.
  - **PATCH:** Updates an existing keyword in the monitored list for data leaks.
  - **DELETE:** Removes a keyword from the monitored list for data leaks.
- **Usage:** Used to get, add, update, or delete keywords monitored for data leaks.

`^api/data_leak/alert/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of alerts related to data leaks.
  - **POST:** Adds a new alert for data leaks.
  - **PATCH:** Updates an existing alert for data leaks.
  - **DELETE:** Removes an alert related to data leaks.
- **Usage:** Used to get, add, update, or delete current alerts regarding data leaks.

</details> <br>

<details>

<summary>Website Monitoring</summary> <br>

`^api/site_monitoring/site/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of sites monitored by the application.
  - **POST:** Adds a new site to the monitored list.
  - **PATCH:** Updates an existing site in the monitored list.
  - **DELETE:** Removes a site from the monitored list.
- **Usage:** Used to get, add, update, or delete currently monitored sites.

`^api/site_monitoring/alert/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of alerts related to site monitoring.
  - **POST:** Adds a new alert related to site monitoring.
  - **PATCH:** Updates an existing alert related to site monitoring.
  - **DELETE:** Removes an alert related to site monitoring.
- **Usage:** Used to get, add, update, or delete current alerts regarding site monitoring.

`^api/site_monitoring/misp/$`
- **HTTP Method:** POST
- **Description:** 
  - **POST:** Adds a new integration with MISP.
- **Usage:** Used to get, add, update, or delete current integrations with MISP.

</details> <br>

<details>

<summary>DNS Finder</summary> <br>

`^api/dns_finder/dns_monitored/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of monitored DNS domains.
  - **POST:** Adds a new DNS domain to the monitored list.
  - **PATCH:** Updates an existing monitored DNS domain.
  - **DELETE:** Removes a DNS domain from the monitored list.
- **Usage:** Used to get, add, update, or delete currently monitored DNS domains.

`^api/dns_finder/keyword_monitored/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of monitored DNS keywords.
  - **POST:** Adds a new keyword to the monitored list.
  - **PATCH:** Updates an existing monitored keyword.
  - **DELETE:** Removes a keyword from the monitored list.
- **Usage:** Used to get, add, update, or delete currently monitored DNS keywords.

`^api/dns_finder/dns_twisted/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of twisted DNS domains (typosquatting).
  - **POST:** Adds a new twisted DNS domain to the monitored list.
  - **PATCH:** Updates an existing twisted DNS domain in the monitored list.
  - **DELETE:** Removes a twisted DNS domain from the monitored list.
- **Usage:** Used to get, add, update, or delete currently monitored twisted DNS domains.

`^api/dns_finder/alert/$`
- **HTTP Method:** GET, POST, PATCH, DELETE
- **Description:** 
  - **GET:** Returns a list of DNS alerts.
  - **POST:** Adds a new DNS alert.
  - **PATCH:** Updates an existing DNS alert.
  - **DELETE:** Removes a DNS alert.
- **Usage:** Used to get, add, update, or delete current DNS alerts.

`^api/dns_finder/misp/$`
- **HTTP Method:** POST, PATCH, DELETE
- **Description:** 
  - **POST:** Adds a new integration with MISP for DNS.
  - **PATCH:** Updates an existing integration with MISP for DNS.
  - **DELETE:** Removes an integration with MISP for DNS.
- **Usage:** Used to get, add, update, or delete current integrations with MISP for DNS.

</details> <br>


### Specific Details

To obtain detailed information about a specific item, such as an alert, a monitored site, or any other entity in the system, you can access its details by appending `/(?P<pk>[^/.]+)/$` to the end of the corresponding API URL.

For instance, let's say you want to retrieve information about an alert with the ID "1". You would construct the URL as follows: `http://0.0.0.0:9002/api/site_monitoring/alert/1`

By making a GET request to this URL using your web browser, CURL, or any HTTP client, you will receive comprehensive details about the alert with the ID "1".

Following this pattern, you can easily navigate and retrieve specific information for any item in the system, ensuring efficient use of the available API endpoints.


## MISP Export
You can export **monitored DNS** to [MISP](https://www.misp-project.org/):

  - Go to **/website_monitoring** page.
  - Add new DNS to monitored.
  - Click on the **blue upload/cloud button**.

### Troubleshooting
If the export do not work as expected, this may be related with 
the version of your MISP instance.

In fact, if you are using an outdated MISP instance, the client API version will not correspond with your MISP instance version:

- Update MISP.

## Remove & Add to Blocklist
There is a **blocklist** to prevent a **false positive trendy words** from reappearing again.

To add **1** word:

- Go to the landing page.
- Authenticate and Click on the "**Delete & Blocklist**" **button**.

To add **several** words:

- Go to **/admin** page.
- Click on **Trendy words**.
- **Check** words that you want to remove & blocklist.
- Click on **Action** dropdown.
- Select "**Delete & Blocklist selected trendy words**".

## Archived Alerts
Once you have processed an alert, you can archive it.

To archived **1** alert:

- Go to the alert that you want to archived.
- Select the "**disable**" **button**.

To archived **several** alerts:

- Go to **/admin** page.
- Click on **Alerts**.
- **Check** alerts that you want to archived.
- Click on **Action** dropdown.
- Select "**Disable selected alerts**".

# Update Watcher

Verify that your local files `/.env`, `/docker-compose.yml` and `/Searx/` are **up-to-date**.

To update Watcher image please follow the instructions below:

- Stop all containers: `docker compose down`
- Remove the old docker images: `docker rmi felix83000/watcher searx/searx`
- Pull the newer docker images: `docker compose up`

This will update the Watcher project.

## Migrate & Populate the database (mandatory)

Updates the state of the database in accordance with all current models and migrations. Populate your database with hundred of banned words and RSS sources related to Cyber Security.

    docker compose down
    docker compose run watcher bash
    python manage.py migrate
    python manage.py populate_db

## Managing Breaking Changes (optional)

If the release includes breaking changes, additional steps may be required. Here are the general steps to manage breaking changes:

1. **Review release notes or documentation**: Check the release notes or documentation for any information about breaking changes and specific instructions on how to handle them.

2. **Backup data**: Before proceeding with the update, it's advisable to backup any critical data to prevent loss in case of unexpected issues.

3. **Test in a staging environment**: If possible, test the update in a staging environment to identify any potential issues or conflicts with existing configurations or customizations.

4. **Update configurations**: Review and update any configurations or settings that may be affected by the breaking changes.

5. **Modify custom code**: If you have any custom code or scripts that rely on the previous version's functionality, you may need to modify them to work with the new version.

6. **Run additional migration scripts**: If provided, run any additional migration scripts or commands provided by the developers to handle specific breaking changes.

Always refer to the specific instructions provided with the update.

# Developers
If you want to modify the project and Pull Request (PR) your work, you will need to setup your development environment.

## Open a Pull Request (PR) to contribute to this project
- Fork the official Watcher repository
- Install `Git`
- Open a terminal: `git clone <your_forked_repository.git>`
- Switch to the dev branch: `git checkout -b feature/<name_of_the_new_feature>`
- Make your changes on the working files and then: `git add *`
- Add a commit message and description: `git commit -m "Title" -m "Description"`
- Publish the changes: `git push origin feature/<name_of_the_new_feature>`
- Back to GitHub on your forked repository, click Under Contribute > Open Pull Request and then Confirm the operation
- Done! Your work will be reviewed by the team! 

## Setup Watcher environment
Use a Linux server, we recommend the use of a Virtual Machine (Ubuntu 20.04 and Ubuntu 21.10 LTS in our case).

Then, follow the steps below:

- **Update and upgrade your machine:** `sudo apt update && sudo apt upgrade -y`
- **Install Python and Node.js:** `sudo apt install python3 python3-pip -y` **&** `sudo apt install nodejs -y`
- **Pull Watcher code:** `git clone <your_forked_repository.git>`
- **Move to the following directory:** `cd Watcher/Watcher`
- **Install** `python-ldap` **dependencies:** `sudo apt install -y libsasl2-dev python-dev-is-python3 libldap2-dev libssl-dev`
- **Install** `mysqlclient` **dependency:** `sudo apt install default-libmysqlclient-dev`
- **Install Python dependencies:** `pip3 install -r requirements.txt`
- **Install NLTK/punkt dependency:** `python3 ./nltk_dependencies.py`
     - If you have a proxy, you can configure it in `nltk_dependencies.py` script.  
- **Install Node.js dependencies:**
     - `sudo apt install npm -y`
     - `npm install`
- **Install MySQL:**
     - `sudo apt install mysql-server -y`
     - `sudo mysql_secure_installation`
          - Enter root password.
          - You may now enter `Y` and `ENTER`. Accept all fields. This will remove some anonymous users and the test database, 
    disable remote root logins, and load these new rules so that MySQL immediately respects any changes made.

**Create & Configure Watcher database:**

    sudo mysql 
    CREATE USER 'watcher'@'localhost' IDENTIFIED BY 'Ee5kZm4fWWAmE9hs!';
    GRANT ALL PRIVILEGES ON *.* TO 'watcher'@'localhost' WITH GRANT OPTION;
    CREATE DATABASE db_watcher;
    use db_watcher;
    exit
    systemctl status mysql.service

- `cd Watcher/watcher`

In `settings.py` change `HOST` variable to `localhost`:

    DATABASES = {
       'default': {
           'ENGINE': 'django.db.backends.mysql',
           'CONN_MAX_AGE': 3600,
           'NAME': 'db_watcher',
           'USER': 'watcher',
           'PASSWORD': 'Ee5kZm4fWWAmE9hs!',
           'HOST': 'localhost',
           'PORT': '3306',
           'OPTIONS': {
               'init_command': "SET sql_mode='STRICT_TRANS_TABLES'",
           },
       }
    }

- <span style="color:red">**[IMPORTANT]** When **commit** put `HOST` variable back to `db_watcher`</span>
- `cd ..`
- **[Migrate](#migrate) the database:** `python3 manage.py migrate`
- **Run Watcher:** `python3 manage.py runserver`

## Deploy a simple SMTP server to test the email notifications
If you are working on a test environment and willing to have email alerts, here is a simple way to configure the SMTP settings to make it work.
- Grab the docker-compose file: [here](https://github.com/rnwood/smtp4dev/blob/master/docker-compose.yml).
- Run the command: `docker compose up`
- The mails will be available here by default: `localhost:5000`
- Modify the mail settings in the environment variables: `vi /.env`
    - `SMTP_SERVER=localhost`
    - `EMAIL_FROM=from@from.com`
- Launch Watcher: `python3 Watcher/Watcher/manage.py runserver` 

## Modify the frontend
If you need to modify the frontend `/Watcher/Watcher/frontend`:

From `/Watcher/Watcher/`, run the command below:

    npm run dev

Let this command run in background. 
Now, when modifying some frontend ReactJs files it will automatically build them into one file (`/Watcher/Watcher/frontend/static/frontend/main.js`).

<span style="color:red">**[IMPORTANT]** When **commit** you have to run **1 time** the command below:</span>

    npm run build

## Migrations: Change the database schema
Migrations are Django’s way of propagating changes you make to your models 
(adding a field, deleting a model, etc.) into your database schema. They’re designed to be mostly automatic, 
but you’ll need to know when to make migrations, when to run them, and the common problems you might run into.

### The commands
There are several commands which you will use to interact with migrations and Django’s handling of database schema:
- `migrate`, which is responsible for applying and unapplying migrations.
- `makemigrations`, which is responsible for creating new migrations based on the changes you have made to your models.
- `sqlmigrate`, which displays the SQL statements for a migration.
- `showmigrations`, which lists a project’s migrations and their status.

### Change a model (adding a field, deleting a model, etc.)
When you are **making a change to a model**, for instance, adding a new field to: **/Watcher/Watcher/data_leak/models.py**
Then, you need to create a new migration based on the changes you have made:
- Go to **/Watcher/Watcher/** and run this command: `python3 manage.py makemigrations`

<span style="color:red"> **[IMPORTANT]** Run the `makemigrations` command **only once**</span>, when you have made **all the changes**. 
Otherwise, it will create **several unnecessary migration files**.

## Build the documentation
Modify some function comments or the `/Watcher/README.md` file.

Go to `/Watcher/docs` and run:
   
     ./build_the_docs.sh

When commit please add the all `/Watcher/docs` folder and the `README.md` file:

    git add ../docs ../README.md