HotZone

Deployed at:

https://hotzone-group-q-final.herokuapp.com/

Iteration 3:

This iteration focuses on calculating case clusters and presenting them nicely. The functionality to connect locations (visits) with cases is also introduced.

Limitations and Exclusions:

• Location can only be created based on GeoData Store i.e user cannot choose to input own values for the Location.
• Data cannot be loaded from spreadsheets or CSV files, which are legacy methods of storing data.
• Cases are identified by global IDs, instead of being grouped by disease outbreaks first.
• Takes long to load.

Setting up the development environment:

Setting up the backend:

⚠️ Make sure you have a .env file in your local HotZone directory (project root). This should contain the following environment variables: DEPLOYMENT_URL, DATABASE_URL, DEBUG & SECRET_KEY.

1. Change directory to HotZone/server.
2. Install all dependencies from requirements.txt using pip install -r /path/to/requirements.txt
3. Make sure you switch to your virtual environments. If you want to go with the one in the repository, you can simply enter the command source server-env/bin/activate
4. From the server directory, gunicorn server.wsgi:application OR heroku local.

Setting up the frontend:

1. Change directory to HotZone/web.
2. Install all dependencies using yarn install.
3. Run the frontend using yarn start.

Alternatively, if you have created the latest build (i.e. you ran yarn build , you can access the frontend from the backend url as well.)

To deploy:

We use the deployment branch for deployment. To deploy, follow these steps:

1. Navigate to the web directory and then run yarn build. This will place build folder in the server folder.
2. With this, you are ready to deploy. Now, you can run from the directory HotZone (project root): git push origin `git subtree split --prefix server`:deployment --force. This places the files required for the deplyment in the corresponding deployment branch. Sometimes, if this command is not run properly, you may end up deleting the remote deployment branch. If that happens, follow the next section.

If you end up deleting the deployment branch:

1. You should firstly restore the deployment remote branch. You can do this by pushing the subtree to the deployment branch. For this, from the directory HotZone (project root) do: git subtree push --prefix server origin deployment
2. Navigate over to the Heroku dashboard and restore the CI/CD. Scroll down to Automatic Deploys and from the dropdown, select the deployment branch.
3. You still have to manually deploy this once. So Scroll further down to the Manual deploy section and click on deploy.