Skip to content

Conversation

@akshat5302
Copy link
Member

@akshat5302 akshat5302 commented Aug 27, 2025

Summary by CodeRabbit

  • Documentation
    • Updated self-hosting docs to replace a single port with separate HTTP/HTTPS port variables and documented their defaults.
    • Clarified WEB_REPLICAS description for the Community Edition.
    • Revised GUNICORN_WORKERS guidance: clarified per-API instance workers and adjusted defaults for Community vs. Production.
    • Updated Docker self-hosting guide to use the new port variables; refreshed references (e.g., WEB_URL, CORS_ALLOWED_ORIGINS) and examples accordingly.
    • Ensured consistency of environment variable names and usage across self-hosting guides.

@vercel
Copy link

vercel bot commented Aug 27, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
developer-docs Error Error Aug 27, 2025 7:44am

@coderabbitai
Copy link

coderabbitai bot commented Aug 27, 2025

Walkthrough

Documentation updates adjust environment variable names and defaults for self-hosting: replacing NGINX_PORT with LISTEN_HTTP_PORT and LISTEN_HTTPS_PORT, revising WEB_REPLICAS and GUNICORN_WORKERS descriptions in Community edition, and updating Docker Compose guidance and examples to reference the new port variables.

Changes

Cohort / File(s) Change Summary
Env var reference (Govern)
self-hosting/govern/environment-variables.mdx
Replaced NGINX_PORT with LISTEN_HTTP_PORT (80) and LISTEN_HTTPS_PORT (443) in Production and Community sections; updated Community text for WEB_REPLICAS; changed Community GUNICORN_WORKERS description to per-API-instance and default to 1; Production GUNICORN_WORKERS unchanged (2).
Docker Compose guide
self-hosting/methods/docker-compose.mdx
Updated environment variable references: removed NGINX_PORT, added LISTEN_HTTP_PORT (80) and LISTEN_HTTPS_PORT (4430); adjusted WEB_URL and CORS_ALLOWED_ORIGINS examples to reference LISTEN_HTTP_PORT; example addresses still show 8080 where applicable.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my ears at ports anew,
HTTP and HTTPS in view 🐇
Compose now hums with tidy art,
Workers trimmed to do their part.
Replicas hop—distribute the load!
Docs refreshed, I thump the road.
Onward to deploy—let’s go! 🚀

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch remove-unused-community-vars

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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

@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: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
self-hosting/govern/environment-variables.mdx (1)

60-60: Typo: SITE_ADDRES → SITE_ADDRESS.

User-facing variable name; fix to avoid misconfiguration.

-| **SITE_ADDRES** | The domain name and port required by Caddy for serving your Plane instance. This determines how Caddy will handle incoming requests. | `localhost:80` |
+| **SITE_ADDRESS** | The domain name and port required by Caddy for serving your Plane instance. This determines how Caddy will handle incoming requests. | `localhost:80` |
🧹 Nitpick comments (3)
self-hosting/methods/docker-compose.mdx (1)

104-105: Minor wording: “not preoccupied” → “not in use”; mention firewall.

Small clarity bump for readers.

-        - `LISTEN_HTTP_PORT`: This is set to `80` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTP_PORT=8080`
-        - `LISTEN_HTTPS_PORT`: This is set to `443` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTPS_PORT=4430`
+        - `LISTEN_HTTP_PORT`: Default `80`. Ensure the port you choose is not in use and allowed in your firewall. Example: `LISTEN_HTTP_PORT=8080`
+        - `LISTEN_HTTPS_PORT`: Default `443`. Ensure the port you choose is not in use and allowed in your firewall. Example: `LISTEN_HTTPS_PORT=4430`
self-hosting/govern/environment-variables.mdx (2)

169-170: Add cross-reference to WEB_URL/CORS and gateway behavior for CE ports.

Readers benefit from knowing these are the external ports and should align with WEB_URL/CORS.

-| **LISTEN_HTTP_PORT** | Port for HTTP traffic. The primary port your users will connect to. | `80` |
-| **LISTEN_HTTPS_PORT** | Port for HTTPS traffic. The primary port your users will connect to. | `443` |
+| **LISTEN_HTTP_PORT** | External HTTP port exposed by the gateway (Caddy). Align WEB_URL/CORS with this when using `http`. | `80` |
+| **LISTEN_HTTPS_PORT** | External HTTPS port exposed by the gateway (Caddy). Align WEB_URL/CORS with this when using `https`. | `443` |

41-41: Confirm GUNICORN_WORKERS default for Commercial section.

CE defaults to 1 (Line 183). Commercial lists default 2 (Line 41). If intentional, add a brief note explaining the difference to reduce confusion.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a0324ae and 5c7ba7e.

📒 Files selected for processing (2)
  • self-hosting/govern/environment-variables.mdx (1 hunks)
  • self-hosting/methods/docker-compose.mdx (1 hunks)
🔇 Additional comments (1)
self-hosting/methods/docker-compose.mdx (1)

104-107: No lingering references to NGINX_PORT found.
Ran rg -n -C1 '\bNGINX_PORT\b|nginx_port|NGINX PORT' -g '!**/node_modules/**' -g '!**/dist/**' from the repo root and confirmed zero matches, so all stale references have been removed across the docs.

Comment on lines +104 to +107
- `LISTEN_HTTP_PORT`: This is set to `80` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTP_PORT=8080`
- `LISTEN_HTTPS_PORT`: This is set to `443` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTPS_PORT=4430`
- `WEB_URL`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
- `CORS_ALLOWED_ORIGINS`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Clarify WEB_URL/CORS examples to match selected protocol/port variables.

"along with LISTEN_HTTP_PORT" is incorrect when the scheme is https. Use the appropriate port variable per scheme and fix examples.

-        - `WEB_URL`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example,  `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
-        - `CORS_ALLOWED_ORIGINS`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
+        - `WEB_URL`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use, and include the matching port variable for the scheme you select — `LISTEN_HTTP_PORT` for `http`, or `LISTEN_HTTPS_PORT` for `https`. For example: `http://plane.example.com:8080` or `https://plane.example.com:4430`.
+        - `CORS_ALLOWED_ORIGINS`: This is set to `http://localhost` by default. Change this to the FQDN(s) you plan to use, including the corresponding port for the chosen scheme. For example: `http://plane.example.com:8080` or `https://plane.example.com:4430`.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- `LISTEN_HTTP_PORT`: This is set to `80` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTP_PORT=8080`
- `LISTEN_HTTPS_PORT`: This is set to `443` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTPS_PORT=4430`
- `WEB_URL`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
- `CORS_ALLOWED_ORIGINS`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
- `LISTEN_HTTP_PORT`: This is set to `80` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTP_PORT=8080`
- `LISTEN_HTTPS_PORT`: This is set to `443` by default. Make sure the port you choose to use is not preoccupied. For example, `LISTEN_HTTPS_PORT=4430`
- `WEB_URL`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use, and include the matching port variable for the scheme you select — `LISTEN_HTTP_PORT` for `http`, or `LISTEN_HTTPS_PORT` for `https`. For example: `http://plane.example.com:8080` or `https://plane.example.com:4430`.
- `CORS_ALLOWED_ORIGINS`: This is set to `http://localhost` by default. Change this to the FQDN(s) you plan to use, including the corresponding port for the chosen scheme. For example: `http://plane.example.com:8080` or `https://plane.example.com:4430`.
🤖 Prompt for AI Agents
In self-hosting/methods/docker-compose.mdx around lines 104 to 107, the docs
instruct users to change WEB_URL and CORS_ALLOWED_ORIGINS "along with
LISTEN_HTTP_PORT" even when using an https scheme; update the text and examples
so that HTTPS examples reference the LISTEN_HTTPS_PORT variable and HTTP
examples reference LISTEN_HTTP_PORT, e.g. show
https://plane.example.com:LISTEN_HTTPS_PORT (or concrete port like :4430) for
HTTPS and http://[IP-ADDRESS]:LISTEN_HTTP_PORT (or :8080) for HTTP, and adjust
the explanatory sentence to say "along with the corresponding LISTEN_HTTP_PORT
or LISTEN_HTTPS_PORT depending on the scheme."

@sriramveeraghanta sriramveeraghanta merged commit 3bb7dc2 into preview Aug 27, 2025
4 of 5 checks passed
@sriramveeraghanta sriramveeraghanta deleted the remove-unused-community-vars branch August 27, 2025 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants