docs: add web server configuration guide for feature branch deployment#22
docs: add web server configuration guide for feature branch deployment#22konradmichalik merged 3 commits intomainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe PR performs stylistic refactoring of comparison expressions in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/WEBSERVER.md (1)
44-48:deny all;is unreachable —return 403;alone is sufficient.In nginx's processing pipeline,
return(rewrite phase) runs beforedeny(access phase). Oncereturn 403;is evaluated, the access module never runs, makingdeny all;dead configuration. Using either directive alone is cleaner.♻️ Proposed simplification
# Deny access to protected directories across all instances location ~ /(typo3conf|var|config)/ { - deny all; return 403; }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/WEBSERVER.md` around lines 44 - 48, The nginx location block "location ~ /(typo3conf|var|config)/" contains both "deny all;" and "return 403;", but "return 403;" executes earlier and makes "deny all;" unreachable; remove the redundant "deny all;" (or alternatively remove "return 403;") so only a single directive enforces the 403 response in that location block, keeping the location regex and message unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/WEBSERVER.md`:
- Around line 51-56: Add a short adaptation note and inline comment around the
PHP location block (the location ~ \.php$ { ... } section) explaining that the
fastcgi_pass path (fastcgi_pass unix:/run/php/php-fpm.sock;) is
Debian/Ubuntu-specific and list common alternatives (e.g.,
/run/php/php8.x-fpm.sock for versioned Ubuntu, /run/php-fpm/www.sock for
CentOS/RHEL, or TCP 127.0.0.1:9000 for custom setups); update both the TYPO3 and
Symfony examples and include the comment next to the fastcgi_pass line so users
know to adjust the socket to avoid 502 errors.
---
Nitpick comments:
In `@docs/WEBSERVER.md`:
- Around line 44-48: The nginx location block "location ~
/(typo3conf|var|config)/" contains both "deny all;" and "return 403;", but
"return 403;" executes earlier and makes "deny all;" unreachable; remove the
redundant "deny all;" (or alternatively remove "return 403;") so only a single
directive enforces the 403 response in that location block, keeping the location
regex and message unchanged.
|
@coderabbitai Good catch on the unreachable |
|
Tip For best results, initiate chat on the files or code changes.
|
Summary
docs/WEBSERVER.mdcovering Apache and nginx prerequisites for feature branch deploymentsdocs/FEATURE.mdprerequisites sectionChanges
docs/WEBSERVER.md- New guide covering Apache (AllowOverride All) and nginx (symlinks, PHP-FPM, URL rewriting with example configs)docs/FEATURE.md- Add web server reference link in prerequirements, following the existingDATABASE.mdpatterndeployer/requirements/functions.php- Apply yoda conditions andfnspacing (CGL)Summary by CodeRabbit