build: update docker compose deploy

[Tohrusky]

Summary by Sourcery

Update Docker Compose configuration to mount volumes from the project directory for configuration and downloads, simplifying the setup process.

Build:

• Mount configuration files from ./animepipeline instead of ../conf.
• Mount downloads from ./downloads instead of ./docker/downloads.
• Mount qBittorrent configuration from ./allinone/qb-config instead of ./docker/qb-config.
• Update qBittorrent download path to /downloads.

Tests:

• Update test case for Telegram bot with a more descriptive name and a fake torrent hash.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the docker compose deployment configuration. The main changes include updating volume mounts to use local directories instead of relative paths and changing the qbittorrent download path. Also a test case for telegram bot is updated.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated volume mounts for the animepipeline service to use local directories.	Changed volume mount for configuration files from "../conf" to "./animepipeline". Changed volume mount for downloads from "./docker/downloads" to "./downloads".	deploy/docker-compose.yml
Updated volume mounts and download path for the qbittorrent service.	Changed volume mount for configuration files from "./docker/qb-config" to "./allinone/qb-config". Changed volume mount for downloads from "./docker/downloads" to "./downloads". Updated the "download_path" in "server.yml" from "." to "/downloads".	deploy/docker-compose.yml conf/server.yml
Modified the test case for the telegram bot.	Removed unused variables "video_key". Updated the message text in the test function. Changed the torrent file hash in the test function from a real hash to a fake one "this_is_a_fake_hash".	tests/test_tg.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Tohrusky - I've reviewed your changes and found some issues that need to be addressed.

Blocking issues:

• Consider using environment variables for qBittorrent credentials instead of hardcoding them in the configuration file (link)

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🔴 Security: 1 blocking issue
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

🚨 suggestion (security): Consider using environment variables for qBittorrent credentials instead of hardcoding them in the configuration file

Hardcoded credentials pose a security risk and make it difficult to maintain different credentials across environments. Using environment variables would be more secure and flexible.

Suggested implementation:

  username: ${QBITTORRENT_USERNAME:-admin}
  password: ${QBITTORRENT_PASSWORD:-adminadmin}

The developer will need to:

1. Document the new environment variables in the project's README or documentation
2. Update any deployment configurations or scripts to set these environment variables
3. Consider adding these variables to any example .env files (with dummy values)
4. Update CI/CD pipelines to provide these environment variables during testing