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 add-on docs to match updated Tailscale docs #416

Merged
merged 1 commit into from
Oct 14, 2024

Conversation

lmagyar
Copy link
Contributor

@lmagyar lmagyar commented Oct 14, 2024

Proposed Changes

TS siteto-site networking docs changed, this updates the reference to the steps in it.

Related Issues

related #415

Summary by CodeRabbit

  • Documentation
    • Enhanced clarity and usability of the Tailscale Home Assistant Community Add-on documentation.
    • Updated instructions on snat_subnet_routes for advanced site-to-site networking.
    • Streamlined explanation of userspace_networking for better understanding of client access on the tailnet.
    • Minor formatting and phrasing improvements for better coherence.

Copy link

coderabbitai bot commented Oct 14, 2024

Walkthrough

The documentation for the Tailscale Home Assistant Community Add-on has been revised to improve clarity and usability. Key updates include rephrased instructions, enhanced explanations for snat_subnet_routes, and a streamlined description of userspace_networking. Minor formatting adjustments were also made to enhance coherence throughout the document.

Changes

File Change Summary
tailscale/DOCS.md Rephrased instructions and notes for clarity; updated snat_subnet_routes section; revised userspace_networking explanation; minor formatting adjustments.

Possibly related PRs

  • Make UDP port configurable #390: Updates to the tailscale/DOCS.md documentation regarding the configuration of the UDP port, related to enhancing clarity for networking features.

Suggested reviewers

  • frenck

Poem

🐇 In the land of tails and nets so wide,
We’ve polished our docs, let clarity guide.
With routes and networks, all clear as day,
Hop on to knowledge, come join the play!
A sprinkle of format, a dash of finesse,
Our add-on's now better, we cheer and we bless! 🌟


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.

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

@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 (4)
tailscale/DOCS.md (4)

Line range hint 32-32: Approved: Helpful note about browser compatibility added.

The addition of the note about browser compatibility during the authentication step is valuable for users. It helps prevent potential frustration and provides a clear recommendation.

Consider specifying why some browsers might not work to give users more context. For example:

-   **Note:** Some browsers don't work with this step. It is recommended to
+   **Note:** Some browsers may have issues with the authentication process due to security settings. It is recommended to
🧰 Tools
🪛 LanguageTool

[uncategorized] ~282-~282: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...tworking][tailscale_info_site_to_site] (eg. to traverse multiple networks), you can...

(E_G)


284-285: Approved: Improved guidance for advanced site-to-site networking.

The updated instructions provide clearer guidance for users implementing advanced site-to-site networking configurations. This change aligns well with the PR objective of updating the add-on docs to match the Tailscale documentation.

Consider adding a brief explanation of why a user might need to disable this functionality. For example:

 steps from step 3 on [Site-to-site networking][tailscale_info_site_to_site]. But
-do it only when you really understand why you need this.
+do it only when you really understand why you need this, such as when you require more complex routing scenarios or need to overcome subnet conflicts.

326-327: Approved: Clearer instructions for accessing tailnet clients from local subnet.

The updated instructions provide a more specific reference to the steps required for accessing other clients on the tailnet from the local subnet. This change improves the clarity of the documentation and aligns with the PR objective.

To further improve clarity, consider rephrasing slightly:

-follow steps from step 3 on [Site-to-site
-networking][tailscale_info_site_to_site].
+follow the instructions starting from step 3 in the [Site-to-site
+networking][tailscale_info_site_to_site] guide.

Line range hint 426-426: Approved: New link added for Tailscale app connectors.

The addition of the link for Tailscale app connectors is helpful and supports the new advertise_connector option mentioned earlier in the document.

For consistency with other Tailscale-related links, consider renaming the link:

-[tailscale_info_app_connectors]: https://tailscale.com/kb/1281/app-connectors
+[tailscale_info_app_connectors]: https://tailscale.com/kb/1281/app-connectors/

Note the added trailing slash.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~282-~282: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...tworking][tailscale_info_site_to_site] (eg. to traverse multiple networks), you can...

(E_G)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 838b93e and da3b98f.

📒 Files selected for processing (1)
  • tailscale/DOCS.md (2 hunks)
🧰 Additional context used
🔇 Additional comments (2)
tailscale/DOCS.md (2)

Line range hint 399-399: Approved: Copyright year updated.

The copyright year has been correctly updated to 2024.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~282-~282: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...tworking][tailscale_info_site_to_site] (eg. to traverse multiple networks), you can...

(E_G)


Line range hint 1-431: Overall: Documentation updates improve clarity and align with Tailscale changes.

The changes made to the Tailscale add-on documentation successfully address the PR objective of updating the docs to match the updated Tailscale site-to-site networking documentation. Key improvements include:

  1. Added note about browser compatibility during authentication.
  2. Updated instructions for advanced site-to-site networking configurations.
  3. Clearer guidance on accessing tailnet clients from the local subnet.
  4. Updated copyright year.
  5. Added reference for the new app connectors feature.

These updates enhance the overall quality and accuracy of the documentation, providing users with more precise instructions and references to the latest Tailscale features.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~282-~282: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...tworking][tailscale_info_site_to_site] (eg. to traverse multiple networks), you can...

(E_G)

@frenck frenck added the documentation Solely about the documentation of the project. label Oct 14, 2024
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Thanks, @lmagyar 👍

../Frenck

@frenck frenck merged commit 1fc21f2 into hassio-addons:main Oct 14, 2024
11 of 12 checks passed
@lmagyar lmagyar deleted the pr-update-docs branch October 14, 2024 16:36
@github-actions github-actions bot locked and limited conversation to collaborators Oct 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Solely about the documentation of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants