mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekayandHanzo Dev
5ac678fd84
PersonHog was the last of it, and it was not only a name. The package is personinsights and the types in it are already Person* -- the shipped descriptor under personinsights_client/proto/generated says PersonService and the tests say TestFakePersonClient -- but the .proto still declared PersonHogService. A client dialling one service name and a server built from a .proto declaring another is not a naming problem, it is a wire that does not connect; the only reason nobody hit it is that none of these services runs here yet. Five service declarations now say what the generated client has said all along. StreamHog was a second fictional company, invented so a Stripe mock had someone to bill. This fork already has Hedgebox, in five hundred fixtures, so the mock bills Hedgebox and there is one made-up company again instead of two. REVIEW_HOG was an enum member in three enums that had to agree, whose value has been `review` since the app was renamed. Only the member said otherwise. Every rule is in bin/debrand and every spelling is refused there, so a fresh upstream import lands on these names and none of them can come back. Two are named as outstanding rather than refused, with the reason each is still sayable: hogdesk survives inside applied migrations' choices lists, where Django compares it in Python and never writes it -- the member is Desk = "desk" and all three tables that store it hold no rows; sherlockhog keys a service in another repository that still calls itself that, and renaming our half would classify its traffic as a product that does not exist. Co-authored-by: Hanzo Dev <[email protected]>
67 lines
2.0 KiB
YAML
67 lines
2.0 KiB
YAML
# Docker Compose profile overlay — historical backwards-compatibility layer.
|
|
#
|
|
# This file exists only to retroactively gate services that were added to
|
|
# docker-compose.dev.yml before per-service `profiles:` was adopted there.
|
|
# It shadows those service definitions with a `profiles:` constraint so that
|
|
# `insightscli dev:start` and CI can start only what's needed without breaking
|
|
# users who run `docker compose -f docker-compose.dev.yml up` directly
|
|
# (they get all services, same as before).
|
|
#
|
|
# DO NOT add new services here. New profile-gated services should define
|
|
# `profiles:` directly in docker-compose.dev.yml (see capture, plugins,
|
|
# ingestion-* for examples of the current pattern).
|
|
#
|
|
# Usage (legacy, for services still listed below):
|
|
# docker compose -f docker-compose.dev.yml -f docker-compose.profiles.yml \
|
|
# --profile temporal up
|
|
#
|
|
# Services not listed here have no profile constraint and always start.
|
|
|
|
services:
|
|
# Temporal capability - workflow orchestration
|
|
temporal:
|
|
profiles: [temporal]
|
|
temporal-ui:
|
|
profiles: [temporal]
|
|
temporal-admin-tools:
|
|
profiles: [temporal]
|
|
elasticsearch:
|
|
profiles: [temporal]
|
|
|
|
# Observability capability - tracing and logging
|
|
otel-collector:
|
|
profiles: [observability]
|
|
jaeger:
|
|
profiles: [observability]
|
|
|
|
# Dev tools - debugging and monitoring UIs
|
|
kafka_ui:
|
|
profiles: [dev_tools]
|
|
flower:
|
|
profiles: [dev_tools]
|
|
maildev:
|
|
profiles: [dev_tools]
|
|
webhook-tester:
|
|
profiles: [dev_tools]
|
|
|
|
# Session-recording storage (replay).
|
|
seaweedfs:
|
|
profiles: [replay]
|
|
|
|
# Cloud provider emulators
|
|
localstack:
|
|
profiles: [localstack]
|
|
objectstorage-azure:
|
|
profiles: [azure]
|
|
|
|
# Coordination - etcd for personinsights and Kafka partition assignment
|
|
etcd:
|
|
profiles: [etcd]
|
|
|
|
# DuckDB query server
|
|
duckgres:
|
|
profiles: [duckgres]
|
|
|
|
# Core services NOT listed = always start:
|
|
# - proxy, db, redis7, datastore, zookeeper, kafka, objectstorage, feature-flags
|