Skip to content

[S4] Add a GET /health endpoint to the NestJS server #803

Description

@Akshola00

Description

The frontend has no way to distinguish between "server is down" and "this specific request failed". A simple health endpoint lets the frontend (or a future monitoring tool) check server availability and show a useful banner rather than confusing 5xx errors on every page.

Deliverables

  • Add a GET /health route to app.controller.ts (or a new HealthController)
  • Response: { status: 'ok', timestamp: new Date().toISOString() }
  • HTTP 200 always (no auth required — health is public)
  • npm run build passes in nevo_server/
  • npm run lint passes in nevo_server/

Notes

No new packages needed — plain NestJS controller method is sufficient. Do not add @nestjs/terminus unless the task explicitly requires dependency health checks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    EasyStellar WaveIssues in the Stellar wave programbackendNestJS server workstage-4Frontend-Backend integration

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions