RC 0.5.0 Prepair (#475)

* Enhances documentation and UI/UX

Adds support for release branches to documentation deployment.

Improves the UI by updating the logo, adjusting the layout, adding a footer with version information and links to documentation and GitHub, and enhancing the backend status widget and help button.

Changes the backend to use `granian` instead of `gunicorn` for improved performance.

Adds a script to generate the `latest-version.json` file for checking for updates in the UI.

* Generates JSON for the latest release version

Updates the script to generate JSON data specifically for the latest release version based on the release notes.

This ensures that only the information relevant to the most current version is exposed through the API, improving clarity and relevance for users.

* Improves update banner and version check reliability

Refactors the version check logic to fetch the current version from local release notes and improve the reliability of the update banner.

Updates the end-to-end tests to use more robust locators and improve the stability of the update banner tests.
Also handles potential API errors during version checks more gracefully.

* Updates release notes for v0.4.1

Updates the release notes to include the features, bug fixes, and improvements included in the v0.4.1 release.

Includes automatic update notifications, a fix for storage calculation, and performance improvements.

* Adds granian dependency

Adds granian as a production dependency to improve
application performance.

Removes the release branch from the deploy-docs workflow as it is no longer needed.

* Improves update banner and release notes

Refactors the update banner tests to improve readability and maintainability.

Adds new tests to cover different scenarios, including error handling.

Updates release notes to reflect UI changes.

* Updates documentation URL in e2e test

Updates the documentation URL in the "How to Use" button's e2e test to reflect the new domain.

This ensures that the test verifies the correct link.

* Updates release notes structure

Refactors the release notes documentation for better organization
and clarity. It introduces a version verification logic section,
explaining how the application checks for new releases, emphasizing
privacy and transparency.

This change prepares the release notes for the upcoming v0.4.1 release.

* Refactors release notes documentation

Updates the release notes documentation to improve clarity and maintainability.

This commit refactors the `release-notes.md` file. It clarifies the version verification logic, emphasizing privacy standards. The update streamlines the maintenance and upgrade instructions for users.

The URL for fetching the latest version is also updated.

* Fetches latest version from GitHub Releases API

Updates the version check mechanism to use the GitHub Releases API instead of a custom endpoint.
This simplifies the process and leverages GitHub's infrastructure for release information.
It also removes the need for a custom script to generate the release information.

The release notes documentation and update banner component are updated to reflect this change.

* Improves version check and update banner logic

Updates the version check logic to use semantic versioning for more accurate comparisons.

It extracts the highest semantic version from release notes for current version detection.

Enhances update banner tests to dynamically generate test data based on current and bumped versions.

* Improves version check and UI

Improves the version check logic by normalizing version strings before comparison.
This ensures accurate comparisons even with varying version formats.

Also, prevents images from being draggable.

* Improves update banner and footer link

Updates the "Issues" link in the footer to "Report a Bug" for clarity.

Enhances the update banner test to handle version tags and display version correctly.

Normalizes version strings in update banner logic to ensure correct version matching.

* Refactors supported formats dialog

Improves the supported formats dialog to display verified and experimental formats separately.

Includes a link to GitHub issues for reporting unsupported or problematic formats.
The dialog now clearly distinguishes between verified and experimental formats,
offering users more clarity on the level of support for each format.

* Updates release notes documentation

Refreshes the release notes documentation to improve clarity and accuracy regarding update checks and privacy standards.

Simplifies language and emphasizes user privacy to ensure users understand how the application interacts with the internet for updates.

* Updates release notes for v0.5.0

Updates the release notes to reflect the v0.5.0 release,
including features, improvements, and a corrected version string example.

* Updates installation documentation

Refactors the maintenance and updates section of the installation documentation.

Provides clearer, step-by-step instructions for updating the service using both Docker Compose and Docker Run methods, improving user experience.

* Removes latest version file

Removes the latest version file in preparation for the 0.5.0 release.
The file will be updated with the new version details.

* Adds `@types/semver` and improves input enabling.

Adds `@types/semver` as a dependency.

Improves the logic for enabling the input field, to ensure it's enabled
before attempting to fill it.

* Improves air-gapped deployment and UI feedback

Enhances documentation for air-gapped deployments, noting the impact on update notifications and linking to relevant documentation.

Adds a manual "Check Internet Connection" button to the Web UI with a lightweight reachability test to provide connectivity feedback. The test attempts to connect to Cloudflare DNS without sending any data.

* Adds support and sponsorship information

Introduces a support and sponsorship page detailing professional
services and ways to contribute to the project's development.

This allows users to find options for enterprise deployment,
custom development, security & compliance reviews, and performance
tuning. It also offers a direct sponsorship link to support
ongoing maintenance, bug fixes, and new feature development.

* Updates support and sponsorship information

Refreshes the support and sponsorship documentation
with updated information about professional services
and sponsorship options.

Includes a visual update with a logo.

Author: karimz1

.devcontainer/requirements-dev.txt

@@ -14,9 +14,9 @@ colorama==0.4.6
 flask==3.1.2
 jsonify==0.5
 apscheduler==3.11.2
-gunicorn==23.0.0
 pillow_heif==1.1.1
 pypdfium2==5.3.0
 psd-tools==1.12.1
 rembg==2.0.72
 onnxruntime==1.23.2
+granian==2.6.1

.github/workflows/deploy-docs.yml

@@ -33,7 +33,7 @@ jobs:
         with:
           key: ${{ github.ref }}
           path: .cache
-          
+
       - run: pip install -r docs/requirements.txt
 
       - run: zensical build

backend/image_converter/bootstraper.py

@@ -1,4 +1,4 @@
-import multiprocessing
+import os
 import subprocess
 import traceback
 import pillow_heif
@@ -7,46 +7,23 @@
 from backend.image_converter.presentation.cli.app import main as cli_main
 from backend.image_converter.presentation.web.server import start_scheduler
 
-
-
-def get_workers_count(cpu_multiplier: int = 2, extra_workers: int = 1, min_workers: int = 1) -> int:
-    """
-    Calculate the recommended number of Gunicorn workers based on CPU count.
-
-    The default formula is:
-        workers = (cpu_multiplier * cpu_count) + extra_workers
-    which defaults to:
-        workers = (2 * cpu_count) + 1
-
-    This formula is a common starting point for many applications. However, for
-    CPU-bound tasks (like image processing), you might want to adjust the multiplier
-    or even use a simpler strategy (e.g., one worker per CPU core).
-
-    Parameters:
-        cpu_multiplier (int): The factor to multiply the CPU count by. Default is 2.
-        extra_workers (int): An extra number of workers to add after the multiplication. Default is 1.
-        min_workers (int): Ensures that at least this many workers are returned. Default is 1.
-
-    Returns:
-        int: The recommended number of workers.
-    """
-    try:
-        cpu_count = multiprocessing.cpu_count()
-    except NotImplementedError:
-        cpu_count = 1                                                   
-
-    workers = (cpu_multiplier * cpu_count) + extra_workers
-    return max(workers, min_workers)
-
-
 def launch_web_prod():
     start_scheduler()
+    workers_setting = os.environ.get("GRANIAN_WORKERS", "auto").strip().lower()
+    if workers_setting == "auto":
+        workers = os.cpu_count() or 1
+    else:
+        try:
+            workers = max(int(workers_setting), 1)
+        except ValueError:
+            workers = os.cpu_count() or 1
     subprocess.run([
-        "gunicorn",
-        "-w", str(get_workers_count()),
-        "--timeout", "1800",        
-        "-b", "0.0.0.0:5000",
-        "backend.image_converter.presentation.web.server:app"  
+        "granian",
+        "--interface", "wsgi",
+        "--workers", str(workers),
+        "--host", "0.0.0.0",
+        "--port", "5000",
+        "backend.image_converter.presentation.web.server:app"
     ], check=True)
 
 

backend/image_converter/presentation/web/routes.py

@@ -96,7 +96,14 @@ def storage_info():
     if not storage_management_service.is_storage_management_enabled():
         return _storage_management_disabled_response()
 
-    return jsonify(storage_management_service.get_disk_usage()), 200
+    container_files = temp_folder_service.get_container_files()
+    total_used_mb = container_files.get("total_size_mb", 0)
+    _, _, free = shutil.disk_usage(TEMP_DIR)
+    mib = 1024 * 1024
+    return jsonify({
+        "used_storage_mb": total_used_mb,
+        "available_storage_mb": round(free / mib, 2),
+    }), 200
 
 
 @api_blueprint.route("/force_cleanup", methods=["POST"])

docs/installation.md

@@ -55,14 +55,40 @@ No local dependencies, no configuration clutter. Just a high-performance image o
 
 
 
-## Maintenance & Updates
+### Maintenance & Updates
+
+Keep your instance secure and benefit from the latest features.
+
+=== "Docker Compose (Recommended)"
+
+    1. **Pull the latest version**
+       ```bash
+       docker compose pull
+       ```
+    2. **Restart the service**
+       ```bash
+       docker compose up -d
+       ```
+
+=== "Docker Run"
+
+    1. **Download the image**
+       ```bash
+       docker pull karimz1/imgcompress:latest
+       ```
+    2. **Replace the container**
+       ```bash
+       docker rm -f imgcompress
+       docker run -d \
+         --name imgcompress \
+         -p 3001:5000 \
+         --restart \
+         unless-stopped \
+         karimz1/imgcompress:latest
+       ```
+     3. Once the container is running, open your web browser & navigate to: http://localhost:3001  
 
-Keep your instance secure and up-to-date.
-
-| Method | Command                                                                                                                                                                   |
-| :--- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Docker Compose** | `docker compose pull && docker compose up -d`                                                                                                                             |
-| **Docker Run** | `docker pull karimz1/imgcompress:latest && docker rm -f imgcompress && docker run -d --name imgcompress -p 3001:5000 --restart unless-stopped karimz1/imgcompress:latest` |
+---
 
 ## Choosing Your Version
 
@@ -110,11 +136,11 @@ ___
 For organizations requiring extreme data isolation (e.g., **HIPAA, GDPR, or SOC2**), `imgcompress` supports a fully air-gapped configuration. This workflow severs the container's ability to communicate with the public internet.
 
 !!! danger "Advanced Implementation Only"
-    This reference architecture introduces significant infrastructure complexity. It requires manual maintenance of Docker networking and typically a pre-configured reverse proxy. Use this only if your security model mandates total network isolation.
+    This architecture mandates total network isolation. **By choosing this method, the Web UI cannot notify you of new releases.** You will need to manually monitor the [GitHub Releases](https://github.com/karimz1/imgcompress/releases) to stay current. See [How Updates Notification Work](release-notes.md#transparent-update-checks) for more details.
 
 ### Technical Implementation
 
-To deploy in a zero-egress environment, use the provided hardened configuration, I created as a sample for you:
+To deploy in a zero-egress environment, use the provided hardened configuration I created as a sample for you:
 
 ```yaml
 --8<-- "docker-compose-no-internet.yml"

docs/release-notes.md

@@ -1,10 +1,41 @@
 ---
-title: "Release Notes & Updates: ImgCompress"
-description: Stay up to date with the latest features, bug fixes, and performance improvements in ImgCompress. Check out my version history.
+title: "Release Notes & Updates | ImgCompress"
+description: Transparent version history and update process for ImgCompress.
 ---
 
 # Release Notes
 
-All notable changes to this project will be documented in this file.
+This document tracks all notable changes I've made to **ImgCompress**, including new features, bug fixes, and performance optimizations.
 
---8<-- "frontend/public/release-notes.md"
+---
+
+## Maintenance and Upgrades
+
+To ensure you have the latest features and security patches, I recommend keeping your installation up to date. 
+
+* **Current History:** Review the [Change Log](#change-log) below.
+* **How to Update:** Follow my [**Update Guide**](installation.md#maintenance-updates) to pull the latest Docker image.
+
+---
+
+## Transparent Update Checks
+
+ImgCompress is **100% open source**. I believe in complete transparency regarding how this software interacts with the internet. To ensure you never miss an important fix, I included a privacy-safe update check in the Web UI:
+
+### How it works
+1.  **Local Version:** The app identifies its current version from the local `release-notes.md`.
+2.  **GitHub Check:** The UI makes a single, secure request to the [GitHub Releases API](https://api.github.com/repos/karimz1/imgcompress/releases/latest).
+3.  **Comparison:** If the GitHub version is newer than your local version, an update banner appears in your dashboard.
+
+!!! success "Privacy First"
+    - This process is **anonymous and read-only**.
+    - **Pure Comparison:** The check only compares two version strings (e.g., `v0.4.0` vs `v0.5.0`).
+
+---
+
+## Change Log
+
+!!! tip "Transparency"
+    You can verify every code change I make directly on the [GitHub Repository](https://github.com/karimz1/imgcompress).
+
+--8<-- "frontend/public/release-notes.md"

docs/support.md

@@ -0,0 +1,35 @@
+---
+title: "Support & Sponsorship"
+description: Professional support options and sponsorship for ImgCompress.
+---
+
+# Support & Sponsorship
+
+<p align="center">
+  <img src="/images/logo_transparent.png" width="300" alt="ImgCompress Mascot">
+</p>
+
+ImgCompress is a personal project licensed under **GPL-3.0**. **The core tool will always remain open source and free.** I offer professional services for teams that require dedicated expertise or modifications beyond the standard feature set.
+
+---
+
+## Professional Services
+*Need custom work or features that aren't there yet? I can help.*
+
+| Service | Goal |
+| :--- | :--- |
+| **Custom Workflows** | Assistance in extending the feature set to your specific workflow. |
+| **Specialized Setup** | Help with hardened, air-gapped, or complex Docker environments. |
+| **Optimization** | Tuning the backend for high-volume or specific performance needs. |
+
+!!! quote ""
+    **Business Inquiries:** [karimzouine.com](https://www.karimzouine.com)
+
+---
+
+## 💖 Sponsorship
+*Help fuel the ongoing development and maintenance of this project.*
+
+If ImgCompress provides value to you or your team, consider supporting the project. Your sponsorship directly funds my time for security maintenance, bug fixes, and new feature development.
+
+[Sponsor on GitHub :octicons-heart-fill-16:](https://github.com/sponsors/karimz1){ .md-button .md-button--primary }

docs/web-ui.md

@@ -99,6 +99,19 @@ The interface provides clear visual cues regarding your current network environm
 | :--- | :--- |
 | ![No internet](images/status/no-internet.png) | ![Internet access](images/status/internet-available.png) |
 
+## Network & Connectivity
+
+The Web UI includes a manual **"Check Internet Connection"** button. I've designed this to be as lightweight and transparent as possible.
+
+### How it works
+When you click the button, the tool performs a basic reachability test:
+1. **Target:** It attempts to open a socket connection to `1.1.1.1:53` (Cloudflare DNS).
+2. **Action:** It simply checks if the connection can be established.
+3. **Privacy:** No DNS queries are sent, and no data is transmitted. This is a pure "heartbeat" check to verify outbound access from within the Docker container.
+
+!!! tip "Manual Reachability Only"
+    This check is purely user-initiated. ImgCompress does not perform background pings for connectivity; the request only occurs when you manually click the button.
+
 ### How to Access the Connection Status
 
 1.  Navigate to the **Storage Management** section:

frontend/package.json

@@ -35,6 +35,7 @@
     "react-dom": "^19.2.0",
     "react-dropzone": "^14.3.8",
     "react-toastify": "^11.0.5",
+    "semver": "^7.7.2",
     "sharp": "^0.34.5",
     "tailwind-merge": "^3.4.0",
     "tailwindcss-animate": "^1.0.7",
@@ -45,6 +46,7 @@
     "@playwright/test": "^1.57.0",
     "@tailwindcss/postcss": "^4.1.18",
     "@types/adm-zip": "^0.5.7",
+    "@types/semver": "^7.7.1",
     "@types/node": "^25",
     "@types/react": "^19",
     "@types/react-dom": "^19",