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

Updating installation.md #2865

Conversation

MohitMaulekhi
Copy link

@MohitMaulekhi MohitMaulekhi commented Jan 18, 2025

What kind of change does this PR introduce?

This PR updates the installation.md file to assist new open-source contributors in setting up the Talawa-API environment.

Issue Number:

Fixes #2857

Summary

This PR includes detailed instructions for setting up the Talawa-API environment, including prerequisite installations, cloning the repository, setting up environment variables, and starting the server. The goal is to make it easier for new contributors to get started.

Does this PR introduce a breaking change?

no

Checklist

  • Updated installation.md with detailed setup instructions

  • Verified that the setup instructions are clear and easy to follow

Have you read the contributing guide?

yes

Summary by CodeRabbit

  • Documentation
    • Enhanced installation guide with a structured Table of Contents
    • Added detailed setup instructions for development and production environments
    • Expanded sections on software prerequisites and installation steps
    • Included recommendations for Linux-based development environments, particularly for Docker usage
    • Provided step-by-step guides for installing essential development tools
    • Added commands for running development and production servers, and accessing PostgreSQL and MinIO
    • Expanded API usage section with detailed examples for signing in and creating organizations

Copy link

coderabbitai bot commented Jan 18, 2025

Walkthrough

The pull request updates the INSTALLATION.md file to provide comprehensive, detailed installation instructions for the project. The document now includes a structured Table of Contents with clear sections for development and production environments. It offers step-by-step guidance for installing prerequisites like Git, Docker, Visual Studio Code, Node.js, and TypeScript. The instructions cover environment setup, configuration, and include specific commands for running the server, accessing databases, and testing API endpoints.

Changes

File Change Summary
INSTALLATION.md - Added comprehensive Table of Contents
- Expanded "Our recommendations" section
- Detailed prerequisites and installation steps
- Added instructions for Git, Docker, VS Code, Node.js, TypeScript
- Included environment file and variable configuration
- Added server running and debugging commands
- Expanded API usage section with detailed examples

Assessment against linked issues

Objective Addressed Explanation
Update INSTALLATION.md comprehensively [#2857]
Use CLI commands
Show ways to test installation (CURL, iGraphQL) Partial coverage of testing methods
Limit use of imagery

Possibly related PRs

  • Updated documentation to include production setup #2798: This PR also focuses on enhancing the INSTALLATION.md file, specifically improving the organization and clarity of installation instructions for both development and production environments, which aligns closely with the changes made in the main PR.

Suggested reviewers

  • palisadoes

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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

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

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b308fb4 and 731dc5c.

⛔ Files ignored due to path filters (2)
  • public/markdown/images/install1.png is excluded by !**/*.png
  • public/markdown/images/install2.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • INSTALLATION.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
INSTALLATION.md

[typographical] ~33-~33: Usually, there’s no comma before “if”.
Context: ...uction server after closing the terminal, if docker containers are running.](#comman...

(IF_NO_COMMA)


[uncategorized] ~54-~54: This expression is usually spelled with a hyphen.
Context: ...ironment setup ## Our recommendations Linux based distributions are simply the best platf...

(BASED_HYPHEN)


[style] ~57-~57: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ... linux, on non-linux platforms they can only be used by emulating linux where they a...

(ONLY_EXCLUSIVELY_STYLE)


[grammar] ~57-~57: Consider using either the past participle “run” or the present participle “running” here.
Context: ... used by emulating linux where they are ran inside linux based virtual machines. So...

(BEEN_PART_AGREEMENT)


[grammar] ~59-~59: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...enalties and limitations don't apply to windows subsystem for linux. So, if you plan on...

(A_WINDOWS)


[style] ~59-~59: Try using a more formal synonym here to elevate your writing.
Context: ...windows subsystem for linux. So, if you plan on using windows, at the very least make use of ...

(PLAN_ON_INTEND)


[grammar] ~59-~59: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ... windows, at the very least make use of windows subsystem for linux. ## Prerequisites ...

(A_WINDOWS)


[typographical] ~74-~74: It appears that a comma is missing.
Context: ...iners 7. Typescript 8. Node.js In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)


[uncategorized] ~80-~80: 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] ~89-~89: This expression is usually spelled with a hyphen.
Context: ... Settings. - Check Use the WSL 2 based engine. - Verify your distribution...

(BASED_HYPHEN)


[uncategorized] ~100-~100: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r $USER` - Sign out and back in again so your changes take effect. ### Install ...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~114-~114: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ote.remote-containers ``` 3. It is very important that you go through [this](https://code...

(EN_WEAK_ADJECTIVE)


[grammar] ~120-~120: The operating system from Apple is written “macOS”.
Context: ...node.jspackages in Windows, Linux and MacOS. 1. For Windows: 1. first install...

(MAC_OS)


[duplication] ~134-~134: Possible typo: you repeated a word.
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ensure...

(ENGLISH_WORD_REPEAT_RULE)


[grammar] ~137-~137: The operating system from Apple is written “macOS”.
Context: ...t version of node.js 2. For Linux and MacOS, use the terminal window. 1. install...

(MAC_OS)


[grammar] ~141-~141: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... the respective recommended commands to setup your node environment 3. This wil...

(NOUN_VERB_CONFUSION)


[grammar] ~191-~191: The word “setup” is a noun. The verb is spelled with a space.
Context: ...avigate to the folder where you want to setup the repository. 2. Open a cmd (Window...

(NOUN_VERB_CONFUSION)


[grammar] ~192-~192: The operating system from Apple is written “macOS”.
Context: ...cmd (Windows) or terminal (Linux or MacOS) session in this folder. 1. An easy ...

(MAC_OS)


[uncategorized] ~194-~194: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e option based on your OS. 3. For Our Open Source Contributor Software Developers: ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~220-~220: Consider using the more formal “until”.
Context: ...take a few minutes to complete. 4. Wait till the process is complete and you see por...

(TILL)


[uncategorized] ~220-~220: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...te. 4. Wait till the process is complete and you see ports being forwarded in the te...

(COMMA_COMPOUND_SENTENCE)


[duplication] ~255-~255: Possible typo: you repeated a word.
Context: ...ent of talawa api: 1. Git 2. Github 3. Docker 4. Docker compose In this section we'll explain ...

(ENGLISH_WORD_REPEAT_RULE)


[typographical] ~258-~258: It appears that a comma is missing.
Context: ...ub 3. Docker 4. Docker compose In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)


[uncategorized] ~264-~264: 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] ~273-~273: This expression is usually spelled with a hyphen.
Context: ... Settings. - Check Use the WSL 2 based engine. - Verify your distribution...

(BASED_HYPHEN)


[uncategorized] ~284-~284: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r $USER` - Sign out and back in again so your changes take effect. ## Setup usi...

(COMMA_COMPOUND_SENTENCE_2)


[grammar] ~314-~314: The operating system from Apple is written “macOS”.
Context: ...s) or terminal (terminal for Linux or MacOS) session in this folder. - You can u...

(MAC_OS)


[typographical] ~367-~367: Usually, there’s no comma before “if”.
Context: ...uction server after closing the terminal, if docker containers are running. - for n...

(IF_NO_COMMA)


[uncategorized] ~391-~391: Did you mean: “By default,”?
Context: ...Ls for coding and troubleshooting : 1. By default talawa-api runs on port 4000 on your ...

(BY_DEFAULT_COMMA)

🪛 Markdownlint (0.37.0)
INSTALLATION.md

47-47: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


51-51: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


247-247: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


383-383: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


448-448: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


495-495: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


507-507: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


519-519: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


84-84: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


92-92: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


231-231: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


268-268: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


276-276: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


367-367: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


111-111: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


113-113: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


206-206: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


210-210: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


317-317: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


321-321: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


333-333: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


358-358: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


360-360: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


404-404: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


451-451: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


453-453: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


498-498: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


500-500: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


510-510: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


512-512: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


605-605: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)


123-123: null
Bare URL used

(MD034, no-bare-urls)


525-525: null
Bare URL used

(MD034, no-bare-urls)


569-569: null
Bare URL used

(MD034, no-bare-urls)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


166-166: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)


296-296: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)


343-343: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

⏰ Context from checks skipped due to timeout of 90000ms (2)

INSTALLATION.md Show resolved Hide resolved
INSTALLATION.md Show resolved Hide resolved
INSTALLATION.md Show resolved Hide resolved
INSTALLATION.md Show resolved Hide resolved
INSTALLATION.md Show resolved Hide resolved
@MohitMaulekhi
Copy link
Author

@coderabbitai full review

Copy link

coderabbitai bot commented Jan 18, 2025

✅ Actions performed

Full review triggered.

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

🔭 Outside diff range comments (1)
INSTALLATION.md (1)

Line range hint 1-605: Address pipeline failure for sensitive file changes.

The pipeline indicates that this file is considered sensitive and requires special handling. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.

Please:

  1. Add the 'ignore-sensitive-files-pr' label to this PR
  2. Review the changes thoroughly for any security implications
  3. Ensure all sensitive information is replaced with placeholders
🧰 Tools
🪛 LanguageTool

[typographical] ~74-~74: It appears that a comma is missing.
Context: ...iners 7. Typescript 8. Node.js In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)


[uncategorized] ~80-~80: 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] ~89-~89: This expression is usually spelled with a hyphen.
Context: ... Settings. - Check Use the WSL 2 based engine. - Verify your distribution...

(BASED_HYPHEN)


[uncategorized] ~100-~100: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r $USER` - Sign out and back in again so your changes take effect. ### Install ...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~114-~114: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ote.remote-containers ``` 3. It is very important that you go through [this](https://code...

(EN_WEAK_ADJECTIVE)


[grammar] ~120-~120: The operating system from Apple is written “macOS”.
Context: ...node.jspackages in Windows, Linux and MacOS. 1. For Windows: 1. first install...

(MAC_OS)


[duplication] ~134-~134: Possible typo: you repeated a word.
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ensure...

(ENGLISH_WORD_REPEAT_RULE)


[grammar] ~137-~137: The operating system from Apple is written “macOS”.
Context: ...t version of node.js 2. For Linux and MacOS, use the terminal window. 1. install...

(MAC_OS)


[grammar] ~141-~141: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... the respective recommended commands to setup your node environment 3. This wil...

(NOUN_VERB_CONFUSION)


[grammar] ~191-~191: The word “setup” is a noun. The verb is spelled with a space.
Context: ...avigate to the folder where you want to setup the repository. 2. Open a cmd (Window...

(NOUN_VERB_CONFUSION)


[grammar] ~192-~192: The operating system from Apple is written “macOS”.
Context: ...cmd (Windows) or terminal (Linux or MacOS) session in this folder. 1. An easy ...

(MAC_OS)


[uncategorized] ~194-~194: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e option based on your OS. 3. For Our Open Source Contributor Software Developers: ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~220-~220: Consider using the more formal “until”.
Context: ...take a few minutes to complete. 4. Wait till the process is complete and you see por...

(TILL)


[uncategorized] ~220-~220: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...te. 4. Wait till the process is complete and you see ports being forwarded in the te...

(COMMA_COMPOUND_SENTENCE)


[duplication] ~255-~255: Possible typo: you repeated a word.
Context: ...ent of talawa api: 1. Git 2. Github 3. Docker 4. Docker compose In this section we'll explain ...

(ENGLISH_WORD_REPEAT_RULE)


[typographical] ~258-~258: It appears that a comma is missing.
Context: ...ub 3. Docker 4. Docker compose In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)


[uncategorized] ~264-~264: 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] ~273-~273: This expression is usually spelled with a hyphen.
Context: ... Settings. - Check Use the WSL 2 based engine. - Verify your distribution...

(BASED_HYPHEN)


[uncategorized] ~284-~284: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r $USER` - Sign out and back in again so your changes take effect. ## Setup usi...

(COMMA_COMPOUND_SENTENCE_2)


[grammar] ~314-~314: The operating system from Apple is written “macOS”.
Context: ...s) or terminal (terminal for Linux or MacOS) session in this folder. - You can u...

(MAC_OS)


[typographical] ~367-~367: Usually, there’s no comma before “if”.
Context: ...uction server after closing the terminal, if docker containers are running. - for n...

(IF_NO_COMMA)


[uncategorized] ~391-~391: Did you mean: “By default,”?
Context: ...Ls for coding and troubleshooting : 1. By default talawa-api runs on port 4000 on your ...

(BY_DEFAULT_COMMA)

🪛 Markdownlint (0.37.0)

247-247: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


383-383: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


448-448: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


495-495: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


507-507: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


519-519: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


84-84: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


92-92: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


231-231: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


268-268: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


276-276: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


367-367: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


111-111: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


113-113: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


206-206: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


210-210: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


317-317: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


321-321: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


333-333: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


358-358: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


360-360: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


404-404: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


451-451: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


453-453: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


498-498: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


500-500: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


510-510: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


512-512: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


605-605: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)


123-123: null
Bare URL used

(MD034, no-bare-urls)


525-525: null
Bare URL used

(MD034, no-bare-urls)


569-569: null
Bare URL used

(MD034, no-bare-urls)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


166-166: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)


296-296: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)


343-343: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

🪛 GitHub Actions: Pull request workflow

[error] Unauthorized changes detected in sensitive file. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b308fb4 and 731dc5c.

⛔ Files ignored due to path filters (2)
  • public/markdown/images/install1.png is excluded by !**/*.png
  • public/markdown/images/install2.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • INSTALLATION.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
INSTALLATION.md

[typographical] ~33-~33: Usually, there’s no comma before “if”.
Context: ...uction server after closing the terminal, if docker containers are running.](#comman...

(IF_NO_COMMA)


[uncategorized] ~54-~54: This expression is usually spelled with a hyphen.
Context: ...ironment setup ## Our recommendations Linux based distributions are simply the best platf...

(BASED_HYPHEN)


[style] ~57-~57: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ... linux, on non-linux platforms they can only be used by emulating linux where they a...

(ONLY_EXCLUSIVELY_STYLE)


[grammar] ~57-~57: Consider using either the past participle “run” or the present participle “running” here.
Context: ... used by emulating linux where they are ran inside linux based virtual machines. So...

(BEEN_PART_AGREEMENT)


[grammar] ~59-~59: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...enalties and limitations don't apply to windows subsystem for linux. So, if you plan on...

(A_WINDOWS)


[style] ~59-~59: Try using a more formal synonym here to elevate your writing.
Context: ...windows subsystem for linux. So, if you plan on using windows, at the very least make use of ...

(PLAN_ON_INTEND)


[grammar] ~59-~59: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ... windows, at the very least make use of windows subsystem for linux. ## Prerequisites ...

(A_WINDOWS)


[typographical] ~74-~74: It appears that a comma is missing.
Context: ...iners 7. Typescript 8. Node.js In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)


[uncategorized] ~80-~80: 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] ~89-~89: This expression is usually spelled with a hyphen.
Context: ... Settings. - Check Use the WSL 2 based engine. - Verify your distribution...

(BASED_HYPHEN)


[uncategorized] ~100-~100: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r $USER` - Sign out and back in again so your changes take effect. ### Install ...

(COMMA_COMPOUND_SENTENCE_2)


[style] ~114-~114: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ote.remote-containers ``` 3. It is very important that you go through [this](https://code...

(EN_WEAK_ADJECTIVE)


[grammar] ~120-~120: The operating system from Apple is written “macOS”.
Context: ...node.jspackages in Windows, Linux and MacOS. 1. For Windows: 1. first install...

(MAC_OS)


[duplication] ~134-~134: Possible typo: you repeated a word.
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ensure...

(ENGLISH_WORD_REPEAT_RULE)


[grammar] ~137-~137: The operating system from Apple is written “macOS”.
Context: ...t version of node.js 2. For Linux and MacOS, use the terminal window. 1. install...

(MAC_OS)


[grammar] ~141-~141: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... the respective recommended commands to setup your node environment 3. This wil...

(NOUN_VERB_CONFUSION)


[grammar] ~191-~191: The word “setup” is a noun. The verb is spelled with a space.
Context: ...avigate to the folder where you want to setup the repository. 2. Open a cmd (Window...

(NOUN_VERB_CONFUSION)


[grammar] ~192-~192: The operating system from Apple is written “macOS”.
Context: ...cmd (Windows) or terminal (Linux or MacOS) session in this folder. 1. An easy ...

(MAC_OS)


[uncategorized] ~194-~194: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e option based on your OS. 3. For Our Open Source Contributor Software Developers: ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~220-~220: Consider using the more formal “until”.
Context: ...take a few minutes to complete. 4. Wait till the process is complete and you see por...

(TILL)


[uncategorized] ~220-~220: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...te. 4. Wait till the process is complete and you see ports being forwarded in the te...

(COMMA_COMPOUND_SENTENCE)


[duplication] ~255-~255: Possible typo: you repeated a word.
Context: ...ent of talawa api: 1. Git 2. Github 3. Docker 4. Docker compose In this section we'll explain ...

(ENGLISH_WORD_REPEAT_RULE)


[typographical] ~258-~258: It appears that a comma is missing.
Context: ...ub 3. Docker 4. Docker compose In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)


[uncategorized] ~264-~264: 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] ~273-~273: This expression is usually spelled with a hyphen.
Context: ... Settings. - Check Use the WSL 2 based engine. - Verify your distribution...

(BASED_HYPHEN)


[uncategorized] ~284-~284: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r $USER` - Sign out and back in again so your changes take effect. ## Setup usi...

(COMMA_COMPOUND_SENTENCE_2)


[grammar] ~314-~314: The operating system from Apple is written “macOS”.
Context: ...s) or terminal (terminal for Linux or MacOS) session in this folder. - You can u...

(MAC_OS)


[typographical] ~367-~367: Usually, there’s no comma before “if”.
Context: ...uction server after closing the terminal, if docker containers are running. - for n...

(IF_NO_COMMA)


[uncategorized] ~391-~391: Did you mean: “By default,”?
Context: ...Ls for coding and troubleshooting : 1. By default talawa-api runs on port 4000 on your ...

(BY_DEFAULT_COMMA)

🪛 Markdownlint (0.37.0)
INSTALLATION.md

47-47: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


51-51: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


247-247: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


383-383: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


448-448: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


495-495: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


507-507: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


519-519: null
Multiple top-level headings in the same document

(MD025, single-title, single-h1)


84-84: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


92-92: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


231-231: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


268-268: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


276-276: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


367-367: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


111-111: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


113-113: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


206-206: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


210-210: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


317-317: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


321-321: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


333-333: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


358-358: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


360-360: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


404-404: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


451-451: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


453-453: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


498-498: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


500-500: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


510-510: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


512-512: null
Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


605-605: null
Lists should be surrounded by blank lines

(MD032, blanks-around-lists)


123-123: null
Bare URL used

(MD034, no-bare-urls)


525-525: null
Bare URL used

(MD034, no-bare-urls)


569-569: null
Bare URL used

(MD034, no-bare-urls)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


166-166: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)


296-296: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)


343-343: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

🪛 GitHub Actions: Pull request workflow
INSTALLATION.md

[error] Unauthorized changes detected in sensitive file. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.

🔇 Additional comments (4)
INSTALLATION.md (4)

343-346: ⚠️ Potential issue

Use secure placeholder values for sensitive configuration.

The example values for environment variables should use clear placeholder text to prevent accidental use in production.

Apply this diff to use secure placeholders:

-    1. **CADDY_TALAWA_API_DOMAIN_NAME** (e.g., `localhost`)
-    2. **CADDY_TALAWA_API_EMAIL** (e.g., `[email protected]`)
-    3. **API_POSTGRES_PASSWORD** (e.g., `password`)
-    4. **API_BASE_URL** (e.g., `https://localhost`)
+    1. **CADDY_TALAWA_API_DOMAIN_NAME** (e.g., `<your-domain>`)
+    2. **CADDY_TALAWA_API_EMAIL** (e.g., `<your-admin-email>`)
+    3. **API_POSTGRES_PASSWORD** (e.g., `<strong-unique-password>`)
+    4. **API_BASE_URL** (e.g., `<your-api-url>`)

Likely invalid or redundant comment.

🧰 Tools
🪛 Markdownlint (0.37.0)

343-343: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

🪛 GitHub Actions: Pull request workflow

[error] Unauthorized changes detected in sensitive file. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.


351-353: ⚠️ Potential issue

Enhance security of JWT secret generation.

The current command using base64 encoding might not provide sufficient entropy for a secure JWT secret.

Apply this diff to use a more secure method:

-openssl rand -base64 64
+openssl rand -hex 32

Likely invalid or redundant comment.

🧰 Tools
🪛 GitHub Actions: Pull request workflow

[error] Unauthorized changes detected in sensitive file. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.


533-541: ⚠️ Potential issue

Remove sensitive information from API examples.

The API examples should not expose default credentials.

Apply this diff to use placeholders:

-      "emailAddress": "[email protected]",
-      "password": "password"
+      "emailAddress": "<your-email>",
+      "password": "<your-password>"

Likely invalid or redundant comment.

🧰 Tools
🪛 GitHub Actions: Pull request workflow

[error] Unauthorized changes detected in sensitive file. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.


1-46: 🧹 Nitpick (assertive)

Improve document structure and formatting.

The document structure needs the following improvements:

  1. Use a single top-level heading (#) for the document title
  2. Use subheadings (##, ###, etc.) for all other sections
  3. Add language specifications to code blocks
  4. Ensure consistent spacing around code blocks

Apply this diff to fix the document structure:

-# Table of Contents
+# Talawa-API Installation Guide
+
+## Table of Contents

Likely invalid or redundant comment.

🧰 Tools
🪛 LanguageTool

[typographical] ~33-~33: Usually, there’s no comma before “if”.
Context: ...uction server after closing the terminal, if docker containers are running.](#comman...

(IF_NO_COMMA)

🪛 GitHub Actions: Pull request workflow

[error] Unauthorized changes detected in sensitive file. Changes to this file require the 'ignore-sensitive-files-pr' label to proceed.

INSTALLATION.md Show resolved Hide resolved
@palisadoes palisadoes added the ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files label Jan 18, 2025
@palisadoes palisadoes requested a review from xoldd January 18, 2025 12:56
@xoldd
Copy link
Contributor

xoldd commented Jan 20, 2025

@MohitMaulekhi you just copy pasted the documentation from develop branch. You have to write it that way it was shown in the videos. All that fluff about installing node.js and typescript isn't what's shown in the video. It's all automated using docker, docker compose and devcontainers, so the developers don't need to bother with that.

@palisadoes
Copy link
Contributor

Closing. This is a cut and paste of the document in the develop branch. There is too much extraneous information that will lead people astray. This is a very important document and needs to be taken seriously. I'm going to have to assign this to someone else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants