-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(livestream): Enable custom livestream host (#26106) #27667
Conversation
Signed-off-by: Yidir <[email protected]>
@pauldambra @benjackwhite Can you guys look into this? I made this change small to make it easy to merge. Thanks |
Signed-off-by: Yidir <[email protected]>
@Yiidiir I'm curious about what is the value of the env |
It should be set to whatever host is serving the livestream image and should be accessible from the client. Note that you'll have to use my branch for this to work since Mister @fuziontech didn't merge this yet |
I'm just gonna approve and merge this as it seems fine to me |
Sorry for the hold up @Yiidiir 🙌 |
What happened @benjackwhite 😂 |
Caused a bunch of issues so had to revert.Will fix it here |
Signed-off-by: Yidir <[email protected]>
Signed-off-by: Yidir <[email protected]>
Problem
This is for self-hosted instances, live event features are broken when not running on localhost because of a hard-coded value.
I can also follow up with an updated
docker-compose.hobby.yml
but I feel the ability to set live events host is more important.Closes #26106
Changes
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Does this work well for both Cloud and self-hosted?
Works for self-hosted / No impact for cloud
How did you test this code?
LIVESTREAM_HOST
value to URI of host serving livestream service