cozystack icon indicating copy to clipboard operation
cozystack copied to clipboard

[docs] Tenants cannot have dashes in the names

Open NickVolynkin opened this issue 6 months ago • 1 comments

Summary by CodeRabbit

  • Documentation
    • Improved and reorganized tenant documentation for better clarity.
    • Added explicit rules for tenant naming, including restrictions on dashes and required alphanumeric names.
    • Clarified how tenant domains are structured and inherited.
    • Expanded explanations on nesting tenants and sharing parent services, with updated examples and clearer formatting.

NickVolynkin avatar May 23 '25 11:05 NickVolynkin

Walkthrough

The tenant documentation was reorganized and expanded for clarity. New sections were added to specify tenant naming rules, particularly disallowing dashes. Existing sections were renamed and reformatted to clarify domain inheritance, tenant nesting, and service reuse, with additional examples and explanations provided.

Changes

File(s) Change Summary
packages/apps/tenant/README.md Reorganized and expanded documentation: added tenant naming rules, clarified domain inheritance, nesting, and service reuse, updated examples and formatting.

Possibly related issues

  • cozystack/cozystack#971: This PR updates tenant documentation to explicitly disallow dashes in tenant names, directly addressing the issue where tenant creation with dashes causes deployment to hang.

Poem

In the land of tenants, rules now shine bright,
No dashes allowed—names kept light!
Domains inherit, services share,
Nesting explained with extra care.
With clearer docs, confusion takes flight—
Hopping forward, everything’s right!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

coderabbitai[bot] avatar May 23 '25 11:05 coderabbitai[bot]