Tracedown Core Backend v0.4.43

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.42

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.41

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.40

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.39

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.38

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.37

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.36

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.35

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.

Tracedown Core Backend v0.4.34

Each service is a self-contained jar (java -jar). tracedown-monolith is the whole platform in one jar — every service in one JVM, the dashboard served from the gateway port, probes executed in-process (no agents needed); it only needs Postgres and Redis. The schema-migrator ships as a zip — unpack and run bin/schema-migrator (it must not be merged into a fat jar; Flyway would find no migrations; the monolith migrates on boot by itself). See the deploy compose in docker/deploy/ for running the per-service stack from these artifacts.