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

Fix paths to files when resetting root password #221

Merged
merged 1 commit into from
Dec 17, 2024
Merged

Conversation

ljm42
Copy link
Member

@ljm42 ljm42 commented Dec 17, 2024

Before Submitting This PR, Please Ensure You Have Completed The Following:

  1. Are internal links to wiki documents using relative file links?
  2. Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)?
  3. Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files?
  4. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  5. Is the build succeeding?

Summary by CodeRabbit

  • Documentation
    • Improved clarity and accuracy of the password reset process for Unraid.
    • Corrected file paths for hashed passwords.
    • Enhanced formatting of user account instructions for better readability.

Copy link
Contributor

coderabbitai bot commented Dec 17, 2024

Walkthrough

The pull request involves updating the Unraid OS manual documentation for password reset procedures. The changes focus on correcting file paths related to password storage and improving formatting in the user instructions. The modifications ensure more accurate guidance for users seeking to reset their root password, with specific attention to the precise locations of shadow and SMB password files.

Changes

File Change Summary
docs/unraid-os/manual/users/reset-password.md - Corrected file paths from boot/config/shadow to /config/shadow
- Corrected file paths from boot/config/smbpasswd to /config/smbpasswd
- Updated arrow symbols from > to in navigation references

Poem

🐰 A Rabbit's Password Reset Rhyme 🔑

In Unraid's realm of config and might,
Paths corrected, now shining bright
From boot to /config, we've found our way
Arrows point true, no more delay!
A password reset, simple and clear


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.

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

🧹 Nitpick comments (1)
docs/unraid-os/manual/users/reset-password.md (1)

Line range hint 24-41: Consider using variables for system paths

To make future path updates easier and ensure consistency, consider introducing documentation variables or constants for commonly referenced system paths. This could be implemented using your documentation framework's features.

Example approach:

Define at the top of the documentation:
{%set CONFIG_DIR = "/config" %}

Then use throughout:
{{CONFIG_DIR}}/shadow
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3c094e7 and 01a0404.

📒 Files selected for processing (1)
  • docs/unraid-os/manual/users/reset-password.md (2 hunks)
🔇 Additional comments (2)
docs/unraid-os/manual/users/reset-password.md (2)

41-41: LGTM! Path is now consistent

The updated path in the Advanced method matches the Basic method, maintaining consistency throughout the document.


24-25: Verify path consistency across documentation

The updated paths look correct, but let's ensure they are consistent with other documentation references.

Comment on lines +30 to +31
<li>
<i>(Optional)</i> If you have any user accounts configured in <b><i>Users Shares Access</i></b> (or <b><i>Settings Users Shares Access</i></b>), select each user and enter a new password. Be sure to select <b>Change</b> and not <b>Done</b> after this.
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 17, 2024

Choose a reason for hiding this comment

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

💡 Codebase verification

Inconsistent arrow symbols need standardization

The documentation currently uses mixed arrow styles:

  • "→" (Unicode arrow) in reset-password.md
  • ">" (greater than) in manage-user.md and create-user.md
  • "->" (hyphen + greater than) in release-notes/6.9.0.md

This inconsistency should be addressed by standardizing on one style across all documentation.

🔗 Analysis chain

Verify arrow symbol consistency

The change from ">" to "→" improves readability. Let's verify this matches the style used in other documentation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for different arrow styles in navigation paths
# to ensure consistency across documentation

echo "Checking for arrow symbols in navigation paths:"
rg -i "users.*>.*shares|settings.*>.*users" --type md

Length of output: 925

Copy link
Member Author

Choose a reason for hiding this comment

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

This rg command looks incredibly powerful, would be a good way to find these types of consistency issues across the docs site

Copy link
Contributor

Choose a reason for hiding this comment

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

@ljm42, I'm glad you find the rg command useful! It's indeed a powerful way to uncover consistency issues across the documentation.

(^・ω・^ )

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-221.d1o5s833kbd339.amplifyapp.com

@ljm42 ljm42 merged commit bf85b26 into main Dec 17, 2024
3 checks passed
@ljm42 ljm42 deleted the fix-reset-password branch December 17, 2024 20:57
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.

1 participant