chore(docker): Optimize Dockerfile and enhance build process

[EvickaStudio]

Refactored Dockerfile to use Alpine base for smaller image size and improved build efficiency. Added a build script for optimized image creation and updated docker-compose configuration with health checks and resource limits. Expanded .dockerignore to exclude unnecessary files and directories, ensuring cleaner builds.

Summary by Sourcery

Refactor the Dockerfile to use an Alpine base image, reducing the image size and improving build efficiency. Introduce a build script for optimized image creation and update the docker-compose configuration with health checks and resource limits. Enhance the .dockerignore file to exclude unnecessary files and directories.

Build:

• Refactor the Dockerfile to use an Alpine base image, reducing the image size.
• Introduce a build script for optimized image creation.
• Update the docker-compose configuration with health checks and resource limits.
• Enhance the .dockerignore file to exclude unnecessary files and directories, ensuring cleaner builds.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request focuses on optimizing the Docker setup for the MoodleMate application. It includes changes to the Dockerfile to reduce image size and improve build efficiency by switching to an Alpine Linux base image, leveraging build cache, and creating a non-privileged user. Additionally, the docker-compose file has been updated with health checks and resource limits. A build script was added to streamline the image creation process, and the .dockerignore file was expanded to exclude unnecessary files.

Updated class diagram for Dockerfile

classDiagram
    class Dockerfile {
        -Base Image: python:3.12-alpine
        -User: moodlemate
        -Working Directory: /app
        +Create user and group
        +Copy application code
        +Set permissions
        +Install dependencies
    }
    note for Dockerfile "Optimized for smaller image size and security"

Loading

File-Level Changes

Change	Details	Files
Refactored the Dockerfile to use an Alpine Linux base image, optimize layer caching, and reduce the final image size.	Switched the base image from python:3.12-slim-bookworm to python:3.12-alpine. Installed build dependencies using apk instead of apt-get. Copied requirements.txt separately to leverage Docker's layer caching. Created a non-privileged user moodlemate and set appropriate permissions. Combined user creation and directory preparation into a single layer. Used multi-stage builds to reduce the final image size. Added --chown flag to the COPY command to set the correct ownership for copied files.	Dockerfile
Enhanced the docker-compose configuration with health checks and resource limits.	Added a health check to the service definition. Included resource limits (memory) for the container. Set the PYTHONUNBUFFERED environment variable to 1. Added BUILDKIT_INLINE_CACHE argument to the build definition.	docker-compose.yml
Added a build script to streamline the Docker image creation process.	Implemented a build.sh script that uses docker buildx build to create optimized images with zstd compression.	build.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @EvickaStudio - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using multi-stage builds to further reduce the final image size by not including the venv in the final image.
• The healthcheck could be more specific to the application's health rather than just checking if python runs.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion: Review the minimal healthcheck implementation.

The healthcheck command simply executes a harmless Python snippet. Ensure that this adequately reflects the health of your service. If a more comprehensive check is needed, consider expanding the command.

Suggested implementation:

    healthcheck:
      test: ["CMD", "python", "-c", "import socket; socket.create_connection(('localhost', 8000), 3).close()"]

This change assumes that your service is available on localhost:8000. If it is listening on a different host or port, please update the connection parameters accordingly. Additionally, if you need a more sophisticated application-level check (e.g., verifying an API endpoint), consider replacing the command with one that uses a tool like curl.