Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update INSTALLATION.md #2734

Closed

Conversation

Shriya-Chauhan
Copy link

@Shriya-Chauhan Shriya-Chauhan commented Dec 3, 2024

What kind of change does this PR introduce?
Changes in installation.md.

Issue Number:

Fixes #2598

If relevant, did you update the documentation?
Yes ,documentation for installation on linux systems has been updated.

Summary
Contributors were running through multiple errors while building the project using docker. This pull request
suggests changes in the documentation to install and take care of the errors faced by multiple contributers.

Link to the issue

Other information

Have you read the contributing guide?

Yes.

Summary by CodeRabbit

  • Documentation
    • Enhanced clarity and structure of installation instructions for Talawa-API.
    • Expanded summary of installation steps for better overview.
    • Updated Docker installation instructions with prerequisites and troubleshooting tips.
    • Clarified MinIO configuration and setup guidance.
    • Detailed configuration instructions for the .env file.
    • Improved clarity on sample database importing with examples.
    • Minor formatting adjustments for better readability.

Copy link

coderabbitai bot commented Dec 3, 2024

Walkthrough

The changes in this pull request focus on enhancing the INSTALLATION.md file for the Talawa-API. The document has been restructured and updated with clearer instructions, additional details, and improved formatting. Key updates include expanded installation steps, detailed Docker and MinIO configuration instructions, and clarified sample database importing procedures, all aimed at improving user comprehension and ease of setup.

Changes

Files Change Summary
INSTALLATION.md - Enhanced content clarity and structure
- Expanded installation steps summary
- Updated Docker installation instructions with prerequisites and troubleshooting tips
- Detailed MinIO configuration instructions
- Clarified configuration section for .env file setup
- Improved sample database importing section with examples
- Minor formatting adjustments throughout the document

Assessment against linked issues

Objective Addressed Explanation
Setup of Talawa-API in local machine using Docker is giving error regarding "PWD" variable not set correctly (#2598)

Possibly related issues

Possibly related PRs

  • Devcontainer #2429: This PR introduces a new section for "Installation Using Devpod" in INSTALLATION.md, which is related to the overall enhancements made to the installation instructions in the main PR.
  • updated google recaptcha image in installation.md #2608: This PR updates the Google reCAPTCHA image in INSTALLATION.md, which is part of the broader restructuring and enhancement of the installation instructions mentioned in the main PR.
  • Using nodemon to get rid of the experimental warning #2715: This PR includes updates to INSTALLATION.md that enhance the installation instructions, particularly regarding Docker and MinIO, aligning with the content enhancements made in the main PR.

Suggested labels

no-pr-activity

Suggested reviewers

  • SiddheshKukade
  • palisadoes

Poem

In the garden of code, we hop and play,
With clearer paths to guide the way.
Docker and MinIO now shine bright,
Installation made easy, what a delight! 🐇✨
Follow the steps, don't be shy,
Set up Talawa-API, oh my, oh my!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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

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

github-actions bot commented Dec 3, 2024

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

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

🧹 Outside diff range and nitpick comments (2)
INSTALLATION.md (2)

Line range hint 333-355: LGTM! The Docker setup instructions address the PWD variable issue.

The added note about PWD=. requirement and port conflict resolution steps directly address the issues reported in #2598. This will help users avoid common setup problems.

Consider adding a brief explanation of why the PWD=. setting is required, to help users understand its importance. For example:

-`Note`: Make sure `PWD=.` is there in `.env` file.
+`Note`: Make sure `PWD=.` is set in your `.env` file. This environment variable is required for proper container path mapping in Docker Compose.
🧰 Tools
🪛 LanguageTool

[style] ~352-~352: Consider shortening or rephrasing this to strengthen your wording.
Context: ... development environment, where you can make changes to the code, and the server will automatic...

(MAKE_CHANGES)


[uncategorized] ~355-~355: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...e ports mentioned in the error are free (eg. Ports- 80, 0, 4000). Refer `sudo lsof ...

(E_G)


[uncategorized] ~355-~355: Possible missing comma found.
Context: ...T}. To kill the process running on the port use kill {PID}`. 2. Accessing the Deve...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 Markdownlint (0.35.0)

358-358: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


201-201: Fix minor grammatical and formatting issues.

There are a few minor issues to address:

  1. Line 201: Add a hyphen in "open-source contribution"
  2. Line 355: Use "e.g." instead of "eg."
  3. Line 355: Add a comma before "use"

Apply these changes:

-Basic `git` knowledge is required for open source contribution
+Basic `git` knowledge is required for open-source contribution

-(eg. Ports- 80, 0, 4000)
+(e.g., Ports- 80, 0, 4000)

-To kill the process running on the port use
+To kill the process running on the port, use

Also applies to: 355-355

🧰 Tools
🪛 LanguageTool

[uncategorized] ~201-~201: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: .... Basic git knowledge is required for open source contribution so make sure you're comfor...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~201-~201: Possible missing comma found.
Context: ...` knowledge is required for open source contribution so make sure you're comfortable with it...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 43f2bb0 and 3dba79e.

📒 Files selected for processing (1)
  • INSTALLATION.md (3 hunks)
🧰 Additional context used
🪛 LanguageTool
INSTALLATION.md

[uncategorized] ~201-~201: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: .... Basic git knowledge is required for open source contribution so make sure you're comfor...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~201-~201: Possible missing comma found.
Context: ...` knowledge is required for open source contribution so make sure you're comfortable with it...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~333-~333: Loose punctuation mark.
Context: ...oftware development environment. Note: Make sure PWD=. is there in .env fi...

(UNLIKELY_OPENING_PUNCTUATION)


[style] ~352-~352: Consider shortening or rephrasing this to strengthen your wording.
Context: ... development environment, where you can make changes to the code, and the server will automatic...

(MAKE_CHANGES)


[uncategorized] ~355-~355: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...e ports mentioned in the error are free (eg. Ports- 80, 0, 4000). Refer `sudo lsof ...

(E_G)


[uncategorized] ~355-~355: Possible missing comma found.
Context: ...T}. To kill the process running on the port use kill {PID}`. 2. Accessing the Deve...

(AI_HYDRA_LEO_MISSING_COMMA)

@palisadoes
Copy link
Contributor

@Shriya-Chauhan Thanks for the PR, however:

  1. This has to be closed. You are using the main branch when you should be using the latest develop branch.
  2. Also, you will need to update the setup script when Docker is selected to make sure that this parameter is available. You'll need to make sure that tests are written for your work.

@palisadoes palisadoes closed this Dec 3, 2024
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.

setup of talawa-api in local machine using docker is giving error regarding "PWD" variable not set correctly
2 participants