Matthew Meszaros 01f88b4e28 feat: give every long-running compose service restart: unless-stopped and stop the tracking service exiting on a transient event-bus failure at boot, because the compose file had no restart policy on any service so Docker's default of no applied everywhere and a container that died stayed dead, which for tracking meant a startup DNS race against nats (its producer had no retry and exited immediately) left the service Exited(1) indefinitely with zero visible symptoms anywhere else since open and click tracking is fire-and-forget from the sender's side, so campaigns kept sending and nothing recorded an open or a click until someone thought to run docker compose ps -a, adding bounded retry with exponential backoff capped at ten seconds over eight attempts so the race self-heals without needing the restart policy as a safety net, excluding the one-shot seed job from the policy, and making the tracking host port overridable with TRACKING_PORT since 3000 is a very common default for other self-hosted software and a collision silently stops the container from publishing

2026-08-16 07:17:56 +02:00

..

src

feat: give every long-running compose service restart: unless-stopped and stop the tracking service exiting on a transient event-bus failure at boot, because the compose file had no restart policy on any service so Docker's default of no applied everywhere and a container that died stayed dead, which for tracking meant a startup DNS race against nats (its producer had no retry and exited immediately) left the service Exited(1) indefinitely with zero visible symptoms anywhere else since open and click tracking is fire-and-forget from the sender's side, so campaigns kept sending and nothing recorded an open or a click until someone thought to run docker compose ps -a, adding bounded retry with exponential backoff capped at ten seconds over eight attempts so the race self-heals without needing the restart policy as a safety net, excluding the one-shot seed job from the policy, and making the tracking host port overridable with TRACKING_PORT since 3000 is a very common default for other self-hosted software and a collision silently stops the container from publishing

2026-08-16 07:17:56 +02:00

.gitignore

Analytics & Tracking

2026-01-29 05:59:04 +01:00

Cargo.lock

feat: run the tracking service on nats by default, kafka behind a cargo feature

2026-07-20 09:56:29 +02:00

Cargo.toml

feat: run the tracking service on nats by default, kafka behind a cargo feature

2026-07-20 09:56:29 +02:00

Dockerfile

build: cross compile the go images and fix realtime and the healthchecks

2026-07-21 17:34:59 +02:00