mesh-catalog

Files

T

jschoubben 1a28e5aec6 Six modules take their secrets from files; the rest say precisely why not

From the survey of every env-file secret (ADR 0086, issue 041): amqp-ping,
minio, mongodb and grafana use the _FILE twin their software honours;
mesh-catalog and model-usage read DATABASE_URL_FILE (a file the mesh
templates, mounted where only the runtime reads it); grafana's secret files
belong to its own account. Two dead deliveries removed: a line nothing read
in amqp-email-forwarder, and mailu's secret.env on four containers that
never read it. The 25 exceptions that remain carry the surveyed reason —
convertible and awaiting a bed, convertible through a generated config file,
the application's own code, or not convertible.

2026-09-21 12:29:25 +02:00

client.ts

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

Dockerfile

Modules compile in the toolchain and ship on the runtime

2026-09-14 01:57:06 +02:00

index.ts

Move amqp-ping's source, so the mesh has something to notice

2026-09-15 21:03:43 +02:00

module.json

Six modules take their secrets from files; the rest say precisely why not