fix: Move TEMPORAL_HOST to docker-compose.hobby.yml

[feedanal]

Problem

Self-hosted installation has been broken out-of-the-box for more than a year now due to overwriting (not merging) of environment section inside posthog/docker-compose.base.yml: the temporal-django-worker dict extends the &worker reference, but then overwrites the environment to set TEMPORAL_HOST: temporal instead of merging. See #16169 (comment) for details.

Changes

Ditch environment section in posthog/docker-compose.base.yml and move TEMPORAL_HOST to docker-compose.hobby.yml

Does this work well for both Cloud and self-hosted?

self-hosted

How did you test this code?

Had to do this manually per each install and it's wearing me thin.

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[fuziontech]

hey @feedanal! Thanks for flagging this and sorry for the slow response. Solid catch that we are paving over that environment setting on the docker-compose stack. I'd rather not just pull this out from the base and put it in hobby since we honestly have a few docker-compose configs based on this base (that's why it's there!)

I've gone ahead and aliased the worker_env directly so that those blocks are extended and not just paved over.

#22367