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

updated java installation prerequisite #321

Conversation

NyashaMuusha
Copy link
Collaborator

@NyashaMuusha NyashaMuusha commented Sep 11, 2024

Summary by CodeRabbit

  • Documentation
    • Revised the standalone installation guide to specify the required Java version as 21.0.3-tem.
    • Added instructions for non-root users to correctly set the Java directory.
    • Included a note for server installations to manually set the SERVER_IP environment variable before executing the installation script.

@rcrichton
Copy link
Member

Copy link
Contributor

coderabbitai bot commented Sep 11, 2024

Walkthrough

The documentation for the standalone installation process has been updated to specify the required Java version as 21.0.3-tem, replacing the previous version. New instructions have been added for users with non-root accounts to correctly set the Java directory, along with a note for server installations to manually set the SERVER_IP environment variable before executing the installation script.

Changes

File Path Change Summary
documentation/installation/standalone-installation.md Updated required Java version to 21.0.3-tem; added instruction to source Java candidate from home directory; added note for setting SERVER_IP environment variable.

Possibly related PRs

Poem

🐇 In the garden of code, we hop with glee,
New paths for the users, as clear as can be.
With Java now sourced from a cozy home,
Every non-root rabbit can freely roam!
Installation made simple, a joyful delight,
Let's celebrate changes that shine oh so bright! 🌟


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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

Outside diff range and nitpick comments (1)
documentation/installation/standalone-installation.md (1)

33-35: Specify the language for the code block.

For better formatting and syntax highlighting, please specify the language for the code block.

Apply this diff:

-```
+```bash
 source "/home/${USER}/.sdkman/candidates/java/current"

<details>
<summary>Tools</summary>

<details>
<summary>Markdownlint</summary><blockquote>

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

(MD040, fenced-code-language)

</blockquote></details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**

<details>
<summary>Commits</summary>

Files that changed from the base of the PR and between c8028dcfde9d94fe6a5a3fdd8bfbbcb719ae681f and 0eafe7f52ea76c4c25f9026dbf8434453b12043f.

</details>


<details>
<summary>Files selected for processing (1)</summary>

* documentation/installation/standalone-installation.md (1 hunks)

</details>










<details>
<summary>Additional context used</summary>

<details>
<summary>Markdownlint</summary><blockquote>

<details>
<summary>documentation/installation/standalone-installation.md</summary><blockquote>

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

(MD040, fenced-code-language)

</blockquote></details>

</blockquote></details>

</details>
<details>
<summary>Additional comments not posted (1)</summary><blockquote>

<details>
<summary>documentation/installation/standalone-installation.md (1)</summary><blockquote>

`31-37`: **LGTM!**

The added instruction for non-root users to source Java from their home directory is clear and helpful.

<details>
<summary>Tools</summary>

<details>
<summary>Markdownlint</summary><blockquote>

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

(MD040, fenced-code-language)

</blockquote></details>

</details>

</blockquote></details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

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

Outside diff range and nitpick comments (3)
documentation/installation/standalone-installation.md (3)

41-45: Use a proper heading instead of emphasis.

The added note with instructions for non-root users is a valuable addition to improve the clarity of the installation process. However, please use a proper Markdown heading (e.g., ###) instead of emphasis for the note to adhere to Markdown best practices and address the static analysis hint.

-**Note: when installing with a non-root user set java directory**
+### Note: when installing with a non-root user set java directory
Tools
Markdownlint

41-41: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


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

(MD040, fenced-code-language)


178-181: Use a proper heading instead of emphasis.

The added note with instructions for server installations to set the SERVER_IP environment variable is a valuable addition to improve the clarity of the installation process. However, please use a proper Markdown heading (e.g., ###) instead of emphasis for the note to adhere to Markdown best practices and address the static analysis hint.

-**Note: for server installations, manually set SERVER_IP for environment variable before executing the script**
+### Note: for server installations, manually set SERVER_IP for environment variable before executing the script
Tools
Markdownlint

178-178: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


42-42: Remove the empty code block or specify a language.

The empty code block should either be removed or have a language specified (e.g., bash) if it's intended to showcase a command or code snippet. Specifying the language for code blocks is a Markdown best practice that enables syntax highlighting and improves readability.

Tools
Markdownlint

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

(MD040, fenced-code-language)

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0eafe7f and 7480eac.

Files selected for processing (1)
  • documentation/installation/standalone-installation.md (3 hunks)
Additional context used
Markdownlint
documentation/installation/standalone-installation.md

41-41: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


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

(MD040, fenced-code-language)


178-178: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

Additional comments not posted (1)
documentation/installation/standalone-installation.md (1)

38-38: LGTM!

The Java version has been correctly updated to 21.0.3-tem as per the PR objective.

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

Outside diff range and nitpick comments (2)
documentation/installation/standalone-installation.md (2)

41-45: Improve the note formatting.

The addition of the note with instructions for non-root users to set the Java directory is helpful and enhances clarity. The code block correctly sources the Java directory path using the user's home directory.

However, please consider converting the emphasized note text to a proper heading for better document structure:

-**Note: when installing with a non-root user set java directory**
+#### Note: Set Java directory when installing with a non-root user
Tools
Markdownlint

41-41: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


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

(MD040, fenced-code-language)


178-181: Improve the note formatting.

The addition of the note advising users to manually set the SERVER_IP environment variable for server installations is helpful and aligns with the PR objective. The code block provides a clear example of how to set the REACT_APP_JEMPI_BASE_API_HOST environment variable using the SERVER_IP.

However, please consider converting the emphasized note text to a proper heading for better document structure:

-**Note: for server installations, manually set SERVER_IP for environment variable before executing the script**
+#### Note: Set `SERVER_IP` environment variable for server installations
Tools
LanguageTool

[uncategorized] ~178-~178: The preposition ‘as’ seems more likely in this position.
Context: ...r installations, manually set SERVER_IP for environment variable before executing t...

(AI_HYDRA_LEO_REPLACE_FOR_AS)

Markdownlint

178-178: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7480eac and 98ff0f9.

Files selected for processing (1)
  • documentation/installation/standalone-installation.md (3 hunks)
Additional context used
Markdownlint
documentation/installation/standalone-installation.md

41-41: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


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

(MD040, fenced-code-language)


178-178: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

LanguageTool
documentation/installation/standalone-installation.md

[uncategorized] ~178-~178: The preposition ‘as’ seems more likely in this position.
Context: ...r installations, manually set SERVER_IP for environment variable before executing t...

(AI_HYDRA_LEO_REPLACE_FOR_AS)

Additional comments not posted (1)
documentation/installation/standalone-installation.md (1)

38-38: LGTM!

The Java installation command has been correctly updated to use version 21.0.3-tem, aligning with the PR objective.

@MatthewErispe MatthewErispe merged commit a4af960 into dev Sep 12, 2024
6 checks passed
@MatthewErispe MatthewErispe deleted the CU-86c089af1_Documentation-Update-Installation-Java-Prerequisites branch September 12, 2024 12:59
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.

3 participants