test_service

Cloudly workload used to showcase service platform capabilities. The initial capability path is dcrouter-backed service mail through @serve.zone/platformclient 32.0.0, pinned exactly so the image can only ever speak the contract this source compiled against.

• HTTP: PORT or 3000
• Route: test-service.gated.one
• Mail identity: test-service@gated.one
• Outbound SMTP uses Cloudly-managed SMTP_* and MAIL_FROM secrets through platformclient.
• Inbound webhook/TypedRequest-style payloads can be posted to /api/inbound-mail; SMTP forwarding is intentionally not implemented by this app.

Useful endpoints:

• GET /healthz
• GET /api/status
• GET /api/events
• GET /api/inbound-mail
• POST /api/send-mail
• POST /api/inbound-mail
• GET /send-test?to=operator@example.com

GET /healthz answers 200 once service mail is configured and 207 while the workload is up without it; the body always states mailReady.

Image

The service ships as code.foss.global/serve.zone/test_service, built from Dockerfile_##version## by tsdocker. From 32.0.0 on it publishes version tags only - latest stays frozen at its last pre-32 build - and the image states no version of its own: tsdocker stamps version and org.opencontainers.image.version from package.json, and coreflow reads that version label to decide when to roll the service.

test/test_latest.sh is the image qualification tsdocker runs: it checks that the installed @serve.zone/platformclient is exactly the declared version, starts the workload inside the image, and probes /healthz and /.