docs: Add reverse proxy X-Forwarded-Port blurb#33
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughDocumentation update adds a clarifying note about configuring ChangesReverse proxy configuration clarification
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested labels
Poem
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/integration/kobo.md`:
- Around line 39-40: The admonition started with :::info[X-Forwarded-Port] is
left unclosed; update the block to follow the same open/body/close pattern used
elsewhere by placing the explanatory text as the body beneath the opener and
adding a closing ::: on its own line (i.e., keep the existing opener
':::info[X-Forwarded-Port]', move the explanatory sentence into the body, then
add ':::' to end the admonition).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: d4cd48b9-b7f0-493e-a5ac-78f4f07b5b6d
📒 Files selected for processing (1)
docs/integration/kobo.md
Co-authored-by: James Ward <james@notjam.es>
Description
It's common for reverse proxy homelab setups to port forward a different public port to different internal port that the reverse proxy is listening on. Added a blurb to point out that X-Forwarded-Port may need a different setting.
Linked Issue
https://github.com/orgs/grimmory-tools/discussions/1476
Changes
Add info section to clarify
X-Forwarded-Portreverse proxy header valuesAI Disclosure
AI not used
Checklist
npm run buildand/ornpm run typecheck.Summary by CodeRabbit
Summary by CodeRabbit