Add backup docs in index

[perpetrator1]

Proposed Changes

• Added backup and restore docs in index.rst

Merge Checklist

• Tests added/fixed
• Update docs in /docs
• Linting Complete
• Any other necessary step

@ohcnetwork/care-backend-maintainers @ohcnetwork/care-backend-admins

Summary by CodeRabbit

• New Features
  • Expanded documentation to include a section on database backup procedures.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces a minor documentation update by adding a new entry to the table of contents in the docs/index.rst file. This change expands the documentation's structure to include a section about database backup procedures, subtly hinting that perhaps someone finally remembered documentation is, you know, kind of important.

Changes

File	Change Summary
docs/index.rst	Added databases/backup to the toctree, graciously expanding the documentation's coverage

Poem

🗂️ A toctree grows, oh so slight
A backup section comes to light
Documentation's gentle sway
One more path for readers today
Whispers Was this really so hard? 📚✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/index.rst (2)

23-23: Maintain consistent formatting with other entries

I couldn't help but notice that this entry seems to be feeling a bit... lonely down there. Perhaps we could show it some love by moving it up with its documentation friends?

   middleware/configuration
+   databases/backup
   others/configuration
   glossary/configuration
-
-   databases/backup

---

23-25: Remove unnecessary blank lines

Those extra blank lines are giving me separation anxiety. One blank line should be sufficient, just like all the other entries above.

   databases/backup
-
-

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7d3d958 and d61789f.

📒 Files selected for processing (1)

• docs/index.rst (1 hunks)

🔇 Additional comments (1)

docs/index.rst (1)

23-23: Verify the existence of the backup documentation file

While adding entries to the index is delightful, it would be even more delightful if we could actually read the documentation it's pointing to.

Would you like me to help create a template for the docs/databases/backup.rst file? It seems to be missing, and I'd be more than happy to assist with that.