From daef5b059d2231e75852a5a06184458fd1bd3bf5 Mon Sep 17 00:00:00 2001 From: Daesgar Date: Fri, 31 Jan 2025 10:56:05 +0100 Subject: [PATCH] chore: include clickhouse-coordinator in the development locally section (#10535) --- contents/handbook/engineering/developing-locally.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contents/handbook/engineering/developing-locally.md b/contents/handbook/engineering/developing-locally.md index 49e374cf1df6..811024d7fefe 100644 --- a/contents/handbook/engineering/developing-locally.md +++ b/contents/handbook/engineering/developing-locally.md @@ -128,11 +128,11 @@ Alternatively, if you'd prefer not to use [Flox-based instant setup](#instant-se In this step we will start all the external services needed by PostHog to work. -First, append line `127.0.0.1 kafka clickhouse` to `/etc/hosts`. Our ClickHouse and Kafka data services won't be able to talk to each other without these mapped hosts. +First, append line `127.0.0.1 kafka clickhouse clickhouse-coordinator` to `/etc/hosts`. Our ClickHouse and Kafka data services won't be able to talk to each other without these mapped hosts. You can do this in one line with: ```bash -echo '127.0.0.1 kafka clickhouse' | sudo tee -a /etc/hosts +echo '127.0.0.1 kafka clickhouse clickhouse-coordinator' | sudo tee -a /etc/hosts ``` > If you are using a newer (>=4.1) version of Podman instead of Docker, the host machine's `/etc/hosts` is used as the base hosts file for containers by default, instead of container's `/etc/hosts` like in Docker. This can make hostname resolution fail in the ClickHouse container, and can be mended by setting `base_hosts_file="none"` in [`containers.conf`](https://github.com/containers/common/blob/main/docs/containers.conf.5.md#containers-table).