FIX : docs: add missing PORT variable to env example in readme

[RitikBora]

This PR makes a minor update to the README to include the missing PORT environment variable required for running the frontend locally using yarn dev.

I used the steps in the README to setup middleware locally and faced the following error.

.env.example file has it right. Its just missing in the README.

Let me know you if you have any suggestions.

Thanks,
Ritik

Summary by CodeRabbit

• Documentation
  • Updated manual setup instructions to include the PORT=3333 environment variable in the example configuration for running middleware locally.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

The README.md file was updated to include the PORT=3333 environment variable in the example configuration for manual middleware setup, ensuring consistency with other documentation references.

Changes

File(s)	Change Summary
README.md	Added PORT=3333 to the .env example in manual setup instructions

Poem

A port to set, a number true,
Three-three-three-three, now in view!
The docs align, the setup’s neat,
Middleware runs without defeat.
With every hop and every line,
Our README shines—how fine, how fine!
🐇✨

---

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.
  • 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

278-289: Add a brief inline comment and keep port variables clustered for readability
A one-liner comment (like the other blocks often use) clarifies what this port controls, and grouping it with the other exposed service ports improves scan-ability.

 ANALYTICS_SERVER_PORT=9696
 SYNC_SERVER_PORT=9697
-PORT=3333
+# Frontend / web-server port
+PORT=3333

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bafb28c and c384670.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

288-288: Addition aligns env documentation with actual .env.example – good catch
The PORT=3333 line removes the discrepancy and prevents “missing PORT” errors when running yarn dev.

[jayantbh]

Strange because it should just take the port by default if not supplied.
Nonetheless, if this helps, let's add this