v1.7.4

[alexjustesen]

What's Changed

• Bump symfony/http-foundation from 7.3.5 to 7.3.7 in the composer group across 1 directory by @dependabot[bot] in Bump symfony/http-foundation from 7.3.5 to 7.3.7 in the composer group across 1 directory #2406
• Release v1.7.4 by @alexjustesen in Release v1.7.4 #2408

Full Changelog: v1.7.3...v1.7.4

---

This discussion was created from the release v1.7.4.

[SpiderMANek]

Hello,

I am experiencing critical issues with the latest Docker image of Speedtest Tracker.
On my previous setup (OMV), the container deployed and worked correctly. However,
with the current image, the application fails to start and throws HTTP 500 errors.

The Laravel logs show missing files such as:

• app/Providers/FilamentServiceProvider.php
• app/Http/Middleware/GettingStarted.php
• app/Http/Middleware/PublicDashboard.php
• app/Http/Middleware/AcceptJsonMiddleware.php
• app/Http/Middleware/AllowedIpAddressesMiddleware.php

These classes are referenced in config/app.php and bootstrap/app.php, but they
do not exist in the container’s /app/www/ directory. As a result, the application
cannot boot properly.

Steps I tried:

• Commenting out the missing middleware and provider references
• Clearing Laravel cache (php artisan config:clear, etc.)
• Restarting the container with bind mounts for local configuration

Despite these workarounds, the image still requires files that are not included,
which makes it unstable compared to the previous release.

Could you please confirm if this is a packaging issue with the current Docker image?
It seems the build is incomplete or references code that was not shipped. Any guidance
or a corrected image would be greatly appreciated.

Thank you for your support!

[svenvg93]

I would advise to make an issue with all the logs from the container and your compose file.
Quickly checked in my instance and all the files are present.