Julien Gautier 8f892972dc
CI / commits (pull_request) Successful in 1m4s
CI / scan (pull_request) Successful in 1m12s
CI / check (pull_request) Successful in 1m13s
CI / a11y (pull_request) Successful in 44s
CI / perf (pull_request) Successful in 1m37s
fix(infra): correct OTel collector image tag
`otel/opentelemetry-collector-contrib:0.115.0` does not exist on
Docker Hub — release 0.115 was published as `0.115.1` only (the
`.0` patch was either yanked or never built). Like the Jaeger
mistake in #58, I picked it from memory in #57 without
verification:

    Error response from daemon: failed to resolve reference
    "docker.io/otel/opentelemetry-collector-contrib:0.115.0":
    not found

Pin to `0.150.1`, the most recent stable patch. The collector
promises backward-compat for stable features (otlp receiver,
batch processor, debug exporter, otlp exporter), so our
`otel-collector.yaml` keeps working as-is. Renovate's
docker-compose manager will surface future bumps automatically.

Postgres / Redis / pgweb tags were verified against Docker Hub at
the same time; they are correct.
2026-05-08 20:21:44 +02:00

Documentation index

This is the entry point to all project documentation. It is maintained automatically: any addition, rename, or removal of a .md file under docs/ must be reflected here in the same change.

Conventions

  • Documentation is written in English.
  • One topic per file. Group related files into a folder when there are three or more.
  • Cross-reference with relative links so they keep working in GitHub, IDEs, and exported sites.
  • For architectural decisions, do not add them here — they belong in decisions/ as MADR 4.0.0 ADRs.

Sections

Daily development

  • development.md — repo layout, prerequisites, initial setup, daily commands, dependency updates (Renovate), conventional commit cycle. Day-to-day reference for working on the project.

Architecture

  • architecture.md — cross-cutting Mermaid diagrams: C4 system context, C4 containers, Nx module boundaries, CI/CD pipeline. Single-decision diagrams (auth sequence, ERD, etc.) live inline in their ADR.

Onboarding & environment

Setup guides for new contributors:

Operations & runbooks

Empty — to be populated when we deploy.

Security, performance, accessibility

Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.

S
Description
No description provided
Readme 42 MiB
Languages
TypeScript 85.3%
JavaScript 5.4%
SCSS 4.3%
HTML 3.9%
Shell 0.8%
Other 0.3%