Missing /health endpoint causes Docker health checks to fail

[Hell1213]

Describe the bug

The backend does not expose a /health endpoint, but both docker-compose.yml and the production deployment configuration reference /health for health checks.
Because the route is missing, container health checks return 404 even when the backend service is running correctly.

This does not usually block local development when running only specific services, but it can affect full Docker Compose usage, CI, and production deployments.

To Reproduce

Run the backend using Docker (for example, docker-compose up)

Docker executes the configured health check at http://localhost:8000/health

The request returns 404 Not Found because the endpoint is not implemented

Expected behavior

The backend should expose a /health endpoint that returns 200 OK when the service is running, so Docker and Kubernetes health checks can work as intended.

Screenshots

No need for this issue (missing API endpoint).

Desktop (please complete the following information):

OS: Linux (Ubuntu)

Smartphone (please complete the following information):

Device: Not applicable

OS: Not applicable

Browser: Not applicable

Version: Not applicable

Additional context
The /health endpoint is already referenced in:

• docker-compose.yml (line 33)
• production/backend-deployment.yaml (line 69)
• production/docker-compose.yml (line 27)
• production/syncserver-deployment.yaml (line 31)

Adding a simple health check handler would align the backend behavior with the existing infrastructure configuration and prevent containers from being marked unhealthy in automated environments.

[Hell1213]

hey @its-me-abhishek

I would like to pick this issue. Could you please assign it to me?,
can implement the /health endpoint and ensure it works with the existing Docker health checks.