fix(docker) : fixed app healthcheck issue

[TeKrop]

Fixed #130 healthcheck issue preventing containers from properly running

Summary by Sourcery

This pull request addresses a healthcheck issue in the Docker configuration that was preventing containers from running properly. The healthcheck command was updated to ensure proper functionality.

• Bug Fixes:
  • Fixed healthcheck issue in docker-compose.yml by updating the healthcheck command to use 'wget --spider --quiet http://0.0.0.0:8080'.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request addresses issue #130 by fixing the healthcheck configuration in the Docker setup, ensuring that containers can properly run by modifying the healthcheck command in the docker-compose.yml file.

File-Level Changes

Files	Changes
docker-compose.yml	Updated Docker Compose version and modified the healthcheck command to ensure proper container operation.

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[sourcery-ai]

Hey @TeKrop - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: 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 to tell me if it was helpful.}

[sourcery-ai]

question: Change in healthcheck URL and wget options

The change from 'localhost' to '0.0.0.0' and the addition of '--spider --quiet' options in wget might have been made for specific reasons. Can you confirm if this change was tested in all environments to ensure it behaves as expected?