Update Dockerfile

Dockerfile

@@ -1,61 +1,48 @@
 # Use an official Python runtime as a parent image
 FROM python:3.10-slim
 
-# Set environment variables to prevent interactive prompts during apt-get install
-ENV DEBIAN_FRONTEND=noninteractive
-
-# Install system dependencies
-RUN apt-get update && \
-    (if [ -f /etc/apt/sources.list.d/debian.sources ]; then \
-        echo "Modifying /etc/apt/sources.list.d/debian.sources to include contrib and non-free-firmware" && \
-        sed -i -e 's/^Components: main$/Components: main contrib non-free-firmware/' \
-               -e 's/^Components: main\( .*\)$/Components: main contrib non-free-firmware\1/' \
-               /etc/apt/sources.list.d/debian.sources; \
-     else \
-        echo "/etc/apt/sources.list.d/debian.sources not found, checking /etc/apt/sources.list"; \
-     fi) && \
-    (if [ -f /etc/apt/sources.list ]; then \
-        echo "Modifying /etc/apt/sources.list to include contrib and non-free-firmware" && \
-        sed -i 's/main$/main contrib non-free-firmware/g' /etc/apt/sources.list; \
-     else \
-        echo "/etc/apt/sources.list not found."; \
-     fi || true) && \
-    apt-get update && \
-    apt-get install -y --no-install-recommends \
-    libgl1-mesa-glx \
-    libglib2.0-0 \
-    fontconfig \
-    && echo "ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true" | debconf-set-selections \
-    && apt-get install -y --no-install-recommends ttf-mscorefonts-installer \
-    && apt-get clean \
-    && rm -rf /var/lib/apt/lists/* \
-    && fc-cache -f -v
-
-# Set the working directory
+# Set the working directory in the container
 WORKDIR /app
 
-# Create a non-root user and group
-RUN groupadd -g 1000 appuser && useradd --no-log-init -u 1000 -g appuser appuser
+# 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 ./app/data
 
-# Copy all application files from the repository root to /app
-# This means 'templates' directory, 'arial.ttf' (if you use it), etc., MUST be in your repo root.
-COPY . .
+chmod -R 777 ./app/data
 
-# Ensure necessary directories exist and set ownership for the entire /app directory.
-# 'templates' should be copied by 'COPY . .'. 'generated_images' and session dir (which is /app) need to be writable.
-RUN mkdir -p ./app/generated_images && \
-    chown -R appuser:appuser ./app
+# Copy the requirements file into the container at /app
+COPY requirements.txt .
 
-# Install Python dependencies
+# Install any needed packages specified in requirements.txt
+# --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
 
-# Switch to the non-root user
-USER appuser
-
-# Environment variables for secrets (set these in Hugging Face Space settings)
-ENV BOT_TOKEN=""
-ENV API_ID=""
-ENV API_HASH=""
+# Copy the rest of the application code (e.g., main.py) into the container at /app
+COPY . .
 
 # Command to run the application
+# This will execute your main.py script when the container launches.
 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.