Feature/dashboard merged to development

.github/workflows/main.yml

@@ -0,0 +1,40 @@
+name: CI Workflow
+
+on:
+  push:
+    branches:
+      - feature/dashboard
+  pull_request:
+    branches:
+      - feature/dashboard
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v2
+
+      - name: Log in to Docker Hub
+        uses: docker/login-action@v2
+        with:
+          username: ${{ secrets.DOCKER_USERNAME }}
+          password: ${{ secrets.DOCKER_PASSWORD }}
+
+      - name: Build Docker containers
+        env:
+          DB_USERNAME: ${{ secrets.DB_USERNAME }}
+          DB_PASSWORD: ${{ secrets.DB_PASSWORD }}
+        run: |
+          docker-compose -f docker-compose.yml build
+
+      - name: Start Docker containers
+        env:
+          DB_USERNAME: ${{ secrets.DB_USERNAME }}
+          DB_PASSWORD: ${{ secrets.DB_PASSWORD }}
+        run: |
+          docker-compose -f docker-compose.yml up -d

README.md

@@ -1,2 +1,24 @@
-# GroupProjectTemplate
-Please make sure to modify this readme file as well as the "about" property of the project!
+# IMDB Movie Data Analysis and Visualization Platform
+**Overview
+**    
+This project focuses on developing a web-based platform for analyzing and visualizing IMDB movie data. The motivation behind this project is the need to process and present large datasets in a user-friendly way, making it easier to identify trends and derive insights. The film industry generates vast amounts of data, such as movie releases, reviews, ratings, and production details. This platform aims to provide an organized solution to visualize and explore this information effectively.    
+
+The platform allows users, including movie enthusiasts, data analysts, film critics, and researchers, to explore IMDB movie data through interactive visualizations. Core functionalities include visualizing movie release trends by year, genre, and production country, performing sentiment analysis on user reviews, and generating word clouds based on commonly found terms in reviews.    
+
+The project is built with a technology stack featuring Python and Django for backend development, managing server-side logic and database interactions. The frontend will be developed with HTML, CSS, and JavaScript, while ECharts will be used to create dynamic visualizations. The MySQL database will store the IMDB movie data. Git will be used for version control, and GitHub will manage collaboration. Additional tools, such as Pandas for data processing and pie charts for specific visualizations, will support the platform's functionality.    
+
+**Features
+**    
+Visualize Movie Trends: Explore movie release trends by year, genre, and country of production.    
+Sentiment Analysis: Analyze user reviews to extract sentiments and display them through visualizations.    
+Word Cloud Generation: View common terms from user reviews to understand the most talked-about topics.    
+Interactive Data Visualizations: Use ECharts to present data in an engaging and interactive format, such as pie charts and bar graphs.    
+
+**Technology Stack
+**    
+Backend: Python with Django Framework    
+Frontend: HTML, CSS, JavaScript    
+Data Visualizations: ECharts    
+Database: MySQL    
+Data Processing: Pandas    
+Version Control: Git, hosted on GitHub

code/.gitattributes

@@ -0,0 +1,15 @@
+# Handle line endings automatically for text files
+* text=auto
+
+# Explicitly declare files that should always have LF line endings
+*.sh text eol=lf
+*.yml text eol=lf
+*.py text eol=lf
+
+# Explicitly declare files that should always have CRLF line endings (Windows files)
+*.bat text eol=crlf
+
+# Ignore binary files
+*.png binary
+*.jpg binary
+*.gif binary

code/.gitignore

@@ -0,0 +1,162 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

code/Dockerfile

@@ -0,0 +1,42 @@
+# Use an official Python runtime as a parent image
+FROM python:3.8-slim
+
+# Set environment variables
+ENV PYTHONDONTWRITEBYTECODE=1
+ENV PYTHONUNBUFFERED=1
+
+# Set the working directory in the container
+WORKDIR /app
+
+# Install system dependencies for MySQL client and other tools
+RUN apt-get update && apt-get install -y \
+    gcc \
+    libmariadb-dev-compat \
+    libmariadb-dev \
+    netcat-openbsd \
+    && rm -rf /var/lib/apt/lists/*
+
+# Copy the requirements.txt file into the container
+COPY requirements.txt /app/
+
+# Install Python dependencies
+RUN pip install --no-cache-dir -r requirements.txt
+
+
+COPY wait-for-it.sh /app/wait-for-it.sh
+
+# Make it executable
+RUN chmod +x /app/wait-for-it.sh
+
+# Copy the rest of your project code into the container
+COPY . /app/
+
+# Expose the port that the app will run on
+EXPOSE 8000
+
+WORKDIR /app/my_project
+# Wait for MySQL to be available, then start the Django development server
+CMD ["sh", "-c", "until nc -z $DB_HOST $DB_PORT; do echo 'Waiting for MySQL...'; sleep 3; done; python /app/my_project/manage.py runserver 0.0.0.0:8000"]
+
+ # Add the my_project directory to PYTHONPATH
+ENV PYTHONPATH="/app/my_project:${PYTHONPATH}"