Fix failing imagick

[cardil]

Summary by CodeRabbit

• Chores
  • Upgraded the PHP runtime environment to a newer version for improved stability and performance.
  • Updated the extension installer tool and streamlined image processing extension configuration to ensure access to the latest available features.

[coderabbitai]

Walkthrough

The pull request updates the Containerfile by upgrading the base PHP image from php:8-fpm to php:8.3-fpm and revising the PHP extension installer script URL from version 2.6.3 to 2.7.28. It also simplifies the installation of the imagick extension by replacing a fixed commit reference with the extension’s name, allowing the latest version to be used.

Changes

File	Change Summary
Containerfile	- Base Image: Updated from php:8-fpm to php:8.3-fpm - Installer URL: Changed from version 2.6.3 to 2.7.28 - Imagick Extension: Specified as imagick instead of a fixed commit reference

Possibly related PRs

• Updated the image for PHP 8.3 with a few added extensions, plus a GH actions build #1: Adjusts the Containerfile to enhance the PHP extension installation process, closely relating to the modifications in this PR.

Poem

In the realm of code, I hop with glee,
Updating PHP in containers, oh me!
Extensions dance with no commit in sight,
A newer, brighter version takes flight.
CodeRabbit cheers with a joyful byte! 🐇✨

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf5f364 and 0e447d8.

📒 Files selected for processing (1)

• Containerfile (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build images

🔇 Additional comments (3)

Containerfile (3)

1-1: Good upgrade to specific PHP version.

Upgrading from the generic php:8-fpm to the specific php:8.3-fpm is a positive change. This ensures we're using the latest stable PHP 8.3 release which has performance improvements and bug fixes that might help with the imagick compatibility issue.

---

5-5: Extension installer update improves compatibility.

Updating the PHP extension installer from version 2.6.3 to 2.7.28 is a good practice. The newer version likely includes better support for PHP 8.3 and may have fixed issues with extension installations, particularly for imagick.

---

18-18:

Details

✅ Verification successful

Using default imagick version resolves the failing installation.

Simplifying from a pinned commit hash (imagick/imagick@28f27044e435a2b203e32675e942eb8de620ee58) to just imagick allows the installer to use the latest compatible version, which should resolve the failing installation issue.

While using the latest version improves maintainability, consider if version pinning might be needed in the future for reproducible builds.

---

🏁 Script executed:

#!/bin/bash
# Verify that the PHP and imagick versions are compatible by checking the installer script's support
curl -s https://raw.githubusercontent.com/mlocati/docker-php-extension-installer/master/data/supported-extensions | grep -A 3 -B 3 imagick

Length of output: 502

---

Verification Approved: Default imagick Version is Valid

The executed script confirms that the installer supports the unpinned "imagick" extension for all relevant PHP versions, making the simplification appropriate. While using the latest compatible version addresses the installation issue, please keep in mind that version pinning might be necessary later to ensure reproducible builds.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.