Skip to content

Comments

feat: updated installation guide in readme Implements #1360#1396

Closed
Malayt04 wants to merge 2 commits intoMail-0:stagingfrom
Malayt04:feature/updated-installation-guide
Closed

feat: updated installation guide in readme Implements #1360#1396
Malayt04 wants to merge 2 commits intoMail-0:stagingfrom
Malayt04:feature/updated-installation-guide

Conversation

@Malayt04
Copy link
Contributor

@Malayt04 Malayt04 commented Jun 20, 2025

In this update

  • Updated the installation guide on the readme section for better understanding

Summary by CodeRabbit

  • Documentation
    • Completely revised the README for improved clarity and structure.
    • Updated setup instructions with a streamlined, step-by-step guide.
    • Enhanced guidance for configuring external services and environment variables.
    • Added recommendations for Windows users.
    • Updated sponsor logos and improved visual presentation.
    • Included a link to the translation guide in the contribution section.
    • Made minor text and formatting improvements throughout.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 20, 2025

Walkthrough

The README.md file was thoroughly rewritten to enhance clarity and user guidance for local setup of the Zero project. The update restructures setup instructions, revises the logo and tagline, adds detailed environment variable explanations, and improves sections for external service configuration, contribution, and sponsor display.

Changes

File(s) Summary of Changes
README.md Complete rewrite for clarity and structure; updated logo style, tagline, setup instructions, env variable table, external service setup, contribution guide, and sponsor display.

Possibly related PRs

  • Mail-0/Zero#429: Also modifies README.md setup instructions, but with a single command addition rather than a full rewrite.
  • Mail-0/Zero#438: Adds a translation guide link to README.md, overlapping with the contribution section changes in this PR.
  • Mail-0/Zero#428: Updates README.md to fix a directory name typo within setup instructions, related by file and purpose.

Poem

Hopping through docs with nimble delight,
I tidied the README all through the night.
With logos and guides and setup anew,
Now Zero’s instructions are clear for you!
🥕✨
Just follow each step and soon you shall see,
A project well-started—by rabbit and thee!


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
Contributor

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

🧹 Nitpick comments (6)
README.md (6)

4-4: Extract inline styles for maintainability
The <img> tag includes inline CSS which can be hard to update and may not render consistently across platforms. Consider simplifying the HTML or centralizing styling (e.g., via a CSS file or utility classes).


10-10: Remove trailing period in tagline
Headings and taglines typically omit terminal punctuation for cleaner presentation. You may want to drop the final . to match common markdown heading style.


44-47: Enforce consistent unordered-list style
Current list items use * but the repo’s markdown lint expects -.

- * [Node.js](https://nodejs.org/en/) (v18 or later recommended)
- * [pnpm](https://pnpm.io/installation)
- * [Docker](https://www.docker.com/products/docker-desktop/) & Docker Compose
+ - [Node.js](https://nodejs.org/en/) (v18 or later recommended)
+ - [pnpm](https://pnpm.io/installation)
+ - [Docker](https://www.docker.com/products/docker-desktop/) & Docker Compose

117-118: Use GitHub-compatible warning syntax
The [!WARNING] block may not render on GitHub. Switch to a simple bold label:

- > [!WARNING]
- > This URI must match **exactly**.
+ > **Warning:** This URI must match **exactly**.

161-163: Remove duplicate translation guide entry
The translation guide link appears twice. Consider removing the second line to avoid redundancy:

- Please refer to the [contributing guide](.github/CONTRIBUTING.md) and the [translation guide](.github/TRANSLATION.md).
- If you'd like to help with translating Zero to other languages, check out our [translation guide](.github/TRANSLATION.md).
+ Please refer to the [contributing guide](.github/CONTRIBUTING.md) and the [translation guide](.github/TRANSLATION.md).

171-171: Reduce inline HTML for logo container
The <div style="..."> wrapper uses inline flex styles. Markdown-level layouts (e.g., <div align="center"> or a simple table) are often more portable and easier to maintain.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c5d5479 and ca61cdc.

📒 Files selected for processing (1)
  • README.md (4 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

45-45: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


46-46: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


47-47: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

🔇 Additional comments (1)
README.md (1)

40-42: These new sections and command blocks are clear, well-structured, and follow the project's documentation conventions. No issues detected.

Also applies to: 49-58, 60-65, 67-73, 75-82, 84-104, 105-116, 119-124, 125-129, 131-136, 137-143, 186-188

@rohhann12
Copy link

@Malayt04 you can also add about twilio, dont want to make another pr just for this, if you can update

@Malayt04
Copy link
Contributor Author

@rohhann12 Yeah makes sense. Will modify it

Copy link
Contributor

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

🧹 Nitpick comments (2)
README.md (2)

45-47: Unify list markers for consistency.

Switch asterisk bullets to dashes to match the existing list style:

- * [Node.js](https://nodejs.org/en/) (v18 or later recommended)
- * [pnpm](https://pnpm.io/installation)
- * [Docker](https://www.docker.com/products/docker-desktop/) & Docker Compose
+ - [Node.js](https://nodejs.org/en/) (v18 or later recommended)
+ - [pnpm](https://pnpm.io/installation)
+ - [Docker](https://www.docker.com/products/docker-desktop/) & Docker Compose

168-170: Remove duplicated translation guide link.

The translation guide is mentioned twice. Consider removing one occurrence to avoid redundancy:

- If you'd like to help with translating Zero to other languages, check out our [translation guide](.github/TRANSLATION.md).
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ca61cdc and caab99a.

📒 Files selected for processing (1)
  • README.md (4 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

45-45: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


46-46: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


47-47: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

🔇 Additional comments (6)
README.md (6)

4-4: Logo styling enhancement approved.

The updated <img> tag includes padding and border-radius for improved visual appearance.


10-10: Updated tagline approved.

The new tagline is punctuated and clear.


40-40: New welcome message approved.

The introductory line clearly guides contributors.


101-104: Twilio environment variables added.

Including TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, and TWILIO_PHONE_NUMBER ensures SMS support is documented.


125-131: Twilio setup instructions approved.

The step-by-step guide for configuring Twilio credentials is clear and comprehensive.


178-178: Sponsor logos layout improvement approved.

Adding gap and vertical alignment enhances the sponsor section's appearance.

Copy link

@aialok aialok left a comment

Choose a reason for hiding this comment

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

@Malayt04
There are some environment variables that are not required. Even if we set them with random values, the local setup still works (for example: Microsoft-related env variables).
It would be helpful to mention which variables are required and which ones are optional.

Also, some users are facing conflicts between the Redis container in Docker and their own local Redis installation.
For example, some contributors already have Redis installed on their system, which causes issues when running Docker.

It would be great to also add steps to set up the project without Docker, like installing PostgreSQL and Redis locally.

cc: @MrgSub

@Malayt04
Copy link
Contributor Author

@aialok only the env vars that are necessary for running the project locally are mentioned in the table. Will surely write about the installation without docker. Thanks for the feedback.


```bash
# Replace [YOUR_USERNAME] with your GitHub username.
git clone https://github.com/[YOUR_USERNAME]/Zero.git
Copy link
Collaborator

Choose a reason for hiding this comment

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

Typo?

Copy link
Collaborator

MrgSub commented Jun 21, 2025

This PR removes a lot of good parts of the current README

@MrgSub MrgSub closed this Jun 21, 2025
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