Update Dockerfile

Dockerfile

@@ -4,45 +4,30 @@ FROM python:3.10-slim
 # Set the working directory in the container
 WORKDIR /app
 
-# Create the data directory for persistent template storage
-# This ensures the directory exists when the application starts.
-# Permissions are usually fine by default for the user running the app.
-RUN mkdir -p ./data/app_template_storage && \
-
-chmod -R 777 ./data/app_template_storage
-
-# Copy the requirements file into the container at /app
+# Define an argument for the data directory name (for flexibility)
+ARG APP_TEMPLATE_DIR_NAME=app_template_storage
+
+# Create the specific data directory for templates AND set permissions.
+# The './' ensures it's relative to WORKDIR (/app).
+# This command runs as root during the image build.
+RUN mkdir -p ./${APP_TEMPLATE_DIR_NAME} && \
+    chmod -R 777 ./${APP_TEMPLATE_DIR_NAME}
+# IMPORTANT on chmod 777:
+# This gives read, write, and execute permissions to everyone (owner, group, others).
+# While it solves permission issues, it's very open.
+# For production, you'd ideally find the UID your app runs as on Hugging Face
+# and chown the directory to that user, or use more restrictive permissions (e.g., 755, 775).
+# However, for troubleshooting and typical Hugging Face Space usage, 777 is a common fix.
+
+# Copy the requirements file into the container
 COPY requirements.txt .
 
-# Install any needed packages specified in requirements.txt
+# Install Python dependencies
 # --no-cache-dir reduces image size
-# Ensure Hydrogram and any other dependencies are in requirements.txt
 RUN pip install --no-cache-dir -r requirements.txt
 
-# Copy the rest of the application code (e.g., main.py) into the container at /app
+# Copy the rest of your application code (e.g., main.py) into the container
 COPY . .
 
-# Command to run the application
-# This will execute your main.py script when the container launches.
+# Command to run your Python application
 CMD ["python", "main.py"]
-
-# --- Persistence Note for Docker (and similar platforms) ---
-# The `RUN mkdir -p /app/data` line creates the directory INSIDE the container image.
-# If the container is stopped and removed, and a new one is started from the image,
-# this directory will be "fresh" (empty, or as it was when the image was built).
-#
-# To make the template content in `/app/data` truly persistent across container
-# restarts and deployments (so you don't lose the template), you would use a Docker Volume.
-# When running the container, you would mount a volume to `/app/data`:
-#
-# docker run -d -v my_template_data:/app/data <your_image_name>
-#
-# - `my_template_data` is the name of the Docker volume on the host.
-# - `:/app/data` maps this volume to the `/app/data` directory inside the container.
-#
-# Hugging Face Spaces often handles some level of persistence for the main app directory,
-# so the `data/` subfolder might persist. However, if you need guaranteed persistence
-# that survives complete rebuilds or more complex scenarios, you'd look into the specific
-# persistence options offered by the platform (which might abstract Docker volumes).
-# For simple cases on HF Spaces, just creating the directory and writing to it usually works
-# for persistence across restarts of the same deployment.