A simple and interactive fitness tracking application built with multiple microservices and programming languages. This application allows users to track their exercises and monitor their progress over time.
The Activity Tracking functionality uses the MERN stack (MongoDB, Express.js, React, Node.js), the Analytics service uses Python/Flask and the Authentication Microservice using Java.
- User registration for personalized tracking
- Log various types of exercises with descriptions, duration, and date
- See weekly and overall statistics
- Interactive UI with Material-UI components
- Real-time data persistence with MongoDB
- Node.js
- MongoDB
- npm or yarn
- Python Flask
- Java 8 (all already installed in the devcontainer)
-
Click on "Code"
-
Switch to the "Codespaces" tab
-
Create new Codespace from main
-
Open Codespace in VS code for best experience:
Walktrough:
sh .devcontainer/check-installation.shexpected output:
Checking installations...
node is /usr/local/bin/node
node is installed with version: v18.16.0
npm is /usr/local/bin/npm
npm is installed with version: 9.5.1
python3 is /usr/bin/python3
python3 is installed with version: Python 3.9.2
pip3 is /usr/bin/pip3
pip3 is installed with version: pip 20.3.4 from /usr/lib/python3/dist-packages/pip (python 3.9)
gradle is /usr/bin/gradle
gradle is installed with version:
------------------------------------------------------------
Gradle 4.4.1
------------------------------------------------------------
......
Done checking installations.
if you're missing any version, please contact your course administrator.
docker compose up --builddocker compose updocker compose up [servicename]docker compose down [servicename]docker system prune --all --force --volumes
cd activity-tracking
npm install
nodemon servercd analytics
flask run -h localhost -p 5050cd authservice
./gradlew clean build
./gradlew bootRuncd frontend
npm install
npm startdocker run --name mongodb -d -p 27017:27017 -v mongodbdata:/data/db mongo:latest
mongosh -u root -p cfgmla23 --authenticationDatabase admin --host localhost --port 27017
show registered activities:
db.exercises.find()
show registered users:
db.users.find()
The application is containerized using Docker and can be deployed on any platform that supports Docker containers. For AWS deployment, a GitHub Actions pipeline is configured for CI/CD.
By default, the services are run behind Tyk (used as an API Gateway & Reverse Proxy). Tyk is configured in the ./tyk folder, where each api has a config file (eg tyk/apps/auth). Here we configure which requests to tyk we match to this api, where we forward them on to and any middleware that is applied.
To access TYK, the frontend/orchestration needs to use an API Key. This is set as TYK_API_KEY in the .env for the frontend, and is set as a header on all requests to tyk. This means that all requests to our services are fully secured through auth, as requests can only get to the service via tyk, and the only way to get the api key is to send a request to the frontend/orchestration with a valid auth token.
If Tyk is giving errors in the logs like connect: connection refused, you may need to generate a new api key and place it in the env file for the frontend.
To do this, copy the cUrl command in the tyk folder and run it in your terminal. Paste the value of the "key" output into your .env.local file as the TYK_API_KEY, and this will give the next.js orch the authentication to hit the services through tyk.
. tyk/curl_command
All services and the frontend send metrics to Prometheus, and are displayed on a Grafana dashboard. The dashboard is stored as a json file in the grafana folder for easy local development.