chore(container): rename Docker Compose file to preferred canonical form

[nanotaboada]

This change is 

Summary by CodeRabbit

• Chores

  • Updated Docker configuration to improve file copying accuracy and storage management.
  • Enhanced .dockerignore to exclude more Python cache and compiled files from Docker builds.
  • Assigned a specific name to the storage volume in the compose file for easier management.

• Bug Fixes

  • Improved health check reliability with stricter timeout and error handling in the health check script.

• Refactor

  • Simplified user creation and clarified storage handling in Docker setup.
  • Updated entrypoint script to use the new storage path for the database file.

[coderabbitai]

"""

Walkthrough

This update refines Docker-related configuration and scripts: .dockerignore now excludes Python cache/compiled files, Dockerfile COPY commands use explicit trailing slashes, the SQLite database is relocated to a hold/ directory, the Docker Compose storage volume is explicitly named, and health/entrypoint scripts are updated for clarity and robustness.

Changes

File(s)	Change Summary
.dockerignore	Added patterns to exclude Python cache/compiled files (__pycache__/, *.pyc, *.pyo, *.pyd).
Dockerfile	COPY commands clarified with trailing slashes; storage now copied to hold/; user creation simplified; comments updated.
compose.yaml	Named the storage volume explicitly as python-samples-fastapi-restful_storage.
scripts/entrypoint.sh	Changed database source path from /app/docker-compose/players-sqlite3.db to /app/hold/players-sqlite3.db.
scripts/healthcheck.sh	Enhanced curl command with silent mode, error display, and connection/operation timeouts.

Sequence Diagram(s)

sequenceDiagram
    participant Dockerfile
    participant Image
    participant Volume
    participant EntrypointScript

    Dockerfile->>Image: COPY app directories and assets (with trailing slashes)
    Dockerfile->>Image: COPY storage/ to hold/
    Dockerfile->>Image: Create /storage, set ownership
    Dockerfile->>Image: Set up fastapi user

    EntrypointScript->>Volume: Check if database exists in /storage
    alt Database missing
        EntrypointScript->>Image: Copy /app/hold/players-sqlite3.db to /storage
    end

Loading

Possibly related PRs

• chore: add .dockerignore to optimize build context #353: Introduced the initial .dockerignore file, which this PR extends by adding Python cache/compiled file patterns.
• chore(container): rename database file volume to storage #363: Renamed and restructured the database volume and paths from sqlite3-db to storage, closely related to this PR's reorganization of storage volume paths and Docker image directory structure.
  """

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2f9b22b and 5c0af65.

📒 Files selected for processing (5)

• .dockerignore (1 hunks)
• Dockerfile (2 hunks)
• compose.yaml (1 hunks)
• scripts/entrypoint.sh (1 hunks)
• scripts/healthcheck.sh (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (5)

• scripts/entrypoint.sh
• compose.yaml
• .dockerignore
• scripts/healthcheck.sh
• Dockerfile

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (5170f54)	131	119	90.84%
Head commit (5c0af65)	131 (+0)	119 (+0)	90.84% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#371)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.65%. Comparing base (5170f54) to head (5c0af65).
Report is 5 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #371   +/-   ##
=======================================
  Coverage   89.65%   89.65%           
=======================================
  Files           3        3           
  Lines         116      116           
=======================================
  Hits          104      104           
  Misses         12       12           

Components	Coverage Δ
Services	79.31% <ø> (ø)
Routes	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.