feat: allow custom path for all runtipi folders

[nicotsx]

Summary by CodeRabbit

• New Features

  • Added display of RUNTIPI_APP_DATA_PATH in debug information to enhance user awareness of data management.

• Refactor

  • Updated environment handling to use RUNTIPI_ prefixed variables, improving configuration consistency.

• Documentation

  • Updated settings schema to include app_data_path, phasing out storage_path for clarity in data management.

[coderabbitai]

Warning

Rate Limit Exceeded

@meienberger has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 52 minutes and 29 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 975cfc1 and bbaa090.

Walkthrough

The updates focus on standardizing environment variable usage across the project by replacing hardcoded paths with variables prefixed by RUNTIPI_. This change enhances configuration flexibility and aligns with best practices for environment management.

Changes

File Path	Change Summary
src/assets/.../docker-compose.yml	Updated volume paths to utilize RUNTIPI_ prefixed environment variables.
src/commands/debug.rs	Display RUNTIPI_APP_DATA_PATH in debug output, replacing STORAGE_PATH.
src/utils/env.rs	Modified generate_env_file to handle app_data_path instead of storage_path.
src/utils/schemas.rs	Added app_data_path to SettingsSchema, deprecating storage_path.

Possibly related issues

• [REQUEST] Split app.env and runtipi-specific env runtipi#900: The separation of environment variables into app.env and app.runtipi.env could benefit from the standardized use of RUNTIPI_ prefixed variables in this PR, enhancing modularity and clarity in environment configuration.

🐇✨
A leap, a hop, in code we trust,
Paths now clear, in variables we must.
From STORAGE_PATH to RUNTIPI bright,
Our code hops forward, into the light!
🌟🐰

---

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

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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