Feature: Separate Healthcheck Port Configurationre Request:

Problem: Currently, Railway's healthcheck configuration only supports a single path but assumes the same port as the main service. For Spring Boot applications (and other frameworks) that expose management/actuator endpoints on a separate port, there's no way to configure the healthcheck to target that management port without either:

Exposing the management port publicly (security risk)

Proxying healthchecks through the main application port (adds complexity)

Requested Feature: Add an optional healthcheckPort field in the Deploy settings that allows specifying a different port for healthchecks than the main service port.

Example Use Case:

Main app: localhost:8080

Management/Actuator: localhost:9090

Healthcheck should call: localhost:9090/actuator/health

Proposed Solution: Add a healthcheckPort configuration option (optional, defaults to main service port if not specified) in the deploy config UI and API.

Benefits:

Better security (management endpoints stay internal)

Cleaner separation of concerns

Aligns with Spring Boot best practices

No need for workarounds or proxies