Skip to content

Conversation

terabytesoftw
Copy link
Member

@terabytesoftw terabytesoftw commented Jul 11, 2025

Q A
Is bugfix ✔️
New feature
Breaks BC

Summary by CodeRabbit

  • Chores
    • Improved container startup output with clearer, color-coded messages.
    • Enhanced setup script to ensure required directories are created with correct permissions and ownership.
    • Adjusted temporary file directory path for PHPStan analysis.
    • Removed redundant directory creation and permission commands from container build process.
    • Updated CI workflow by removing vendor package update step for nginx test environment.
    • Introduced a new container entrypoint script to streamline initialization and startup.

…Yii2 directories; update PHPStan tmpDir configuration and add .gitignore for runtime.
Copy link

coderabbitai bot commented Jul 11, 2025

Warning

Rate limit exceeded

@terabytesoftw has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between fae6fe7 and caa2a32.

📒 Files selected for processing (3)
  • .github/workflows/docker.yml (1 hunks)
  • docker-compose.frankenphp.yml (1 hunks)
  • docker/entrypoint.sh (1 hunks)

Walkthrough

Directory creation and permission management were moved from the Dockerfile to the init.sh script, which was enhanced with structured output, explicit checks, and colored messages. A new entrypoint.sh script was introduced to serve as the container entrypoint, running init.sh with error handling and messaging. The PHPStan configuration was updated to use a different temporary directory path. The GitHub Actions workflow combined Docker build and up commands and removed a composer update step, replacing it with a wait and log output. No changes were made to exported or public entities.

Changes

File(s) Change Summary
docker/frankenphp/Dockerfile Removed directory creation and permission commands; added copying, permission setting, line ending normalization, and syntax checks for entrypoint.sh and init.sh; replaced CMD with ENTRYPOINT running entrypoint.sh.
docker/init.sh, docker/entrypoint.sh init.sh rewritten with explicit directory creation, ownership and permission handling, color-coded output, and error fallbacks; new entrypoint.sh added to run init.sh with error handling and startup messages.
phpstan.neon Changed PHPStan tmpDir from %currentWorkingDirectory%/public/runtime to %currentWorkingDirectory%/runtime.
.github/workflows/docker.yml Combined Docker build and up commands into one; removed composer update step; added wait and container log output step in test-frankenphp job.

Sequence Diagram(s)

sequenceDiagram
    participant Entrypoint as entrypoint.sh
    participant InitScript as init.sh
    participant System as OS
    participant Composer as Composer
    participant Supervisor as supervisord

    Entrypoint->>InitScript: Run initialization script
    InitScript->>System: Create /app/runtime/cache, /app/runtime/logs, /app/public/assets
    InitScript->>System: Set ownership and permissions
    InitScript->>System: Verify directory existence and writability
    InitScript->>Composer: Conditional dependency installation
    InitScript->>System: Set ownership on vendor directory
    InitScript->>Supervisor: Start supervisord
    InitScript-->>Entrypoint: Return success or failure
    Entrypoint->>Entrypoint: Print startup messages and exit accordingly
Loading

Possibly related PRs

Suggested labels

bug

Poem

A bunny hopped through Docker’s den,
Shifting scripts with nimble pen.
From Dockerfile to shell’s embrace,
Directories now find their place.
With colors bright and checks anew,
The rabbit cheers, “This build is true!” 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

Copy link

codecov bot commented Jul 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (6b74197) to head (caa2a32).
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##                main      #110   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity        36        36           
===========================================
  Files             23        23           
  Lines            621       621           
===========================================
  Hits             621       621           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
docker/init.sh (2)

11-20: Collapse mkdir/permission logic into single install -d calls

You can avoid three separate commands per directory:

-mkdir -p /app/runtime/cache
-mkdir -p /app/runtime/logs
-mkdir -p /app/public/assets
-chmod -R 775 /app/runtime
-chmod -R 775 /app/public/assets
-chown -R www-data:www-data /app/runtime
-chown -R www-data:www-data /app/public/assets
+install -d -m 775 -o www-data -g www-data /app/runtime/cache \
+                             /app/runtime/logs \
+                             /app/public/assets

This is faster, atomic, and avoids redundant chmod/chown passes over large trees.


41-58: Composer install: add resilience & speed flags

  1. Fail early if composer is missing:
command -v composer >/dev/null || { echo "Composer not found"; exit 1; }
  1. Use --prefer-dist --no-progress to cut network traffic and log noise.
-composer install --no-dev --optimize-autoloader --no-interaction
+composer install --no-dev --optimize-autoloader --prefer-dist --no-progress --no-interaction

Same for the dev branch.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6b74197 and f3dafd1.

📒 Files selected for processing (3)
  • docker/frankenphp/Dockerfile (0 hunks)
  • docker/init.sh (2 hunks)
  • phpstan.neon (1 hunks)
💤 Files with no reviewable changes (1)
  • docker/frankenphp/Dockerfile
🧰 Additional context used
🧠 Learnings (1)
docker/init.sh (1)
Learnt from: terabytesoftw
PR: yii2-extensions/app-basic#102
File: docker/apache/Dockerfile:0-0
Timestamp: 2025-07-10T13:59:10.805Z
Learning: In docker/apache/Dockerfile, the queue.conf copy command is intentionally commented out because yii2-queue is optional. Users should uncomment the line `COPY docker/apache/supervisord/conf.d/queue.conf /etc/supervisor/conf.d/queue.conf` only if they install yii2-queue.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: codeception / PHP 8.3-windows-latest
  • GitHub Check: codeception / PHP 8.1-windows-latest
  • GitHub Check: codeception / PHP 8.2-windows-latest
  • GitHub Check: codeception / PHP 8.4-windows-latest
  • GitHub Check: test-frankenphp
  • GitHub Check: codeception / PHP 8.4-windows-latest
  • GitHub Check: test-frankenphp
🔇 Additional comments (1)
phpstan.neon (1)

17-17: tmpDir relocation looks good – just confirm the folder exists before CI runs

Moving PHPStan’s tmpDir outside public/ reduces surface-area and matches the new runtime layout.
Please double-check that the runtime/ directory is created (locally and in CI) before PHPStan executes; otherwise PHPStan will fail to create its cache.

@terabytesoftw terabytesoftw added the bug Something isn't working label Jul 11, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
docker/entrypoint.sh (1)

8-9: Avoid the repeated chmod at runtime

init.sh is already copied with the correct mode in the Dockerfile (RUN chmod +x …).
Touching it again on every container start:

  1. Wastes a layer-cache hit by updating the mtime.
  2. Fails when the filesystem is mounted read-only / non-root.

You can safely drop these two lines.

-# Ensure init script is executable
-chmod +x /usr/local/bin/init.sh
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e17877b and fae6fe7.

📒 Files selected for processing (4)
  • .github/workflows/docker.yml (1 hunks)
  • docker/entrypoint.sh (1 hunks)
  • docker/frankenphp/Dockerfile (1 hunks)
  • docker/init.sh (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • docker/frankenphp/Dockerfile
  • docker/init.sh
  • .github/workflows/docker.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: codeception / PHP 8.4-windows-latest
  • GitHub Check: codeception / PHP 8.3-windows-latest
  • GitHub Check: codeception / PHP 8.2-windows-latest
  • GitHub Check: test-frankenphp
  • GitHub Check: test-frankenphp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant