solved uneven layout of sidebar

Author: Dushyant Bhardwaj

.github/workflows/pr-tests.yml

@@ -16,7 +16,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v3
         with:
-          node-version: '18'
+          node-version: "18"
 
       - name: Install Dependencies
         run: |

.pre-commit-config.yaml

@@ -3,10 +3,10 @@ repos:
     rev: "v0.0.241"
     hooks:
       - id: ruff
-        args: [--fix] 
+        args: [--fix]
 
   - repo: https://github.com/psf/black
-    rev: "22.3.0" 
+    rev: "22.3.0"
     hooks:
       - id: black
-        language_version: python3
+        language_version: python3

backend/app/logging_config.json

@@ -1,10 +1,10 @@
 {
-    "logger": {
-        "path": "app/logs/PictoPy.log",
-        "filename": "PictoPy.log",
-        "level": "info",
-        "rotation": "1 days",
-        "retention": "1 months",
-        "format": "<level>{level: <8}</level> <green>{time:YYYY-MM-DD HH:mm:ss.SSS}</green> request id: {extra[request_id]} - <cyan>{name}</cyan>:<cyan>{function}</cyan> - <level>{message}</level>"
-    }
-}
+  "logger": {
+    "path": "app/logs/PictoPy.log",
+    "filename": "PictoPy.log",
+    "level": "info",
+    "rotation": "1 days",
+    "retention": "1 months",
+    "format": "<level>{level: <8}</level> <green>{time:YYYY-MM-DD HH:mm:ss.SSS}</green> request id: {extra[request_id]} - <cyan>{name}</cyan>:<cyan>{function}</cyan> - <level>{message}</level>"
+  }
+}

docker-compose.yml

@@ -32,4 +32,3 @@ services:
 volumes:
   frontend-data:
   images-data:
-

docs/backend/docker-setup.md

@@ -1,107 +1,107 @@
-# Backend Docker Setup for PictoPy
-
-This guide provides step-by-step instructions for building and running the PictoPy backend using Docker.
-
-## Table of Contents
-
-1. [Prerequisites](#prerequisites)
-2. [Building the Docker Image](#building-the-docker-image)
-3. [Running the Docker Container](#running-the-docker-container)
-4. [Verifying the Container](#verifying-the-container)
-5. [Accessing the Application](#accessing-the-application)
-6. [Stopping the Container](#stopping-the-container)
-7. [Troubleshooting](#troubleshooting)
-
-## Prerequisites
-
-Before you begin, ensure you have the Docker installed on your machine
-
-- Verify the installation by running:
-  ```bash
-  docker --version
-  ```
-
-## Building the Docker Image
-
-1. Open a terminal and navigate to your project's root directory.
-
-2. Go to Backend directory
-
-   ```bash
-   cd backend
-   ```
-
-3. Run the following command to build the Docker image, replacing `<image_name>` with your desired image name:
-
-   ```bash
-   docker build -t <image_name> .
-   ```
-
-4. Wait for the build process to complete. This may take a few minutes depending on your internet speed and system performance.
-
-## Running the Docker Container
-
-Once the image is built, you can run a container using the following command:
-
-```bash
-docker run -it --name backend-container -p 8000:8000 \
--v images-data:/app/images \
--v /:/host \
-<image-name>
-```
-
-- `-it`: Runs the container interactively, attaching to the terminal for input/output.
-- `-p 8000:8000`: Maps port 8000 on the host to port 8000 in the container.
-- `-v`: Mounts a volume to share data between the host and container.
-- `<image_name>`: Specifies the image to use (the one we just built).
-
-## Verifying the Container
-
-To check if the container is running:
-
-```bash
-docker ps
-```
-
-You should see an entry for `<container_name>` with the status `Up`.
-
-## Accessing the Application
-
-Open a web browser or frontend to access the application at:
-
-```
-http://localhost:8000
-```
-
-## Stopping the Container
-
-If you need to stop the container:
-
-```bash
-docker kill <container_id>
-```
-
-## Troubleshooting
-
-1. **Port already in use**: If you get an error saying the port is already in use, you can either:
-
-   - Stop the process using port 8000, or
-   - Change the port mapping in the `docker run` command (e.g., `-p 8001:8000`)
-
-2. **Container exits immediately**: Check the container logs:
-
-   ```bash
-   docker logs <container_name>
-   ```
-
-3. **Permission issues**: Ensure that `run.sh` has execute permissions(for linux only):
-
-   ```bash
-   chmod +x run.sh
-   ```
-
-   Then rebuild the Docker image.
-
-Remember to rebuild your Docker image (`docker build -t <image_name> .`) after making any changes to your application or Dockerfile.
-
-For more advanced Docker usage , view the [Docker documentation](https://docs.docker.com/get-started/).
+# Backend Docker Setup for PictoPy
+
+This guide provides step-by-step instructions for building and running the PictoPy backend using Docker.
+
+## Table of Contents
+
+1. [Prerequisites](#prerequisites)
+2. [Building the Docker Image](#building-the-docker-image)
+3. [Running the Docker Container](#running-the-docker-container)
+4. [Verifying the Container](#verifying-the-container)
+5. [Accessing the Application](#accessing-the-application)
+6. [Stopping the Container](#stopping-the-container)
+7. [Troubleshooting](#troubleshooting)
+
+## Prerequisites
+
+Before you begin, ensure you have the Docker installed on your machine
+
+- Verify the installation by running:
+  ```bash
+  docker --version
+  ```
+
+## Building the Docker Image
+
+1. Open a terminal and navigate to your project's root directory.
+
+2. Go to Backend directory
+
+   ```bash
+   cd backend
+   ```
+
+3. Run the following command to build the Docker image, replacing `<image_name>` with your desired image name:
+
+   ```bash
+   docker build -t <image_name> .
+   ```
+
+4. Wait for the build process to complete. This may take a few minutes depending on your internet speed and system performance.
+
+## Running the Docker Container
+
+Once the image is built, you can run a container using the following command:
+
+```bash
+docker run -it --name backend-container -p 8000:8000 \
+-v images-data:/app/images \
+-v /:/host \
+<image-name>
+```
+
+- `-it`: Runs the container interactively, attaching to the terminal for input/output.
+- `-p 8000:8000`: Maps port 8000 on the host to port 8000 in the container.
+- `-v`: Mounts a volume to share data between the host and container.
+- `<image_name>`: Specifies the image to use (the one we just built).
+
+## Verifying the Container
+
+To check if the container is running:
+
+```bash
+docker ps
+```
+
+You should see an entry for `<container_name>` with the status `Up`.
+
+## Accessing the Application
+
+Open a web browser or frontend to access the application at:
+
+```
+http://localhost:8000
+```
+
+## Stopping the Container
+
+If you need to stop the container:
+
+```bash
+docker kill <container_id>
+```
+
+## Troubleshooting
+
+1. **Port already in use**: If you get an error saying the port is already in use, you can either:
+
+   - Stop the process using port 8000, or
+   - Change the port mapping in the `docker run` command (e.g., `-p 8001:8000`)
+
+2. **Container exits immediately**: Check the container logs:
+
+   ```bash
+   docker logs <container_name>
+   ```
+
+3. **Permission issues**: Ensure that `run.sh` has execute permissions(for linux only):
+
+   ```bash
+   chmod +x run.sh
+   ```
+
+   Then rebuild the Docker image.
+
+Remember to rebuild your Docker image (`docker build -t <image_name> .`) after making any changes to your application or Dockerfile.
+
+For more advanced Docker usage , view the [Docker documentation](https://docs.docker.com/get-started/).

docs/docker-compose/redme.md

@@ -1,4 +1,3 @@
-
 # Docker Compose Setup
 
 This repository includes a Docker Compose configuration to streamline the deployment of services for your application. By using Docker Compose, you can set up and run the entire stack with just a few commands.
@@ -18,39 +17,41 @@ docker-compose --version
 ```
 
 - For Linux : An X server also installed (If not installed)
-    ```bash
-    sudo apt install x
-    ```
-    Allow X11 forwarding:
-    ```bash
-    xhost +local:docker
-    ```
 
-- For Windows: An X Server (e.g., VcXsrv or Xming)
-    - Start an X Server:
-        1. Launch VcXsrv or Xming.
-        2. Configure it to allow connections from any host.
+  ```bash
+  sudo apt install x
+  ```
 
-    - Find your host machine's IP address:
-        1. Open Command Prompt and run `ipconfig`.
-        2. Look for the IPv4 Address under your active network adapter.
+  Allow X11 forwarding:
 
-    - Run the container:
-        ```bash
-        docker run -it -p 1420:1420 -e DISPLAY=<HOST_IP>:0.0  <image-name>
-        ```
-        Replace `<HOST_IP>` with your actual IP address.
+  ```bash
+  xhost +local:docker
+  ```
+
+- For Windows: An X Server (e.g., VcXsrv or Xming)
 
+  - Start an X Server:
 
+    1. Launch VcXsrv or Xming.
+    2. Configure it to allow connections from any host.
 
+  - Find your host machine's IP address:
 
+    1. Open Command Prompt and run `ipconfig`.
+    2. Look for the IPv4 Address under your active network adapter.
+
+  - Run the container:
+    ```bash
+    docker run -it -p 1420:1420 -e DISPLAY=<HOST_IP>:0.0  <image-name>
+    ```
+    Replace `<HOST_IP>` with your actual IP address.
 
 ## Services
 
 The Docker Compose file in this repository orchestrates the following services:
 
 1. **Backend** : The application backend service.
-4. **Frontend** : The application frontend service.
+2. **Frontend** : The application frontend service.
 
 ## Getting Started
 
@@ -74,6 +75,7 @@ dos2unix run.sh
 ```
 
 ### Step 3 : Move to Actual Location (PictoPy)
+
 ```bash
 cd ..
 ```
@@ -105,17 +107,16 @@ To stop services without removing the data:
 docker compose stop
 ```
 
-
 ## How to 'Add Folder' Instructions
 
 Since Docker containers are isolated from each other, we cannot directly access the folders of other containers. This is where the concept of volume mounting comes into play.where if you run your application via docker then for adding folders of your host machine
-  
-  1. Click the Path **Other Locations**
-  2. Then click **Computer**
-  3. After that click **host**
-  
-  (Genrally in Linux , **C** and **D** Drive are located in **mnt** folder)
+
+1. Click the Path **Other Locations**
+2. Then click **Computer**
+3. After that click **host**
+
+(Genrally in Linux , **C** and **D** Drive are located in **mnt** folder)
 
 Now in this **host** location all of your host machine's files are available now you can add any folder from this path .
 
-At all if you face any problem Click the [Video Demo](https://s3.eu-north-1.amazonaws.com/jibeshroy.static.dev/Pictopy/FINAL_OUTPUT.mp4) 
+At all if you face any problem Click the [Video Demo](https://s3.eu-north-1.amazonaws.com/jibeshroy.static.dev/Pictopy/FINAL_OUTPUT.mp4)