All checks were successful
CD / Build and push images (push) Successful in 2m36s
CI / Lint, typecheck, test (push) Successful in 1m50s
CI / Auth e2e pack (push) Successful in 1m58s
CI / Build container images (push) Has been skipped
CD / Deploy to Test (push) Successful in 9s
CD / Smoke tests against Test (push) Successful in 1m13s
CD / Promote to Int (push) Successful in 11s
Bootstrap apps/collab as a Hocuspocus WebSocket server (ADR 0003): - pino JSON logging (service=collab) and shared Zod env validation (collabEnvSchema); structured connection open/close logs. - /healthz endpoint (process liveness + PostgreSQL ping) served via the onRequest hook, matching the container-internal path and the proxied /collab/healthz path; any WebSocket handshake is accepted for now (authentication arrives with #34, persistence with #35). - Dockerfile (ESM workspace build) and a compose service on the frontend and internal networks with a healthcheck; dev overlay service and a new COLLAB_PORT variable. - CD builds, pushes, and promotes the collab image; CI builds it on PRs; the smoke suite asserts /collab/healthz through the reverse proxy. - deployment.md/stages.md: proxy routing, per-stage COLLAB_PORT, checklist. Closes #33 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
533 B
TypeScript
16 lines
533 B
TypeScript
import { pino, type Logger } from 'pino';
|
|
|
|
import type { CollabEnv } from '@dorfteich/shared';
|
|
|
|
/**
|
|
* A pino JSON logger, matching the api's structured output (ADR 0003 asks the
|
|
* collab service to log consistently with the api). Every line carries
|
|
* `service: "collab"` so logs from the two containers are easy to tell apart.
|
|
*/
|
|
export function createLogger(env: Pick<CollabEnv, 'LOG_LEVEL' | 'APP_VERSION'>): Logger {
|
|
return pino({
|
|
level: env.LOG_LEVEL,
|
|
base: { service: 'collab', version: env.APP_VERSION },
|
|
});
|
|
}
|