endoreg-db 0.5.3__tar.gz → 0.6.0__tar.gz

endoreg_db-0.6.0/PKG-INFO

@@ -0,0 +1,151 @@
+Metadata-Version: 2.2
+Name: endoreg-db
+Version: 0.6.0
+Summary: EndoReg Db Django App
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: agl-report-reader>=0.4.0
+Requires-Dist: django-bootstrap5>=24.3
+Requires-Dist: django-cors-headers>=4.7.0
+Requires-Dist: django-extensions>=3.2.3
+Requires-Dist: django>=5.1.3
+Requires-Dist: djangorestframework>=3.15.2
+Requires-Dist: faker>=32.1.0
+Requires-Dist: icecream>=2.1.4
+Requires-Dist: numpy>=2.1.3
+Requires-Dist: opencv-python>=4.10.0.84
+Requires-Dist: pandas>=2.2.3
+Requires-Dist: pillow>=11.0.0
+Requires-Dist: pydantic>=2.10.6
+Requires-Dist: pytesseract>=0.3.13
+Requires-Dist: python-ffmpeg>=2.0.12
+Requires-Dist: pytorch-lightning>=2.4.0
+Requires-Dist: pyyaml>=6.0.2
+Requires-Dist: scikit-learn>=1.5.2
+Requires-Dist: scipy>=1.14.1
+Requires-Dist: tesseract>=0.1.3
+Requires-Dist: tqdm>=4.67.0
+Requires-Dist: urllib3>=2.2.3
+
+# EndoregDB - Professional Data Infrastructure for Clinical Research
+
+EndoregDB is a comprehensive database framework designed to manage medical and research-related data for clinical trials. This repository focuses on efficient data processing, automated deployment, security, and reproducibility, offering a flexible setup for local development environments as well as distributed systems. It supports the integration of AI/ML tools and advanced image and report processing.
+
+This infrastructure was originally designed for clinical research studies and is optimized for handling large data volumes, including:
+
+- Medical reports,
+- Patient imaging and video data,
+- Clinical product and treatment data,
+  and more.
+
+## 🚀 Key Features
+
+### System Architecture
+
+- **Modular Design**: Built on scalable and reusable components to simplify integration into various environments.
+- **Multi-System Support**: Manages configurations for local workstations and production servers.
+- **Role-Specific Configuration**: Predefined roles for common use cases:
+  - Medical data processing systems
+  - AI/ML model deployment
+  - Research workstation configuration
+
+### Security & Data Management
+
+- **Data Encryption**: All sensitive data is encrypted, and privacy policies are enforced.
+- **Impermanence**: Stateless system configuration with persistence for critical data.
+- **Access Control**: Role-based access and identity management integration.
+
+### Data and Processing Environment
+
+- **Data Processing**: Optimized for processing medical datasets with preprocessing tools.
+- **AI/ML Support**:
+  - Integration of machine learning tools for predictive analysis.
+  - TensorFlow, PyTorch, and other frameworks supported for model training.
+- **Image/Video Processing**: Support for analyzing patient images and clinical videos.
+
+### Development Tools & Infrastructure
+
+- **Data Science Toolchains**: Pre-configured environments for data processing, analysis, and visualization.
+- **Monitoring & Logging**: Setup for continuous monitoring and logging to ensure system stability and performance.
+
+---
+
+## 🛠 Getting Started
+
+### Prerequisites
+
+- A Linux-based system (Ubuntu/Debian recommended) or NixOS
+- Hardware with sufficient storage for data processing (at least 1 TB recommended)
+
+### Quick Start
+
+1. Clone the repository:
+
+   ```bash
+   git clone https://github.com/wg-lux/endoreg-db.git
+   cd endoreg-db
+   ```
+
+2. Set up your Python environment:
+   _TODO_: Explain Devenv / point to other docs
+
+   ```bash
+   direnv allow
+   ```
+
+3. Run tests:
+   Call Devenv Script to run tests
+
+   ```bash
+   runtests
+   ```
+
+---
+
+## 📁 Repository Structure
+
+```
+endoreg-db/
+├── endoreg_db/                # Main Django app for medical data
+│   ├── case_generator/        # Sample case generator
+│   ├── data/                  # Medical knowledge base
+│   ├── management/            # Data wrangling operations
+│   ├── models/                # Data models
+│   ├── migrations/            # Database migrations
+│   └── serializers/           # Serializers for data
+├── .gitignore                 # Git ignore file for unnecessary files
+└── README.md                  # Project description and setup instructions
+```
+
+---
+
+## 🔒 Security Features
+
+- **Data Encryption**: All sensitive patient data is encrypted.
+- **Role-Based Access Control**: Configurable roles for managing access to various parts of the system.
+- **Logging & Auditing**: Comprehensive logging system that tracks user activities and data changes.
+
+---
+
+## 🖥️ Supported Systems
+
+- **Workstations**: Local development or research workstations with low data processing demands.
+- **Servers**: Scalable server infrastructure for processing large data volumes, integrated with cloud services for scalability.
+
+---
+
+## 🛟 Support
+
+For issues and questions:
+
+- Create an issue in the repository
+- Review the Deployment Guide for common issues
+
+---
+
+## 📜 License
+
+MIT - see LICENSE
+
+---

endoreg_db-0.6.0/README.md

@@ -0,0 +1,121 @@
+# EndoregDB - Professional Data Infrastructure for Clinical Research
+
+EndoregDB is a comprehensive database framework designed to manage medical and research-related data for clinical trials. This repository focuses on efficient data processing, automated deployment, security, and reproducibility, offering a flexible setup for local development environments as well as distributed systems. It supports the integration of AI/ML tools and advanced image and report processing.
+
+This infrastructure was originally designed for clinical research studies and is optimized for handling large data volumes, including:
+
+- Medical reports,
+- Patient imaging and video data,
+- Clinical product and treatment data,
+  and more.
+
+## 🚀 Key Features
+
+### System Architecture
+
+- **Modular Design**: Built on scalable and reusable components to simplify integration into various environments.
+- **Multi-System Support**: Manages configurations for local workstations and production servers.
+- **Role-Specific Configuration**: Predefined roles for common use cases:
+  - Medical data processing systems
+  - AI/ML model deployment
+  - Research workstation configuration
+
+### Security & Data Management
+
+- **Data Encryption**: All sensitive data is encrypted, and privacy policies are enforced.
+- **Impermanence**: Stateless system configuration with persistence for critical data.
+- **Access Control**: Role-based access and identity management integration.
+
+### Data and Processing Environment
+
+- **Data Processing**: Optimized for processing medical datasets with preprocessing tools.
+- **AI/ML Support**:
+  - Integration of machine learning tools for predictive analysis.
+  - TensorFlow, PyTorch, and other frameworks supported for model training.
+- **Image/Video Processing**: Support for analyzing patient images and clinical videos.
+
+### Development Tools & Infrastructure
+
+- **Data Science Toolchains**: Pre-configured environments for data processing, analysis, and visualization.
+- **Monitoring & Logging**: Setup for continuous monitoring and logging to ensure system stability and performance.
+
+---
+
+## 🛠 Getting Started
+
+### Prerequisites
+
+- A Linux-based system (Ubuntu/Debian recommended) or NixOS
+- Hardware with sufficient storage for data processing (at least 1 TB recommended)
+
+### Quick Start
+
+1. Clone the repository:
+
+   ```bash
+   git clone https://github.com/wg-lux/endoreg-db.git
+   cd endoreg-db
+   ```
+
+2. Set up your Python environment:
+   _TODO_: Explain Devenv / point to other docs
+
+   ```bash
+   direnv allow
+   ```
+
+3. Run tests:
+   Call Devenv Script to run tests
+
+   ```bash
+   runtests
+   ```
+
+---
+
+## 📁 Repository Structure
+
+```
+endoreg-db/
+├── endoreg_db/                # Main Django app for medical data
+│   ├── case_generator/        # Sample case generator
+│   ├── data/                  # Medical knowledge base
+│   ├── management/            # Data wrangling operations
+│   ├── models/                # Data models
+│   ├── migrations/            # Database migrations
+│   └── serializers/           # Serializers for data
+├── .gitignore                 # Git ignore file for unnecessary files
+└── README.md                  # Project description and setup instructions
+```
+
+---
+
+## 🔒 Security Features
+
+- **Data Encryption**: All sensitive patient data is encrypted.
+- **Role-Based Access Control**: Configurable roles for managing access to various parts of the system.
+- **Logging & Auditing**: Comprehensive logging system that tracks user activities and data changes.
+
+---
+
+## 🖥️ Supported Systems
+
+- **Workstations**: Local development or research workstations with low data processing demands.
+- **Servers**: Scalable server infrastructure for processing large data volumes, integrated with cloud services for scalability.
+
+---
+
+## 🛟 Support
+
+For issues and questions:
+
+- Create an issue in the repository
+- Review the Deployment Guide for common issues
+
+---
+
+## 📜 License
+
+MIT - see LICENSE
+
+---

endoreg_db-0.6.0/endoreg_db/admin.py

@@ -0,0 +1,92 @@
+from django.urls import path
+from django.contrib import admin
+from django.http import JsonResponse
+from endoreg_db.models import (
+    Patient,
+    Examination,
+    PatientExamination,
+    Finding,
+    FindingLocationClassification,
+    FindingMorphologyClassification,
+    FindingIntervention,  #  Import Finding Interventions
+    PatientFindingIntervention,
+    FindingLocationClassificationChoice,
+    FindingMorphologyClassificationChoice,
+)
+from endoreg_db.forms.patient_finding_intervention_form import (
+    PatientFindingInterventionForm,
+)
+from endoreg_db.forms.patient_form import PatientForm
+
+
+@admin.register(Patient)
+class PatientAdmin(admin.ModelAdmin):
+    form = PatientForm
+    list_display = ("id", "first_name", "last_name", "dob", "center")
+    search_fields = ("first_name", "last_name", "email", "phone")
+    list_filter = ("dob", "center")
+    ordering = ("last_name",)
+
+
+@admin.register(Examination)
+class ExaminationAdmin(admin.ModelAdmin):
+    list_display = ("id", "name")
+    search_fields = ("name", "name_de", "name_en")
+    list_filter = ("name",)
+    ordering = ("name",)
+
+
+class PatientFindingInterventionAdmin(admin.ModelAdmin):
+    change_list_template = "admin/patient_finding_intervention.html"
+
+    def changelist_view(self, request, extra_context=None):
+        """Pass Patients, Examinations, Findings, Locations, Location Choices, Morphologies, Morphology Choices, and Finding Interventions to the template"""
+        extra_context = {
+            "patients": Patient.objects.all(),
+            "examinations": Examination.objects.all(),
+            "findings": Finding.objects.all(),
+            "locations": FindingLocationClassification.objects.all(),
+            "location_choices": FindingLocationClassificationChoice.objects.none(),
+            "morphologies": FindingMorphologyClassification.objects.all(),
+            "morphology_choices": FindingMorphologyClassificationChoice.objects.all(),
+            "finding_interventions": FindingIntervention.objects.all(),  #  Pass Finding Interventions
+        }
+        return super().changelist_view(request, extra_context=extra_context)
+
+    def get_location_choices_json(self, request):
+        """Ensure Django Admin returns JSON response for Location Choices"""
+        location_id = request.GET.get("location")
+        if not location_id:
+            return JsonResponse({"error": "Location ID is required"}, status=400)
+
+        try:
+            choices = list(
+                FindingLocationClassificationChoice.objects.filter(
+                    location_classifications__id=location_id
+                ).values("id", "name")
+            )  #  Convert QuerySet to List
+
+            if not choices:
+                return JsonResponse(
+                    [], safe=False
+                )  #  Return an empty list if no data found
+
+            return JsonResponse(choices, safe=False)  #  Return valid JSON
+
+        except Exception as e:
+            return JsonResponse({"error": str(e)}, status=500)
+
+    def get_urls(self):
+        """Register JSON endpoint inside Django Admin"""
+        urls = super().get_urls()
+        custom_urls = [
+            path(
+                "ajax/get-location-choices/",
+                self.admin_site.admin_view(self.get_location_choices_json),
+                name="ajax_get_location_choices",
+            ),
+        ]
+        return custom_urls + urls
+
+
+admin.site.register(PatientFindingIntervention, PatientFindingInterventionAdmin)

endoreg_db-0.6.0/endoreg_db/urls.py

@@ -0,0 +1,173 @@
+from django.urls import path, include
+from rest_framework.routers import DefaultRouter
+from .views.patient_views import (
+    PatientViewSet,
+    start_examination,
+    get_location_choices,
+    get_morphology_choices, 
+)
+from .views.csrf import csrf_token_view
+#from .views.feature_selection_view import FetchSingleFramePredictionView // its implemented in ando-ai other project need to add here
+from .views.video_segmentation_views import VideoView, VideoLabelView,UpdateLabelSegmentsView
+from .views.views_for_timeline import video_timeline_view
+from .views.raw_video_meta_validation_views import VideoFileForMetaView
+router = DefaultRouter()
+router.register(r'patients', PatientViewSet)
+
+urlpatterns = [
+    path('start-examination/', start_examination, name="start_examination"),
+    path('get-location-choices/<int:location_id>/', get_location_choices, name="get_location_choices"),
+    path('get-morphology-choices/<int:morphology_id>/', get_morphology_choices, name="get_morphology_choices"),
+    path('api/', include(router.urls)),
+    path('api/conf/', csrf_token_view, name='csrf_token'),
+    
+
+
+#--------------------------------------VIDEO SEGMENTATION END POINTS--------------------------------------
+
+       # The dropdown contains video names and their corresponding IDs, which are retrieved from the database(RawVideoFile). Additionally, this route(api/videos) also fetches labels along with their names and IDs from the label table.
+       # We will modify this implementation later as per our requirements.
+        #Based on the selected video ID, relevant data will be fetched from the database, and the video, along with its associated details, 
+        # will be displayed on the frontend using route(api/video/<int:video_id>/).
+        # once label is selected from the dropdown,using its name, details can be fetched from rawvideofile using route("api/video/<int:video_id>/label/<str:label_name>/) 
+        #If editing is required, a form will be available for each label. This form dynamically updates when the selected label changes. It will display all segments associated with the selected label, each with a delete option. Below these segments, there may be a button for adding more segments.
+        #If any values in the form are modified, the updated data will be saved in the database table.
+    
+    
+    
+    
+    # Fetch all videos for the dropdown
+    # Fetch all available videos (for the video selection dropdown in frontend)
+    # Usage in frontend: Call this API to get a list of available videos.
+    # Example request: GET /api/videos/
+    # Response: Returns a JSON list of videos (id, file path, video_url, sequences, label_names).
+    # it also fetch the label from teh label table
+    path("api/videos/", VideoView.as_view(), name="video_list"),
+    
+    #need to change this route
+    #path('api/prediction/', FetchSingleFramePredictionView.as_view(), name='fetch-single-frame-prediction'),#.as_view() converts the class-based view into a function that Django can use for routing.
+    
+    # Fetch video details + labels based on selected video
+    # Usage in frontend: Call this when a user selects a video from the dropdown.
+    # Example request: GET /api/video/1/
+    # Response: Returns metadata, file path, video URL, sequences, and available label names.
+    # Frontend should use this api for `label_names`, to display label selection (dropdown or tabs).
+    path("api/video/<int:video_id>/", VideoView.as_view(), name="video_handler"),
+    
+
+    # Fetch time segments along with frame predictions and filenames for a selected label
+    # 
+    # **Usage in frontend:**
+    # - Call this API when a user selects a label from the dropdown in the timeline.
+    # - The API returns time segments (start & end times in seconds) where the label appears in the video.
+    # - Each segment includes frame-wise predictions and the corresponding frame filenames.
+    #
+    # **Example request:**
+    #   GET /api/video/1/label/outside/
+    #
+    # **Example response:**
+    # {
+    #     "label": "outside",
+    #     "time_segments": [
+    #         {   "segment_start": 0,
+     #       "segment_end": 463,
+    #             "start_time": 0.0,
+    #             "end_time": 9.26,
+    #             "frames": {
+    #                 "0": {
+    #                     "frame_filename": "frame_0000000.jpg",
+    #                     "frame_file_path": "/home/admin/test-data/video_frames/abc123/frame_0000000.jpg",
+    #                     "predictions": {
+    #                         "appendix": 0.0150,
+    #                         and others
+    #                     }
+    #                 },
+    #                 "1": {
+    #                     "frame_filename": "frame_0000001.jpg",
+    #                     "frame_file_path": "/home/admin/test-data/video_frames/abc123/frame_0000001.jpg",
+    #                     "predictions": {
+    #                         "appendix": 0.0124,
+    #                         and otehrs
+    #                     }}}}]}
+    #                 
+    # start_time and end_time are in seconds, converted from frame indices.
+    # frames contains all frames in the segment with:
+    # frame_filename (e.g., frame_0000001.jpg)
+    # frame_file_path (full path for easy access)
+    #  predictions (frame-wise probability scores for each category)
+    #we need label name for this not id as we donot have id in rawvideofile table
+    path("api/video/<int:video_id>/label/<str:label_name>/", VideoLabelView.as_view(), name="video_label_times"),
+
+    # Update or create label segments for a specific video and label
+    # - Call this API when a user updates the start and end frames of a label segment(adding new , deleting or changing the values).
+    # - The API will:
+    #   - **Update** existing segments if they match the given `video_id` and `label_id`.
+    #   - **Create** new segments if they do not already exist.
+    #   - **Delete** segments from the database if they were removed from the frontend.
+    # - This ensures that the database reflects exactly what is sent from the frontend.
+    #
+    # **Example request (Updating segments for label ID 12 in video ID 1):**
+    #   PUT /api/video/1/label/12/update_segments/
+    #
+    # **Request body (JSON):**
+    # {
+    #     "video_id": 1,
+    #     "label_id": 12,
+    #     "segments": [
+    #         {
+    #             "start_frame_number": 0,
+    #             "end_frame_number": 463
+    #         },{
+    #             "start_frame_number": 500,
+    #             "end_frame_number": 700
+    #         }]}
+    #
+    # **Expected response (If successful):**
+    # {
+    #     "updated_segments": [
+    #         {
+    #             "id": 1,
+    #             "video_id": 1,
+    #             "label_id": 12,
+    #             "start_frame_number": 0,
+    #             "end_frame_number": 463
+    #         }
+    #     ],
+    #     "new_segments": [
+    #         {
+    #             "id": 2,
+    #             "video_id": 1,
+    #             "label_id": 12,
+    #             "start_frame_number": 500,
+    #             "end_frame_number": 700
+    #         }
+    #     ],
+    #     "deleted_segments": 1  # Number of deleted segments if any were removed
+    # }
+ 
+    # **Frontend Integration:**
+    # - Vue.js should send this request when the user **saves changes** to segments.
+    # - The **"Add Segment"** button should allow users to add new segments dynamically.
+    # - The **"Delete Segment"** button should remove segments from the list before submitting.
+    # - The request should be triggered via an `axios.put` call:
+    #
+    path("api/video/<int:video_id>/label/<int:label_id>/update_segments/", UpdateLabelSegmentsView.as_view(), name="update_label_segments"),
+
+#----------------------------------END--VIDEO SEGMENTATION SECTION-------------------------------
+    #this is for to test the timeline
+    #need to delete this url and also endoreg_db_production/endoreg_db/views/views_for_timeline.py and endoreg_db_production/endoreg_db/templates/timeline.html
+    path('video/<int:video_id>/timeline/', video_timeline_view, name='video_timeline'),
+
+    
+    
+    
+    #  const url = lastId ? `http://localhost:8000/api/video/meta/?last_id=${lastId}` : "http://localhost:8000/api/video/meta/";
+    path("api/video/sensitivemeta/", VideoFileForMetaView.as_view(), name="video_meta"),  # Single endpoint for both first and next video    
+    ]
+
+
+
+
+
+
+#https://biigle.de/manual/tutorials/videos/navigating-timeline#for time line example

endoreg_db-0.6.0/endoreg_db.egg-info/PKG-INFO

@@ -0,0 +1,151 @@
+Metadata-Version: 2.2
+Name: endoreg-db
+Version: 0.6.0
+Summary: EndoReg Db Django App
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: agl-report-reader>=0.4.0
+Requires-Dist: django-bootstrap5>=24.3
+Requires-Dist: django-cors-headers>=4.7.0
+Requires-Dist: django-extensions>=3.2.3
+Requires-Dist: django>=5.1.3
+Requires-Dist: djangorestframework>=3.15.2
+Requires-Dist: faker>=32.1.0
+Requires-Dist: icecream>=2.1.4
+Requires-Dist: numpy>=2.1.3
+Requires-Dist: opencv-python>=4.10.0.84
+Requires-Dist: pandas>=2.2.3
+Requires-Dist: pillow>=11.0.0
+Requires-Dist: pydantic>=2.10.6
+Requires-Dist: pytesseract>=0.3.13
+Requires-Dist: python-ffmpeg>=2.0.12
+Requires-Dist: pytorch-lightning>=2.4.0
+Requires-Dist: pyyaml>=6.0.2
+Requires-Dist: scikit-learn>=1.5.2
+Requires-Dist: scipy>=1.14.1
+Requires-Dist: tesseract>=0.1.3
+Requires-Dist: tqdm>=4.67.0
+Requires-Dist: urllib3>=2.2.3
+
+# EndoregDB - Professional Data Infrastructure for Clinical Research
+
+EndoregDB is a comprehensive database framework designed to manage medical and research-related data for clinical trials. This repository focuses on efficient data processing, automated deployment, security, and reproducibility, offering a flexible setup for local development environments as well as distributed systems. It supports the integration of AI/ML tools and advanced image and report processing.
+
+This infrastructure was originally designed for clinical research studies and is optimized for handling large data volumes, including:
+
+- Medical reports,
+- Patient imaging and video data,
+- Clinical product and treatment data,
+  and more.
+
+## 🚀 Key Features
+
+### System Architecture
+
+- **Modular Design**: Built on scalable and reusable components to simplify integration into various environments.
+- **Multi-System Support**: Manages configurations for local workstations and production servers.
+- **Role-Specific Configuration**: Predefined roles for common use cases:
+  - Medical data processing systems
+  - AI/ML model deployment
+  - Research workstation configuration
+
+### Security & Data Management
+
+- **Data Encryption**: All sensitive data is encrypted, and privacy policies are enforced.
+- **Impermanence**: Stateless system configuration with persistence for critical data.
+- **Access Control**: Role-based access and identity management integration.
+
+### Data and Processing Environment
+
+- **Data Processing**: Optimized for processing medical datasets with preprocessing tools.
+- **AI/ML Support**:
+  - Integration of machine learning tools for predictive analysis.
+  - TensorFlow, PyTorch, and other frameworks supported for model training.
+- **Image/Video Processing**: Support for analyzing patient images and clinical videos.
+
+### Development Tools & Infrastructure
+
+- **Data Science Toolchains**: Pre-configured environments for data processing, analysis, and visualization.
+- **Monitoring & Logging**: Setup for continuous monitoring and logging to ensure system stability and performance.
+
+---
+
+## 🛠 Getting Started
+
+### Prerequisites
+
+- A Linux-based system (Ubuntu/Debian recommended) or NixOS
+- Hardware with sufficient storage for data processing (at least 1 TB recommended)
+
+### Quick Start
+
+1. Clone the repository:
+
+   ```bash
+   git clone https://github.com/wg-lux/endoreg-db.git
+   cd endoreg-db
+   ```
+
+2. Set up your Python environment:
+   _TODO_: Explain Devenv / point to other docs
+
+   ```bash
+   direnv allow
+   ```
+
+3. Run tests:
+   Call Devenv Script to run tests
+
+   ```bash
+   runtests
+   ```
+
+---
+
+## 📁 Repository Structure
+
+```
+endoreg-db/
+├── endoreg_db/                # Main Django app for medical data
+│   ├── case_generator/        # Sample case generator
+│   ├── data/                  # Medical knowledge base
+│   ├── management/            # Data wrangling operations
+│   ├── models/                # Data models
+│   ├── migrations/            # Database migrations
+│   └── serializers/           # Serializers for data
+├── .gitignore                 # Git ignore file for unnecessary files
+└── README.md                  # Project description and setup instructions
+```
+
+---
+
+## 🔒 Security Features
+
+- **Data Encryption**: All sensitive patient data is encrypted.
+- **Role-Based Access Control**: Configurable roles for managing access to various parts of the system.
+- **Logging & Auditing**: Comprehensive logging system that tracks user activities and data changes.
+
+---
+
+## 🖥️ Supported Systems
+
+- **Workstations**: Local development or research workstations with low data processing demands.
+- **Servers**: Scalable server infrastructure for processing large data volumes, integrated with cloud services for scalability.
+
+---
+
+## 🛟 Support
+
+For issues and questions:
+
+- Create an issue in the repository
+- Review the Deployment Guide for common issues
+
+---
+
+## 📜 License
+
+MIT - see LICENSE
+
+---