.env.example

# ---------------------------------------------------------------------------
# TIMEZONE CONFIGURATION
# ---------------------------------------------------------------------------
# This lab simulates a distributed system spanning two African time zones.
#
#   Lagos, Nigeria  — WAT (West Africa Time)  — UTC+1
#   Nairobi, Kenya  — EAT (East Africa Time)  — UTC+3
#
# Services by timezone:
#   UTC+1 (Lagos)   : PostgreSQL, Producer, Consumers
#   UTC+3 (Nairobi) : ClickHouse, Transformer
#   UTC+0           : Kafka Brokers, Kafka Connect (infrastructure is always UTC)
#
# The 2-hour gap between source and warehouse timestamps is intentional.
# It demonstrates a core challenge in distributed data engineering:
# timestamps must carry timezone context, or they become meaningless.
# ---------------------------------------------------------------------------

# Source system timezone — Lagos, Nigeria (WAT = UTC+1)
TZ_LAGOS=Africa/Lagos

# Warehouse timezone — Nairobi, Kenya (EAT = UTC+3)
TZ_NAIROBI=Africa/Nairobi

# Infrastructure timezone — Kafka brokers and Kafka Connect always run UTC
TZ_INFRA=UTC