Skip to content
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

How to test PostHog feature branches, using self-hosted version #25262

Closed
MannyAdumbire opened this issue Sep 27, 2024 · 2 comments
Closed

How to test PostHog feature branches, using self-hosted version #25262

MannyAdumbire opened this issue Sep 27, 2024 · 2 comments

Comments

@MannyAdumbire
Copy link

Is there a guide for on how to test PRs, using the self-hosted/"hobby" docker version of PostHog?
How can I update my local copy/container of PostHog to the changes from a branch.

The question came up in relation to #25174

In attempting to test the PR, I added the hls-src attribute on a <video> element and used an .m3u8 HLS video for its value.

Then did the following:

  1. pulled the latest changes from master branch which contains this merged PR.
  2. ran docker-compose up --build -d
  3. "recorded" a couple sessions for replay

The fix didn't seem to be present still in my local PostHog.
I searched(greped) inside the web, caddy, plugins, worker docker containers, but can't find any reference to hls-src.
None of this worked.

I asked on PostHog Community as well https://posthog.com/questions/how-to-use-latest-version-of-posthog-docker.
The AI answer was not helpful.

What am I missing?

@pauldambra
Copy link
Member

Hey Manny,

I don't actually know the answer here...

My guess is that you need to actually build the front end. However, it's not something we support, so we don't have instructions for this.

However, your title says feature branch and your body says master

If you only want to update to the latest version on trunk, just use the update script https://posthog.com/docs/self-host#upgrading

@MannyAdumbire
Copy link
Author

@pauldambra thanks so much for the suggestions.
I did check out the update script, but was able to get by just by pulling the latest changes from posthog git project, recreating the posthog:posthog image, then rebuilding the containers which worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants