Make Docker health checks more flexible

[guicattani]

First Check

• This is not a feature request.
• I added a very descriptive title to this issue (title field is above this).
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Mealie documentation, with the integrated search.
• I already read the docs and didn't find an answer.
• This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

Docker health checks are making the idle CPU usage sit around 4%. Changing it to something like

    healthcheck:
      test: [ "CMD-SHELL", "echo 0" ]
      interval: 120000s
      retries: 5
      start_period: 30s
      timeout: 10s

Makes the usage negligible

Steps to Reproduce

1. Deploy mealie
2. Check CPU usage after it stabilizes

Please provide relevant logs

None

Mealie Version

v2.4.1

Deployment

Docker (Linux)

Additional Deployment Details

No response

[guicattani]

I found this issue in other applications that I deployed to my home server and this was the fix.

I would suggest that the health checks are kept outside the image so that the user is responsible for it.
It also makes it better in case a user doesn't want to use docker health checks and prefers something like Uptime Kuma to track it.

:)

[Kuchenpirat]

Assuming the 120000 interval is in seconds i would say running a health check less than daily is not advisable, but is surely reducing load from this check as it is running 4000x less often.

Also this seems more like a feature request / change request than an actual issue with mealie. But i would welcome a PR that adds more flexibility around this.

I will convert this into a feature request.

[guicattani]

Thank you! :)

[guicattani]

Please remove the bug and triage labels as I can't do it on my end 😅